Abstract: The present subject matter relates to securing data on a computing system (102). In an example, a request to execute an application instance of the application is received. After receiving the request a role to be associated with the application instance may be identified based on one of user inputs, an object-role mapping, and a set of rules. Further, the application is executable in a plurality of application instances and the role of the application instance is indicative of a nature of activity to be performed in the application instance. The identified role is then associated with the application instance. Based on the role, data pertaining to the application instance may be stored in a memory location allocated to the role of the application instance. Further, each role has a dedicated memory location.
CLIAMS:1. A method to secure data on a computing system (102), the method comprising:
receiving a request to execute an application instance of an application;
identifying a role to be associated with the application instance based on one of user inputs, an object-role mapping, and a set of rules, wherein the application is executable in a plurality of application instances, and wherein the role of the application instance is indicative of a nature of activity to be performed in the application instance;
associating, based on the identifying, the role with the application instance; and
storing, based on the role, data pertaining to the application instance in a memory location allocated to the role of the application instance, wherein each role has a dedicated memory location.
2. The method as claimed in claim 1, wherein the identifying further comprises,
associating, based on one of the user inputs, the object-role mapping, and the set of rules, a persistence attribute and a rank attribute with the role.
3. The method as claimed in claim 2, wherein, on being classified as a permanent role based on the persistence attribute, the data pertaining to the permanent role is allowed to persist in the memory location dedicated to the permanent role after the execution of the application instance associated with the permanent role is complete.
4. The method as claimed in claim 2, wherein, on being classified as a temporary role based on the persistence attribute, the data pertaining to the temporary role is removed from the memory location dedicated to the temporary role after the execution of the application instance associated with the temporary role is complete.
5. The method as claimed in claim 2, wherein access to the dedicated memory location of the role is provided based on an absolute criteria when the rank attribute is not set, and wherein the absolute criteria indicates that the data in the dedicated memory location of the role is made inaccessible to one or more other roles.
6. The method as claimed in claim 2, wherein access to the dedicated memory location of the role is provided based on a hierarchical access criteria when the rank attribute is set, and wherein the hierarchical access criteria indicates that access to the dedicated memory location of the role is provided based on a hierarchical rank associated with the role such that data in the dedicated memory location of roles associated with a lower hierarchical rank is made accessible to one or more other roles associated with a higher hierarchical rank.
7. The method as claimed in claim 1, wherein the method further comprises:
ascertaining, based on role switching data, whether there is a probable data security threat to the data in the role, the role switching data including information pertaining to malicious objects; and
based on the ascertaining, switching, while executing the application instance, from the role to a random role, wherein, upon the switching, the data pertaining to the application instance is stored in the memory location dedicated to the random role.
8. The method as claimed in claim 1, wherein the method further comprises:
identifying, based on user inputs, the application to be integrated with a role generation module (114); and
integrating, based on the identifying, the role generation module (114) with the identified application.
9. The method as claimed in claim 1, wherein the method further comprises moving the data pertaining to the application instance from the dedicated memory location of the role to a secondary memory location at predetermined time intervals.
10. The method as claimed in claim 1, wherein the method further comprises:
creating a plurality of roles for the application, wherein each role is created based on the nature of activity performed in the application instance of the application; and
allocating a respective dedicated memory location to each of the plurality of roles.
11. A computing system (102) to secure data, the computing system (102) comprising:
a memory (108);
a processor(s) (104);
a role generation module (114) coupled to the processor(s) (104) to:
receive a request to execute an application instance of an application;
identify a role to be associated with the application instance, wherein the application is executable in a plurality of application instances, and wherein the role of the application instance is indicative of a nature of activity to be performed in the application instance; and
associate the role with the application instance; and
a data security module (120) coupled to the processor(s) (104) to,
store, based on the role, data pertaining to the application instance in a memory location allocated to the role of the application instance, wherein each role has a dedicated memory location.
12. The computing system (102) as claimed in claim 11, wherein the role generation module (114):
identifies the role to be associated with the application instance based on one of user inputs, an object-role mapping, and a set of rules, wherein the object-role mapping indicates the role to be associated with an object; and
associates a persistence attribute and a rank attribute with the role, based on one of the user inputs, the object-role mapping, and the set of rules.
13. The computing system (102) as claimed in claim 12, wherein the role is classified as a permanent role when the persistence attribute is set, and wherein the data security module (120) allows the data pertaining to the permanent role to persist in the memory location dedicated to the permanent role after the execution of the application instance associated with the permanent role is complete.
14. The computing system (102) as claimed in claim 12, wherein the role is classified as a temporary role when the persistence attribute is not set, and wherein the data security module (120) removes the data pertaining to the temporary role from the memory location dedicated to the temporary role after the execution of the application instance associated with the temporary role is complete.
15. The computing system (102) as claimed in claim 12, wherein the data security module (120) provides access to the dedicated memory location of the role based on an absolute criteria when the rank attribute is not set, and wherein the absolute criteria indicates that the data in the dedicated memory location of the role is to be made inaccessible to one or more other roles.
16. The computing system (102) as claimed in claim 12, wherein the data security module (120) provides access to the dedicated memory location of the role based on a hierarchical access criteria when the rank attribute is set, and wherein the hierarchical access criteria indicates that access to the dedicated memory location of the role is provided based on a hierarchical rank associated with the role such that data in the dedicated memory location of roles associated with a lower hierarchical rank is to be made accessible to one or more other roles associated with a higher hierarchical rank.
17. The computing system (102) as claimed in claim 11, wherein the data security module (120):
ascertains, based on role switching data, whether there is a probable data security threat to the data in the role, the role switching data including information pertaining to malicious objects; and
upon ascertaining that there is a probable data security threat, switches, while executing the application instance, from the role to a random role, wherein, upon the switching, the data pertaining to the application instance is stored in the memory location dedicated to the random role.
18. The computing system (102) as claimed in claim 11, further comprising an application integration module (113) coupled to the processor(s) (104) to:
identify, based on user inputs, the application to be integrated with the role generation module (114); and
integrate, based on the identifying, the role generation module (114) with the identified application.
19. The computing system (102) as claimed in claim 11, wherein the role generation module (114):
creates a plurality of roles for the application, wherein each role is created based on the nature of activity performed in the application instance of the application; and
allocates a respective dedicated memory location, to each of the plurality of roles.
20. A non-transitory computer readable medium having embodied thereon a set of computer readable instructions that, when executed, perform a method to secure data on a computing system (102), the method comprising:
receiving a request to execute an application instance of an application;
identifying a role to be associated with the application instance based on one of user inputs, an object-role mapping, and a set of rules, wherein the application is executable in a plurality of application instances, and wherein the role of the application instance is indicative of a nature of activity to be performed in the application instance;
associating, based on the identifying, the role with the application instance; and
storing, based on the role, data pertaining to the application instance in a memory location allocated to the role of the application instance, wherein each role has a dedicated memory location.
,TagSPECI:As Attached
| # | Name | Date |
|---|---|---|
| 1 | 3560-MUM-2014-IntimationOfGrant13-11-2023.pdf | 2023-11-13 |
| 1 | Form 5 [11-11-2014(online)].pdf | 2014-11-11 |
| 2 | 3560-MUM-2014-PatentCertificate13-11-2023.pdf | 2023-11-13 |
| 2 | Form 3 [11-11-2014(online)].pdf | 2014-11-11 |
| 3 | Drawing [11-11-2014(online)].pdf | 2014-11-11 |
| 3 | 3560-MUM-2014-Written submissions and relevant documents [06-11-2023(online)].pdf | 2023-11-06 |
| 4 | Description(Complete) [11-11-2014(online)].pdf | 2014-11-11 |
| 4 | 3560-MUM-2014-FORM-26 [23-10-2023(online)].pdf | 2023-10-23 |
| 5 | REQUEST FOR CERTIFIED COPY [09-12-2015(online)].pdf | 2015-12-09 |
| 5 | 3560-MUM-2014-Correspondence to notify the Controller [11-10-2023(online)].pdf | 2023-10-11 |
| 6 | SPEC FOR FILING PD013747IN-SC.pdf | 2018-08-11 |
| 6 | 3560-MUM-2014-US(14)-HearingNotice-(HearingDate-25-10-2023).pdf | 2023-09-29 |
| 7 | FORM 5 PD013747IN-SC.pdf | 2018-08-11 |
| 7 | 3560-MUM-2014-CLAIMS [16-04-2020(online)].pdf | 2020-04-16 |
| 8 | FORM 3 PD013747IN-SC.pdf | 2018-08-11 |
| 8 | 3560-MUM-2014-COMPLETE SPECIFICATION [16-04-2020(online)].pdf | 2020-04-16 |
| 9 | 3560-MUM-2014-FER_SER_REPLY [16-04-2020(online)].pdf | 2020-04-16 |
| 9 | FIGURES PD013747IN-SC.pdf | 2018-08-11 |
| 10 | 3560-MUM-2014-OTHERS [16-04-2020(online)].pdf | 2020-04-16 |
| 10 | 3560-MUM-2014-Power of Attorney-200115.pdf | 2018-08-11 |
| 11 | 3560-MUM-2014-FORM 18.pdf | 2018-08-11 |
| 11 | 3560-MUM-2014-Information under section 8(2) [24-03-2020(online)].pdf | 2020-03-24 |
| 12 | 3560-MUM-2014-Form 1-271114.pdf | 2018-08-11 |
| 12 | 3560-MUM-2014-FORM 3 [23-03-2020(online)].pdf | 2020-03-23 |
| 13 | 3560-MUM-2014-Correspondence-271114.pdf | 2018-08-11 |
| 13 | 3560-MUM-2014-FER.pdf | 2019-10-16 |
| 14 | 3560-MUM-2014-Correspondence-200115.pdf | 2018-08-11 |
| 15 | 3560-MUM-2014-Correspondence-271114.pdf | 2018-08-11 |
| 15 | 3560-MUM-2014-FER.pdf | 2019-10-16 |
| 16 | 3560-MUM-2014-Form 1-271114.pdf | 2018-08-11 |
| 16 | 3560-MUM-2014-FORM 3 [23-03-2020(online)].pdf | 2020-03-23 |
| 17 | 3560-MUM-2014-Information under section 8(2) [24-03-2020(online)].pdf | 2020-03-24 |
| 17 | 3560-MUM-2014-FORM 18.pdf | 2018-08-11 |
| 18 | 3560-MUM-2014-Power of Attorney-200115.pdf | 2018-08-11 |
| 18 | 3560-MUM-2014-OTHERS [16-04-2020(online)].pdf | 2020-04-16 |
| 19 | 3560-MUM-2014-FER_SER_REPLY [16-04-2020(online)].pdf | 2020-04-16 |
| 19 | FIGURES PD013747IN-SC.pdf | 2018-08-11 |
| 20 | 3560-MUM-2014-COMPLETE SPECIFICATION [16-04-2020(online)].pdf | 2020-04-16 |
| 20 | FORM 3 PD013747IN-SC.pdf | 2018-08-11 |
| 21 | 3560-MUM-2014-CLAIMS [16-04-2020(online)].pdf | 2020-04-16 |
| 21 | FORM 5 PD013747IN-SC.pdf | 2018-08-11 |
| 22 | 3560-MUM-2014-US(14)-HearingNotice-(HearingDate-25-10-2023).pdf | 2023-09-29 |
| 22 | SPEC FOR FILING PD013747IN-SC.pdf | 2018-08-11 |
| 23 | 3560-MUM-2014-Correspondence to notify the Controller [11-10-2023(online)].pdf | 2023-10-11 |
| 23 | REQUEST FOR CERTIFIED COPY [09-12-2015(online)].pdf | 2015-12-09 |
| 24 | 3560-MUM-2014-FORM-26 [23-10-2023(online)].pdf | 2023-10-23 |
| 24 | Description(Complete) [11-11-2014(online)].pdf | 2014-11-11 |
| 25 | Drawing [11-11-2014(online)].pdf | 2014-11-11 |
| 25 | 3560-MUM-2014-Written submissions and relevant documents [06-11-2023(online)].pdf | 2023-11-06 |
| 26 | Form 3 [11-11-2014(online)].pdf | 2014-11-11 |
| 26 | 3560-MUM-2014-PatentCertificate13-11-2023.pdf | 2023-11-13 |
| 27 | Form 5 [11-11-2014(online)].pdf | 2014-11-11 |
| 27 | 3560-MUM-2014-IntimationOfGrant13-11-2023.pdf | 2023-11-13 |
| 1 | TPOSEARCH_15-10-2019.pdf |