Kernel level application data protection

1. A system for web application security through containerization, the system comprising:

a client device comprising at least one processor; and

a data store comprising executable instructions, wherein the instructions, when executed by the at least one processor, cause the client device to at least:

transmit, by a container application to a management service accessed over a network, an identifier of a protected application that is loaded in a container of the container application;

receive, by the container application, in response to transmitting the identifier of the protected application to the management service, a security label for the protected application, and a list of permitted applications that are allowed to access files originated by the protected application, wherein the container application uses the security label to identify and protect the files originated by the protected application;

write a security label map within a kernel layer of the client device, the security label map comprising: the security label, and the list of permitted applications;

generate, by the container application, a secured file by embedding the security label within a file originated by the protected application;

intercept, by kernel-level management instructions, a file access system call to access the secured file;

determine, by the kernel-level management instructions, an application identity for an application that invokes the file access system call; and

permit or deny, by the kernel-level management instructions, access to the secured file based on a comparison of the application identity with the list of permitted applications within the security label map.

2. The system of claim 1 , wherein the container application calls a function that writes the security label map, wherein the function is exposed by a user driver within the kernel layer.

3. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the client device to at least:

install the protected application on the client device, wherein the security label and the list of permitted applications are received based on the protected application being installed on the client device.

4. The system of claim 1 , wherein the security label is uniquely associated with the protected application.

5. The system of claim 1 , wherein the security label is embedded within an inode table.

6. The system of claim 1 , wherein the kernel-level management instructions permit access to the secured file by passing the file access system call to an inter-process communication mechanism.

7. The system of claim 1 , wherein the kernel-level management instructions deny access to the secured file by preventing the file access system call from being passed to an inter-process communication mechanism.

8. A method performed by instructions executed by a client device, the method comprising:

transmitting, by a container application to a management service accessed over a network, an identifier of a protected application that is loaded in a container of the container application;

receiving, by the container application, in response to transmitting the identifier of the protected application to the management service, a security label for the protected application, and a list of permitted applications that are allowed to access files originated by the protected application, wherein the container application uses the security label to identify and protect the files originated by the protected application;

writing a security label map within a kernel layer of the client device, the security label map comprising: the security label, and the list of permitted applications;

generating, by the container application, a secured file by embedding the security label within a file originated by the protected application;

intercepting, by kernel-level management instructions, a file access system call to access the secured file;

determining, by the kernel-level management instructions, an application identity for an application that invokes the file access system call; and

permitting or denying, by the kernel-level management instructions, access to the secured file based on a comparison of the application identity with the list of permitted applications within the security label map.

9. The method of claim 8 , wherein the container application calls a function that writes the security label map, wherein the function is exposed by a user driver within the kernel layer.

10. The method of claim 8 , further comprising:

installing the protected application on the client device, wherein the security label and the list of permitted applications are received based on the protected application being installed on the client device.

11. The method of claim 8 , wherein the security label is uniquely associated with the protected application.

12. The method of claim 8 , wherein the security label is embedded within an inode table.

13. The method of claim 8 , wherein the kernel-level management instructions permit access to the secured file by passing the file access system call to an inter-process communication mechanism.

14. The method of claim 8 , wherein the kernel-level management instructions deny access to the secured file by preventing the file access system call from being passed to an inter-process communication mechanism.

15. A non-transitory computer-readable medium comprising executable instructions, wherein the instructions, when executed by at least one processor, cause a client device to at least:

transmit, by a container application to a management service accessed over a network, an identifier of a protected application that is loaded in a container of the container application;

receive, by the container application, in response to transmitting the identifier of the protected application to the management service, a security label for the protected application, and a list of permitted applications that are allowed to access files originated by the protected application, wherein the container application uses the security label to identify and protect the files originated by the protected application;

generate, by the container application, a secured file by embedding the security label within a file originated by the protected application;

write a security label map within a kernel layer of the client device, the security label map comprising: the security label, and the list of permitted applications;

intercept, by kernel-level management instructions, a file access system call to access the secured file;

determine, by the kernel-level management instructions, an application identity for an application that invokes the file access system call; and

permit or deny, by the kernel-level management instructions, access to the secured file based on a comparison of the application identity with the list of permitted applications within the security label map.

16. The non-transitory computer-readable medium of claim 15 , wherein the container application calls a function that writes the security label map, wherein the function is exposed by a user driver within the kernel layer.

17. The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the client device to at least:

install the protected application on the client device, wherein the security label and the list of permitted applications are received based on the protected application being installed on the client device.

18. The non-transitory computer-readable medium of claim 15 , wherein the security label is uniquely associated with the protected application.

19. The non-transitory computer-readable medium of claim 15 , wherein the security label is embedded within an inode table.

20. The non-transitory computer-readable medium of claim 15 , wherein the kernel-level management instructions permit access to the secured file by passing the file access system call to an inter-process communication mechanism.