IP Library › Granted Patent US 12,375,469
Granted Patent B2
US 12,375,469 · App. 18/481,512 · Granted Jul 29, 2025

Active data loss prevention (DLP) engine

Inventors: Rajesh K. Shah (Parsippany, NJ); Arif Sufi (Harrison, NJ); Balamurugan Muthu (Phoenix, AZ); Sudip Mukhopadhyay (Jamaica, NY); Deepak Nayak (Dayton, NJ); Senthil K. Ponnappan (Peoria, AZ); Chris Benz (Seville, OH); Christopher D. Elomaa (Coventry, RI); Christine Roberts (Wayland, MA); Ryan Pearson (Cumberland, RI); Jeffrey M. Mayerson (Addison, TX); Christopher C. Ebeling (Westwood, MA); Kalyan C. Gottipati (Phoenix, AZ)
Assignee: Citizens Financial Group, Inc.
H04L63/0815G06F21/6245H04L63/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,375,469
App. No.
18/481,512
Granted
Jul 29, 2025
Kind
B2
Abstract

A unified platform may comprise a combination of independent frameworks that have been integrated and configured to collaboratively operate seamlessly. In some aspects, the unified platform may comprise one or more of an authentication and authorization framework, a dynamic user interface framework, a workflow state management framework, a notification and active data loss and prevention (DLP) engine framework, and an orchestration engine framework. Each of the frameworks included in the unified platform may comprise one or more of the plurality of computing devices executing computer-readable program instructions.

Claims (43)

1. A notification and active data loss and prevention (DLP) engine framework comprising:

one or more computing devices executing computer-readable program instructions that cause the notification and active DLP engine framework to:

capture a flow of data associated with one or more workflow journeys;

extract data objects from the captured flow of data;

determine whether the data objects comprise sensitive data;

classify the data objects based on the determination as to whether the data objects comprise sensitive data; and

initiate at least one of an action and control when the data objects are classified as comprising the sensitive data,

wherein the one or more computing devices comprise a plurality of modules that include at least an event subscriber module and a streaming service module,

wherein the event subscriber module is configured to subscribe to the streaming service module to receive the data objects, and

wherein the data objects further comprise event data associated with the one or more workflow journeys.

2. The notification and active DLP engine framework claim 1 , wherein the sensitive data comprises personal identifying information (PII) data, and wherein the notification and active DLP engine framework is further configured to:

apply one or more rules to the data objects to determine that at least a portion of the data objects comprises PII data; and

classify the portion of the data objects as comprising the PII data.

3. The notification and active DLP engine framework claim 1 , wherein the one or more computing devices are further configured to apply one or more machine learning processes to the data objects and the classifications to adjust the one or more rules.

4. The notification and active DLP engine framework claim 1 , wherein the one or more computing devices comprise an event sourcing framework that includes the plurality of modules, said plurality of modules configured to capture the flow of data associated with the one or more workflow journeys in real-time, in batch, on-demand, periodically, continuously or a combination thereof.

5. The notification and active DLP engine framework claim 1 , further comprising a data conversion module configured to convert data included in the flow of data into text-based data objects.

6. The notification and active DLP engine framework claim 1 , wherein the flow of data associated with the one or more workflow journeys is captured from at least one of a system in communication with the notification and active DLP engine framework, user device in communication with the system and one or more electronic communications received or generated by the system, the one or more electronic communications comprising one or more of a text message, an e-mail and an electronic document.

7. The notification and active DLP engine framework claim 6 , further comprising a communication monitor configured to monitor and interrogate the one or more electronic communications and interrogate content of the one or more electronic communications to identify the sensitive data.

8. The notification and active DLP engine framework claim 6 , wherein the flow of data associated with the one or more workflow journeys comprises at least one of network data, user-generated data, template manager data, data generated or stored by the system in communication with the notification and active DLP engine framework and data included within the electronic communication.

9. The notification and active DLP engine framework claim 6 , wherein the one or more workflow journeys comprises at least two workflow journeys, and wherein the flow of data includes two or more user types, two or more personas or a combination thereof.

10. The notification and active DLP engine framework claim 4 , wherein the plurality of modules further comprises a publisher module.

11. The notification and active DLP engine framework claim 10 , wherein the publisher module is configured to:

interrogate and analyze metadata associated with the data objects to identify at least one source of the flow of data; and

provide the data objects to the streaming service module.

12. The notification and active DLP engine framework claim 11 , wherein the streaming service module is configured to monitor and receive the data objects from the publisher module.

13. The notification and active DLP engine framework claim 12 , further comprising a Command Query Responsibility Segregation (CQRS) framework configured to classify the data objects as comprising the sensitive data and initiate the at least one of the action and control.

14. The notification and active DLP engine framework claim 13 , wherein the CQRS framework comprises one or more of a query module, a rules engine and a knowledge graph module comprising one or more pattern read databases.

15. The notification and active DLP engine framework claim 14 , wherein the query module is configured to:

receive the data objects from the event subscriber module; and

read and apply patterns, rules and scores to the data objects to classify the data objects as comprising at least one of sensitive data and non-sensitive data,

wherein the patterns, rules and scores are accessed from the one or more pattern read databases.

16. The notification and active DLP engine framework claim 15 , wherein the rules engine comprises a command module, a compute module, one or more pattern write databases, the command module configured to:

determine, based on the classification of the data objects, to initiate the at least one of the action and control; and

write, to the one or more pattern write databases, the determination to initiate the at least one of the action and control and details of the at least one action and control.

17. The notification and active DLP engine framework claim 16 , wherein the at least one of the action and control comprises generating a notification, generating an alert and stopping or pausing transmission of a communication.

18. The notification and active DLP engine framework claim 16 , wherein the at least one of the action and control is initiated in real-time, in batch or in a combination thereof.

19. The notification and active DLP engine framework claim 16 , wherein the compute module is configured to:

execute one or more machine learning models to test and update the patterns, rules and scores; and

write the updated patterns, rules and scores to the one or more pattern write databases, wherein the patterns, rules and scores stored in the one or more pattern read databases of the knowledge graph are revised according to the updated patterns, rules and scores.

20. The notification and active DLP engine framework claim 16 , wherein the command module is further configured to initiate the at least one of the action and control responsive to one or more of:

receipt, by the notification and active DLP engine framework, of predetermined user input data;

receipt, by the notification and active DLP engine framework, of inconsistent or erroneous user data; and

completion of one or more workflow steps of the one or more workflow journeys.

Assignments (4)
CORRECTIVE ASSIGNMENT TO CORRECT THE THE ASSIGNOR FROM CHRISTOPHER ELOMAA TO CHRISTOPHER D. ELOMAA PREVIOUSLY RECORDED ON REEL 65136 FRAME 594. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded May 6, 2025
From: SHAH, RAJESH K.; SUFI, ARIF; MUTHU, BALAMURUGAN; MUKHOPADHYAY, SUDIP; NAYAK, DEEPAK; BENZ, CHRIS; ELOMAA, CHRISTOPHER D.; ROBERTS, CHRISTINE; PEARSON, RYAN; MAYERSON, JEFFREY M.; EBELING, CHRISTOPHER C.
To: CITIZENS FINANCIAL GROUP, INC.
Reel/Frame 071190/0121 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2024
From: GOTTIPATI, KALYAN C.
To: CITIZENS FINANCIAL GROUP, INC.
Reel/Frame 069018/0833 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 13, 2023
From: PONNAPPAN, SENTHIL K.
To: CITIZENS FINANCIAL GROUP, INC.
Reel/Frame 065208/0820 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 5, 2023
From: SHAH, RAJESH K.; SUFI, ARIF; MUTHU, BALAMURUGAN; MUKHOPADHYAY, SUDIP; NAYAK, DEEPAK; BENZ, CHRIS; ELOMAA, CHRISTOPHER; ROBERTS, CHRISTINE; PEARSON, RYAN; MAYERSON, JEFFREY M.; EBELING, CHRISTOPHER C.
To: CITIZENS FINANCIAL GROUP, INC.
Reel/Frame 065136/0594 →
Continuity (8)
Continuation 18348631 · Jul 7, 2023
Provisional Application 63423530 · Nov 8, 2022
Provisional Application 63423652 · Nov 8, 2022
Provisional Application 63422029 · Nov 3, 2022
Provisional Application 63422180 · Nov 3, 2022
Provisional Application 63421785 · Nov 2, 2022
Provisional Application 63421797 · Nov 2, 2022
Related Publication 20240146711A1 · May 2, 2024
References Cited (18)
US 9258344B2 · Sharaga et al. · 2016 [cited by applicant]
US 10698738B1 · Sun · 2020 [cited by applicant]
US 11818115B1 · Shah · 2023 [cited by applicant]
US 20040172445A1 · Singh · 2004 [cited by applicant]
US 20130081126A1 · Soukup · 2013 [cited by applicant]
US 20140189123A1 · Dodd · 2014 [cited by applicant]
US 20150088558A1 · Guyan et al. · 2015 [cited by applicant]
US 20160124742A1 · Rangasamy et al. · 2016 [cited by applicant]
US 20160127352A1 · Xu · 2016 [cited by applicant]
US 20180176326A1 · Shantharam et al. · 2018 [cited by applicant]
US 20190355068A1 · Yu et al. · 2019 [cited by applicant]
US 20200065897A1 · McBride · 2020 [cited by applicant]
US 20220116381A1 · Bosch · 2022 [cited by applicant]
US 20230247003A1 · Chanak et al. · 2023 [cited by applicant]
Pai (Automated data classification for mainframes, 2012, 110 pages) (Year: 2012). [cited by examiner]
Boroujeni (Development of a Shared Authentica-Tion System—A Microservice Approach, Master of Science Thesis Nov. 2019, 65 pages), (Year 2019). [cited by applicant]
TitleEditor (Nondeterministic finite automaton, WikipediA, May 6, 2022, 10 pages) (Year: 2022). [cited by applicant]
Jgeek1: “Microservice orchestration using camunda 8 and API gateway,” Sep. 2022 [12 Pages]. [cited by applicant]