Tagging and auditing sensitive information in a database environment
Access to sensitive information in a database can be restricted to improve security and enable efficient auditing. A security engine receives a request from a requesting entity to access data in the database and determines that the requested data includes sensitive information. In response to the requesting entity being authorized to access the data, the security engine retrieves the requested data from the database and modifies the retrieved data by modifying metadata of the retrieved data to include a tag indicating that the retrieved data includes sensitive information. The security engine provides the modified data to the requesting entity and modifies a data access log to identify each attempted access to the modified data. When sensitive data is requested, an interface can include an obscuring element, requiring a user to manually select the element to view the data, enabling the logging of the explicit access request by the user.
1. A method of restricting a display of data comprising:
displaying, by a security engine, an interface on a client device of a requesting entity for displaying sensitive information in a field of the interface, the interface including an interface element that obscures the field, wherein the client device accesses information for display within the interface from a database that includes sensitive flags indicating columns of sensitive information, wherein a first portion of the information not including sensitive flags is provided to the client device for display within the interface, and wherein a second portion of the information including sensitive flags is not provided to the client device;
after displaying the interface on the client device, receiving, by the security engine, a request from the requesting entity to view the sensitive information within the field obscured by the interface element; and
after receiving the request to view the sensitive information and in response to determining that the requesting entity is authorized to view the sensitive information:
accessing, by the security engine, the sensitive information from the database;
after the sensitive information is accessed, removing, by the security engine, the interface element, wherein the field is no longer obscured when the interface element is removed; and
displaying the sensitive information within the field of the interface displayed by the client device.
2. The method of claim 1 , further comprising:
accessing, by the security engine, non-sensitive information from the database; and
displaying in the interface, by the security engine, the non-sensitive information within a corresponding non-sensitive data field of the interface.
3. The method of claim 1 , further comprising modifying, by the security engine, a data access log to identify the request to view the sensitive information, the modified data access log identifying the requesting entity, the sensitive information, and a time associated with the request to view the sensitive information.
4. The method of claim 3 , further comprising in response to determining that the requesting entity is not authorized to view the sensitive information, initiating by the security engine, an audit of the modified data access log.
5. The method of claim 3 , wherein the modified data access log further includes information representative of at least one of:
a user account associated with the requesting entity,
a hardware device used by the requesting entity to access the sensitive information in the database,
a software application used by the requesting entity to access the sensitive information in the database, and
an indication of whether a request to view the sensitive information was granted.
6. The method of claim 3 , wherein the modified data access log includes information identifying the interface.
7. The method of claim 3 , wherein the modified data access log further includes information identifying sensitive data fields located within the interface.
8. The method of claim 1 , further comprising:
in response to determining that the requesting entity is not authorized to view the sensitive information, displaying a message in the interface indicating that the requesting entity is not authorized to view the sensitive information.
9. The method of claim 8 , wherein the sensitive information is not accessed from the database in response to determining that the requesting entity is not authorized to view the sensitive information.
10. The method of claim 1 , wherein the interface element comprises an opaque or semi-opaque box obscuring the field corresponding to the sensitive information.
11. A non-transitory computer readable storage medium storing executable instructions that, when executed by one or more processors, cause the one or more processors to perform steps comprising:
displaying, by a security engine, an interface on a client device of a requesting entity for displaying sensitive information in a field of the interface, the interface including an interface element that obscures the field, wherein the client device accesses information for display within the interface from a database that includes sensitive flags indicating columns of sensitive information, wherein a first portion of the information not including sensitive flags is provided to the client device for display within the interface, and wherein a second portion of the information including sensitive flags is not provided to the client device;
after displaying the interface on the client device, receiving, by the security engine, a request from the requesting entity to view the sensitive information within the field obscured by the interface element; and
after receiving the request to view the sensitive information and in response to determining that the requesting entity is authorized to view the sensitive information:
accessing, by the security engine, the sensitive information from the database;
after the sensitive information is accessed, removing, by the security engine, the interface element, wherein the field is no longer obscured when the interface element is removed; and
displaying the sensitive information within the field of the interface displayed by the client device.
12. The non-transitory computer readable storage medium of claim 11 , wherein the instructions, when executed, cause the one or more processors to perform additional steps comprising:
accessing, by the security engine, non-sensitive information from the database; and
displaying in the interface, by the security engine, the non-sensitive information within a corresponding non-sensitive data field of the interface.
13. The non-transitory computer readable storage medium of claim 11 , wherein the instructions, when executed, cause the one or more processors to perform additional steps comprising modifying, by the security engine, a data access log to identify the request to view the sensitive information, the modified data access log identifying the requesting entity, the sensitive information, and a time associated with the request to view the sensitive information.
14. The non-transitory computer readable storage medium of claim 13 , wherein the instructions, when executed, cause the one or more processors to perform additional steps comprising in response to determining that the requesting entity is not authorized to view the sensitive information, initiating by the security engine, an audit of the modified data access log.
15. The non-transitory computer readable storage medium of claim 13 , wherein the modified data access log further includes information representative of at least one of:
a user account associated with the requesting entity,
a hardware device used by the requesting entity to access the sensitive information in the database,
a software application used by the requesting entity to access the sensitive information in the database, and
an indication of whether a request to view the sensitive information was granted.
16. The non-transitory computer readable storage medium of claim 13 , wherein the modified data access log includes information identifying the interface.
17. The non-transitory computer readable storage medium of claim 13 , wherein the modified data access log further includes information identifying sensitive data fields located within the interface.
18. The non-transitory computer readable storage medium of claim 11 , wherein the instructions, when executed, cause the one or more processors to perform additional steps comprising:
in response to determining that the requesting entity is not authorized to view the sensitive information, displaying a message in the interface indicating that the requesting entity is not authorized to view the sensitive information.
19. The non-transitory computer readable storage medium of claim 18 , wherein the sensitive information is not accessed from the database in response to determining that the requesting entity is not authorized to view the sensitive information.
20. The non-transitory computer readable storage medium of claim 11 , wherein the interface element comprises an opaque or semi-opaque box obscuring the field corresponding to the sensitive information.