DESC:FIELD OF INVENTION
[0001] The embodiments herein relate to a method and system for automatically managing Aadhaar data, specifically for Aadhaar data discovery. The present application is based on, and claims priority from an Indian Application Number 201741022992 filed on 30th June, 2017, the disclosure of which is hereby incorporated by reference herein.
BACKGROUND OF INVENTION
[0002] Data security is essential to maintaining and managing data pertaining to identity, health records, confidential matters and the like.
[0003] The Aadhaar card (UID) is an attempt to uniquely & digitally identify people for the primary purpose of tracking the social security of an individual. However, due to certain cyber threats and lack of secured storage inputs Aadhaar data has not been secured properly. To address such issues the regulatory authority of Aadhaar data, the Unique Identification Authority of India (UIDAI) has come up with a compliance checklist. In a
[0004] As per UIDAI norms entities using Aadhaar information cannot store private data (Card number, Personal Identification Number and biometric data) as this may lead to a breach in confidentiality. The stored data detection is impossible as it is stored in numerous sources like mails, data base, file systems, shared folders and the like. There remains a need for systems and methods for detecting Aadhaar data while maintaining confidentiality norms provided by the UIDAI.
[0005] The above information is presented as background information only to help the reader to understand the present invention. Applicants have made no determination and make no assertion as to whether any of the above might be applicable as Prior Art with regard to the present application.

OBJECT OF INVENTION
[0006] The principal object of the embodiments herein is to provide.
[0007] Another object of the embodiments herein is to automatically manage Aadhaar data in a data management system.
[0008] Another object of the embodiments herein is to determine an Aadhaar policy pertaining to an action to be performed on Aadhaar data.
[0009] Another object of the embodiments herein is to dynamically determine the Aadhaar data by scanning applications stored in the data management system.
[0010] Another object of the embodiments herein is to automatically perform an action on the Aadhaar data based on the Aadhaar policy without requiring a user input.
SUMMARY
[0011] Accordingly, embodiments disclosed herein provide a method for automatically managing Aadhaar data in a data management system. The method includes determining an Aadhaar policy for at least one action to be performed on Aadhaar data of a user stored at the data management system, dynamically determining the Aadhaar data of the user by scanning each application stored at the data management system and automatically performing the at least one action on the Aadhaar data based on the Aadhaar policy without requiring a user input.
[0012] In an embodiment, the at least one action comprises removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
[0013] In an embodiment, the Aadhaar policy comprises at least one of removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
[0014] In an embodiment, dynamically determining the Aadhaar data of the user by scanning each application stored at the data management system includes opening and reading data available in each of the applications in the data management system by scanning each application stored at the data management system.
[0015] In an embodiment, the Aadhaar data pattern comprises at least one of a regular expression, a unique identifier pattern, a biometric identifier, a personal information identifier.
[0016] Accordingly, embodiments disclosed herein provide a data management system that includes a processor, a memory to store data associated with a user, a data discovery engine operationally coupled to the memory and the processor and a confidential data controller operationally coupled to the data discovery engine. The data discovery engine is configured to determine an Aadhaar policy for at least one action to be performed on Aadhaar data of a user stored at the memory and dynamically determine the Aadhaar data of the user by scanning each application stored at the memory.
[0017] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF FIGURES
[0018] This invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0019] FIG. 1 is a general overview of an system for managing Aadhaar data, according to an embodiment as disclosed herein;
[0020] FIG. 2 illustrates various hardware components of a data management system, according to an embodiment as disclosed herein;
[0021] FIG. 3 is a flow diagram illustrating a method to manage Aadhaar data, according to an embodiment as disclosed herein;
[0022] FIG. 4 is a flow diagram illustrating a method to detect and truncate Aadhaar data, according to embodiments as disclosed herein;
[0023] While embodiments of the present disclosure are described herein by way of example using several illustrative drawings, those skilled in the art will recognize the present disclosure is not limited to the embodiments or drawings described. It should be understood the drawings and the detailed description thereto are not intended to limit the present disclosure to the form disclosed, but to the contrary, the present disclosure is to cover all modification, equivalents and alternatives falling within the spirit and scope of embodiments of the present disclosure as defined by the appended claims.

DETAILED DESCRIPTION OF INVENTION
[0024] Various embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. In the following description, specific details such as detailed configuration and components are merely provided to assist the overall understanding of these embodiments of the present disclosure. Therefore, it should be apparent to those skilled in the art that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.
[0025] Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. Herein, the term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein. Further it should be possible to combine the flows specified in different figures to derive a new flow.
[0026] As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, engines, controllers, units or modules or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware and software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
[0027] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein.
[0028] Embodiments herein discuss an Aadhaar Data Discovery Engine that scans and identifies the Aadhaar data. This tool also helps in masking or truncating the Aadhaar Data information in one click, hence it helps in saving time by identifying Aadhaar data and deleting the same.
[0029] Unlike conventional methods and systems, embodiments disclosed herein provide a method for automatically managing Aadhaar data in a data management system. The method includes determining an Aadhaar policy for at least one action to be performed on Aadhaar data of a user stored at the data management system, dynamically determining the Aadhaar data of the user by scanning each application stored at the data management system and automatically performing the at least one action on the Aadhaar data based on the Aadhaar policy without requiring a user input.
[0030] Referring now to the drawings and more particularly to FIGS. 1 through 4, where similar reference characters denote corresponding features consistently throughout the figure, there are shown preferred embodiments.
[0031] FIG. 1 is a general overview of a data management system 1000 for managing Aadhaar data. The data management system 1000 includes a data management device 100 coupled to a plurality of targets (target 300a to target 300n), collectively referred to as target 300. The data management device 100 is communicably coupled to the targets 300 through a communication network 200.
[0032] The data management device 100 and the targets 300 can be but not limited to a smartphone, a tablet computer, a personal computer and a server. In some embodiments, the data management device 100 and the targets 300 can include communication units pertaining to communication with remote computers, servers or remote databases over the communication network 200. The communication network 200 can include a data network such as, but not restricted to, the Internet, local area network (LAN), wide area network (WAN), metropolitan area network (MAN) etc. In certain embodiments, the communication network 200 can include a wireless network, such as, but not restricted to, a cellular network and may employ various technologies including enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS) etc. Accordingly, the data management device 100 is included with communication components facilitating communications over the communication network 200.
[0033] In some embodiments, an Aadhaar discovery application can be installed and stored on the data management device 100. A user registers with the tool on the data management device 100 and sets a new password for further actions such as but not limited to further login and scanning of the targets 300. Registration typically requires details such as but not limited to name, email, and the like. In an embodiment, all registration details are encrypted using AES 256 bit encryption standard and stored on the data management device 100 or in cloud storage.
[0034] The registered user configures the Aadhaar discovery application to select the types of files that need to be scanned. The user can add remote targets among the targets 300 to search Aadhaar data.
[0035] In some embodiments, the data management device 100 can be utilized to determine an Aadhaar policy for an action to be performed on the Aadhaar data of the user stored in any of the targets 300. The Aadhaar data is dynamically determined by scanning files stored on each of the targets 300. Upon determining the Aadhaar data, an action in accordance with the Aadhaar policy is performed.
[0036] In some embodiments, the action includes removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
[0037] In some embodiments, the Aadhaar policy includes any or a combination of removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantining the encrypted Aadhaar data in a secure storage communicably coupled to the data management system 100.
[0038] In some embodiments, the Aadhaar data is dynamically determined by scanning each application stored in the data management device 100 and/or any of the targets 300 added by the user during registration. This further includes opening and reading data available in each of the applications and dynamically determining the Aadhaar data by matching the data available in the each of the applications based on an Aadhaar data pattern. The Aadhaar data pattern can include but is not limited to a regular expression, a unique identifier pattern, a biometric identifier, a personal information identifier.
[0039] FIG. 2 illustrates various hardware components of the data management device 100, according to an embodiment as disclosed herein. The data management device 100 includes a data discovery engine 110, a confidential data controller 120, a processor 130 and a memory 140. The data discovery engine 110 is operationally coupled to the memory 130, the processor 140 and the confidential data controller 120. The data discovery engine 110 determines the Aadhaar policy for the action to be performed on the Aadhaar data of the user based on preferences provided by the user at the time of registration. The data discovery engine 110 further dynamically determines the Aadhaar data of the user by scanning each application stored in the memory 130 and in the targets 300.
[0040] The confidential data controller 120 automatically performs the action on the Aadhaar data based on the Aadhaar policy without requiring any user input.
[0041] The processor 140 can be, but not restricted to, a Central Processing Unit (CPU), a microprocessor, or a microcontroller. The processor 140 executes sets of instructions stored on the memory 130.
[0042] The memory 130 includes storage locations to be addressable through the processor 140. The memory 130 is not limited to a volatile memory and/or a non-volatile memory. Further, the memory 130 can include one or more computer-readable storage media. The memory 130 can include non-volatile storage elements. For example, non-volatile storage elements can include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
[0043] Dynamically determining the Aadhaar data entails opening files in all applications on the memory 130 and at the targets 300, and searching for the Aadhaar data. Based on selection criteria provided at the time of registration, a plain text Aadhaar number are scanned in all files by the data discovery engine 110. If the Aadhaar number is of twelve digits uses a regular expression to validate the Aadhaar number which is:
(?:[0-9]{4}[0-9]{4}[0-9]{4})+ - (1)
[0044] If the plain text Aadhar number passes regular expression and the plain text Aadhaar number is further validated using the algorithm below:
private static int[,] _multiplicationTable = {
{ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 },
{ 1, 2, 3, 4, 0, 6, 7, 8, 9, 5 },
{ 2, 3, 4, 0, 1, 7, 8, 9, 5, 6 },
{ 3, 4, 0, 1, 2, 8, 9, 5, 6, 7 },
{ 4, 0, 1, 2, 3, 9, 5, 6, 7, 8 },
{ 5, 9, 8, 7, 6, 0, 4, 3, 2, 1 },
{ 6, 5, 9, 8, 7, 1, 0, 4, 3, 2 },
{ 7, 6, 5, 9, 8, 2, 1, 0, 4, 3 },
{ 8, 7, 6, 5, 9, 3, 2, 1, 0, 4 },
{ 9, 8, 7, 6, 5, 4, 3, 2, 1, 0 }
};
private static int[,] _permutationTable = {
{ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 },
{ 1, 5, 7, 6, 2, 8, 3, 0, 9, 4 },
{ 5, 8, 0, 3, 7, 9, 6, 1, 4, 2 },
{ 8, 9, 1, 6, 0, 4, 3, 5, 2, 7 },
{ 9, 4, 5, 3, 1, 2, 6, 8, 7, 0 },
{ 4, 2, 8, 6, 5, 7, 3, 9, 0, 1 },
{ 2, 7, 9, 3, 8, 0, 6, 4, 1, 5 },
{ 7, 0, 4, 6, 9, 1, 3, 2, 5, 8 }
};
int[] _inverseTable = { 0, 4, 3, 2, 1, 5, 6, 7, 8, 9 };
int c = 0;
int len = number.Length;
for (int i = 0; i < len; ++i)
c = _multiplicationTable[c, _permutationTable[((i + 1) % 8), number[len - i - 1] - '0']];
return _inverseTable[c];
int[] array = new int[cardNumber.Length];
for (int i = 0; i < cardNumber.Length; i++)
{ array[i] = int.Parse(cardNumber.Substring(i, 1));}
if (array[0] != 0 && array[0] != 1)
{ int c = 0;
int len = cardNumber.Length;
for (int i = 0; i < len; ++i)
c = _multiplicationTable[c, _permutationTable[(i % 8), cardNumber[len - i - 1] - '0']];
return c == 0;}
[0045] Upon successful validation, the result is displayed through the data management device 100. The data discover engine 110 closes the file and open another file and the process continues till all files in all targets 300 are scanned and validated.
[0046] In an embodiment, unique identity data (UID) and personal identity data (PID) data based on the number format are scanned in the files. If the Aadhaar number passes the regular expression
[0-9]{4}[0-9]{4}[0-9]{4})""" + @".*?>[\D +[\d]*? - (2)
[0047] The Aadhaar number is then validated using Aadhaar PID and UID algorithms which is as follows:
Aadhar PID and UID format should be like this.



*****
*******
+JY/BaTREZpu68y









******


*******


******
******

[0048] Accordingly, the result is displayed on the data management device 100.
[0049] In an embodiment, the data discovery engine 110 opens a file and search for the Aadhaar number. Biometric data and PID data based on the number format are scanned. If number passes the authentication format then further validation is done using Biometric data.
[0050] The Biometric data always store in base64 string format. For example, the Biometric data format can be the following:
Rk1SACAyMAAAAAEZXZZXssyAAABGAFUAMUAxQEAAABkLoCnABAZZIC1ABgVZIDFACANZEDzACoBZECDADQVZIDHADiLZICmAEwNZIB1AF2cZIDQAGKIZECtAGUGZIDOAIGFZICoAIMQZICMAImcZIDUAJH6ZID1AJl0ZIDVAJ2AZIAjAKqhZICgAK6hZIDwAK50ZEByALQlZEEAALjpZID3ALzmZIC6AL0VZECPAMcmZECVAOMoZECrAOkiZEDTAO4BZIDQAPf6ZIDdAPl6ZECHAP6qZEDeAP/nZIC1AQMhZIBPAQ8mZEDgAQ9mZEDCARAVZEDKARkAZIB3ASAoZICMASUmZECgASenZIECASjQZIDMAS3aZEDwATHIZIBAATKeZECxATIeZEC6ATqbZIDOATzHZAAA
[0051] Further validation is performed if the Aadhaar number number passes a biometric regular expression as given below:
Rk1S.*?[\D]+.*?AA
[0052] The corresponding result is displayed on the data management device 100. The process continues until all files are scanned.
[0053] In an embodiment, the data discovery engine checks whether all files are scanned and repeats the above methods until all files stored in the memory 130 and the targets 300 are scanned. Once scan is complete, the user is notified via the display of the data management device 100 that the scan is complete and can take further actions whether to truncate or mask identified data based on the Aadhaar policy determined by the data discovery engine 110.
[0054] The confidential data controller 120 automatically performs the action on the Aadhaar data based on the Aadhaar policy without requiring any user input.
[0055] Truncation of identified data cannot be reverted as per the Aadhaar UIDAI guide lines. In an example, plain text Aadhaar numbers are shown below:
34999999999901 2010IPG-53
35549933587201 2010IPG-54
[0056] After truncation the Aadhaar Number. Text will be storis stored as
342010IPG-53
352010IPG-54
[0057] Suppose Aadhaar number with PID identified in the file is as below:
[0503/161021.358:ERROR:registration_protocol_win.cc(83)]

mWrYVOKXs=iMEI

TransactNamedPipe: The pipe has been ended. (0x6D)
[0058] After truncation the Aadhaar Number with PID is stored as shown below:
[0503/161021.358:ERROR:registration_protocol_win.cc(83)]
TransactNamedPipe: The pipe has been ended. (0x6D)
[0059] In the case of biometric data as shown below:
Rk1SACAyMAAAAAEZXZZXssyAAABGAFUAMUAxQEAAABkLoCnABAZZIC1ABgVZIDFACANZEDzACoBZECDADQVZIDHADiLZICmAEwNZIB1AF2cZIDQAGKIZECtAGUGZIDOAIGFZICoAIMQZICMAImcZIDUAJH6ZID1AJl0ZIDVAJ2AZIAjAKqhZICgAK6hZIDwAK50ZEByALQlZEEAALjpZID3ALzmZIC6AL0VZECPAMcmZECVAOMoZECrAOkiZEDTAO4BZIDQAPf6ZIDdAPl6ZECHAP6qZEDeAP/TzHZAAA
79 2010IPG-114
[0060] After truncation the biometric data is stored as:
79 2010IPG-114
[0061] In an embodiment, the confidential data controller 120 automatically masks the Aadhaar data based on the Aadhaar policy without requiring any user input.
[0062] Masking is nothing but replacing number with * mark as per UIDAI guidelines masking also for remediation as plain text Aadhaar data cannot be stored at any cost.
[0063] Let's suppose some Aadhaar number identified in the file -
34999999999901 2010IPG-53
35549933587201 2010IPG-54
[0064] After masking the Aadhaar number is stored in the manner shown below:
34999******901 2010IPG-53
35549******201 2010IPG-54
[0065] Suppose Aadhaar number with PID identified in the file -
[0503/161021.358:ERROR:registration_protocol_win.cc(83)]

mWrYVOKXs=iMEI

TransactNamedPipe: The pipe has been ended. (0x6D)
[0066] After masking the Aadhaar Number with PID, the corresponding Aadhaar data is stored as:
[0503/161021.358:ERROR:registration_protocol_win.cc(83)]

TransactNamedPipe: The pipe has been ended. (0x6D)
[0067] Suppose Biometric Data identified in the file is as shown below:
Rk1SACAyMAAAAAEZXZZXssyAAABGAFUAMUAxQEAAABkLoCnABAZZIC1ABgVZIDFACANZEDzACoBZECDADQVZIDHADiLZICmAEwNZIB1AF2cZIDQAGKIZECtAGUGZIDOAIGFZICoAIMQZICMAImcZIDUAJH6ZID1AJl0ZIDVAJ2AZIAjAKqhZICgAK6hZIDwAK50ZEByALQlZEEAALjpZID3ALzmZIC6AL0VZECPAMcmZECVAOMoZECrAOkiZEDTAO4BZIDQAPf6ZIDdAPl6ZECHAP6qZEDeAP/TzHZAAA
792010IPG-114
[0068] After masking the biometric data, the corresponding Aadhaar data is stored as:
Rk1S**************************************AA
792010IPG-114
[0069] In an embodiment, the data discovery engine 110 can generate a final report once all the scan procedure is done and reports can be shared with the information security consultants and network administrators for further validations.
[0070] FIG. 3 is a flow diagram illustrating a method 400 to manage Aadhaar data, according to an embodiment as disclosed herein. At step 402 the data management device 100 can be utilized to determine an Aadhaar policy for an action to be performed on the Aadhaar data of the user stored in any of the targets 300. At steps 404 and 406, the Aadhaar data is dynamically determined by scanning each application stored in the data management device 100 and/or any of the targets 300 added by the user during registration. This further includes opening and reading data available in each of the applications and dynamically determining the Aadhaar data by matching the data available in the each of the applications based on an Aadhaar data pattern. The Aadhaar data pattern can include but is not limited to a regular expression, a unique identifier pattern, a biometric identifier, a personal information identifier.
[0071] The Aadhaar data is dynamically determined by scanning files stored on each of the targets 300. Upon determining the Aadhaar data, at step 408, an action in accordance with the Aadhaar policy is performed. The action includes removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
[0072] FIG. 4 is a flow diagram illustrating a method 500 to detect and truncate Aadhaar data, according to embodiments as disclosed herein. At steps 502 and 504, the Aadhaar data is dynamically determined by scanning each application stored in the data management device 100 and/or any of the targets 300 added by the user during registration. This further includes opening and reading data available in each of the applications and dynamically determining the Aadhaar data by matching the data available in the each of the applications based on an Aadhaar data pattern. The Aadhaar data pattern can include but is not limited to a regular expression, a unique identifier pattern, a biometric identifier, a personal information identifier.
[0073] Accordingly, at steps 506, 508 and 510, the Aadhaar number is checked to have 12 digits, UID form or contain biometric data respectively. If it doany of the checks are successful based on expressions 1, 2 and 3, the Aadhaar number is further validated at step 512 using algorithms explained previously. At step 514, the corresponding result is displayed at the data management device 100. At step 516,the data discovery engine 110 checks if all the files have been scanned. Accordingly, the confidential data controller stores the detected Aadhaar data in masked or truncated form (step 518).
[0074] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in FIGS. 1-4 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0075] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
,CLAIMS:STATEMENT OF CLAIMS
We claim:
1. A method for automatically managing Aadhaar data in a data management system, comprising:
determining an Aadhaar policy for at least one action to be performed on Aadhaar data of a user stored at the data management system;
dynamically determining the Aadhaar data of the user by scanning each application stored at the data management system; and
automatically performing the at least one action on the Aadhaar data based on the Aadhaar policy without requiring a user input.
2. The method of claim 1, wherein the at least one action comprises removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
3. The method of claim 1, wherein the Aadhaar policy comprises at least one of removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
4. The method of claim 1, wherein the dynamically determining the Aadhaar data of the user by scanning each application stored at the data management system comprising:
opening and reading data available in each of the applications in the data management system by scanning each application stored at the data management system; and
dynamically determining the Aadhaar data by matching the data available in the each of the applications based on an Aadhaar data pattern.
5. The method of claim 4, wherein the Aadhaar data pattern comprises at least one of a regular expression, a unique identifier pattern, a biometric identifier, a personal information identifier.
6. A data management system, comprising:
a processor;
a memory to store data associated with a user; and
a data discovery engine, operationally coupled to the memory and processor, configured to:
determine an Aadhaar policy for at least one action to be performed on Aadhaar data of a user stored at the memory; and
dynamically determine the Aadhaar data of the user by scanning each application stored at the memory, and
a confidential data controller, operationally coupled to the data discovery engine, configured to automatically perform the at least one action on the Aadhaar data based on the Aadhaar policy without requiring a user input .
7. The system of claim 6, wherein the at least one action comprises removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
8. The system of claim 6, wherein the Aadhaar policy comprises at least one of removing the Aadhaar data from the application, truncating the Aadhaar data in the application, masking the Aadhaar data in the application, and encrypting the Aadhaar data and quarantine the encrypted Aadhaar data in a secured location in the data management system.
9. The system of claim 6, wherein the dynamically determining the Aadhaar data of the user by scanning each application stored at the data management system comprising:
opening and reading data available in each of the applications in the data management system by scanning each application stored at the data management system; and
determining the Aadhaar data by matching the data available in the each of the applications based on an Aadhaar data pattern.
10. The system of claim 9, wherein the Aadhaar data pattern comprises at least one of a regular expression, a unique identifier pattern, a biometric identifier, a personal information identifier.

Dated: 29th Day of June, 2018 Signature
Arun Kishore Narasani. Patent Agent