DESC:DYNAMIC DATA MASKING FOR THICK-CLIENT APPLICATION ,CLAIMS:1. An system for dynamic data masking of thick-client applications, the system comprising:
one or more hardware processors;
a memory coupled with the one or more hardware processors, wherein the one or more hardware processors executes a plurality of modules stored in the memory, and wherein the plurality of modules comprises:
an application analyzer module to interact with a thick-client application for uniquely identifying component characteristics of a plurality of components of the thick-client application, uniquely identifying the component characteristics comprises categorizing the plurality of components as static components and dynamic components;
a rule configurator module to generate a plurality of rules for the plurality of components based at least on the categorizing of the plurality of components, the plurality of rules comprising:
rule definitions associating the component characteristics with one or more modes to interact with the plurality of components, and
sensitivity information associated with sensitivity of data of the plurality of com-ponents and user attributes for accessing the plurality of components;
a rule parser module to parse the plurality of rules and distribute fragments of the plu-rality of rules to respective components of the plurality of components; and
a masking module to mask data associated with the respective components based on the fragments of the plurality of rules.

2. The system as claimed in claim 1, wherein interacting with the thick-client application comprises: capturing handle of each component of the plurality of components; and
uniquely identifying the each component based on one of a hierarchical path and contextual information associated with the each component, the hierarchical path comprising hierarchical arrangement of components of the thick-client application, and the contextual information comprising relative position of the each component with respect to one or more components on a UI of the application.

3. The system as claimed in claim 1, wherein the static components comprises Operating System native components capable of being interacted using native APIs.

4. The system as claimed in claim 1, further comprising interacting with the static component using one of Code Injection and Operating System (OS) APIs, Automation API and Accessibility API.

5. The system as claimed in claim 1, wherein the dynamic components comprises at least one of:
painted components with an underlying environment exposing Application Programming Interfaces (APIs), and
painted component without exposed APIs.

6. The system as claimed in claim 5, wherein the application analyser module identifies the component as painted component without exposed APIs based on one of a position based identification, image based template identification, optical character recognition (OCR) based identification, accessibility API, and automation API.

7. The system as claimed in claim 1, wherein the rule configurator module further updates one or more rules from amongst the plurality of rules based on the interacting of the application analyser module with the thick-client application.

8. A processor-implemented method for dynamic data masking of thick-client applications, the method comprising:
interacting, via one or more hardware processors, with a thick-client application for uniquely identifying component characteristics of a plurality of components of the thick-client application, uniquely identifying the component characteristics comprises categorizing the plurality of components as static components and dynamic components;
generating, via the one or more hardware processors, a plurality of rules for the plurality of components based on the categorizing of the plurality of components, the plurality of rules comprising:
rule definitions associating the component characteristics with one or more modes to interact with the plurality of components, and
sensitivity information associated with sensitivity of data of the plurality of components and user attributes for accessing the plurality of components;
parsing, via the one or more hardware processors, the plurality of rules and distributing fragments of the plurality of rules to respective components of the plurality of components; and
masking, via the one or more hardware processors, data associated with the respective components based on the fragments of the plurality of rules.

9. The method as claimed in claim 8, wherein interacting with the thick-client application comprises: capturing handle of each component of the plurality of components; and
uniquely identifying the each component based on one of a hierarchical path and contextual information associated with the each component, the hierarchical path comprising hierarchical arrangement of components of the thick-client application, and the contextual information comprising relative position of the each component with respect to one or more components on a UI of the application.

10. The method as claimed in claim 8, wherein the static components comprises Operating System native components capable of being interacted using native APIs.

11. The method as claimed in claim 8, further comprising interacting with the static component using one of Code Injection and Operating System (OS) APIs, Automation API and Accessibility API.

12. The method as claimed in claim 8, wherein the dynamic components comprises at least one of:
painted components with an underlying environment exposing Application Programming Interfaces (APIs), and
painted component without exposed APIs.

13. The method as claimed in claim 12, wherein identifying the component as painted component without exposed APIs is based on one of a position based identification, image based template identification, optical character recognition (OCR) based identification, accessibility API, and automation API.

14. The method as claimed in claim 8, further comprising updating one or more rules from amongst the plurality of rules based on the interacting with the thick-client application.