DIVIDING A DATA PROCESSING DEVICE INTO SEPARATE SECURITY DOMAINS

• US 20180302443A1
• Filed: 05/25/2018
• Published: 10/18/2018
• Est. Priority Date: 08/02/2012
• Status: Active Grant

• Current Assignee: Pulse Secure, LLC (Ivanti Software, Inc.)
• Original Assignee: Cellsec, Inc. (Ivanti Software, Inc.)
• Inventors: Weiss, Yoav, Goldschlag, David, Ginter, Karl, Bartman, Michael
• Granted Patent: US 10,305,937 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/74 operating in dual or compartmented mode, i.e. at least one secure mode
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

This invention provides secure, policy-based separation of data and applications on computer, especially personal computers that operate in different environments, such as those including personal applications and corporate applications, so that both types of applications can run simultaneously while complying with all required policies. The invention enables employees to use their personal devices for work purposes, or work devices for personal purposes. The secure, policy-based separation is created by dividing the data processing device into two or more “domains,” each with its own policies. These policies may be configured by the device owner, an IT department, or other data or application owner.

Claims

1-18. -18. (canceled)

19. A method for operating a computer data processing device in two or more data security domains, comprising:

providing in data memory associated with said computer data processing device at least on external policy defining a first domain;

associating a first computer data processing device application with said first domain;

providing a persistent control mechanism, said persistent control mechanism being bound to said application and implemented externally to said operating system, said persistent control mechanism being configured to intercept and mediate requests between the application and the operating system in accordance with specifications contained within the policies of said first domain without modifying said application and without requiring operating system privileges, over said computer data processing device application associated with said first domain, said persistent control mechanism being subject to policies defined for said first domain, and said persistent control mechanism being located logically between said first data processing device application and said operating system;

receiving an application request at said persistent control mechanism;

processing said application request by said persistent control mechanism, said persistent control mechanism determining how to process said application request using one or more of;

an aspect of the domain of the requesting application, the domain the data belongs to, and the policies for the application and data domains; and

responding to said application request by said persistent control mechanism by either blocking said request completely, modifying at leant one aspect of a requested operation before permitting the modified operation to proceed, or redirecting said request to a different function.

20. The method of claim 19, further comprising loading said persistent control mechanism substantially at the time of initial device software loading, or installing said persistent control mechanism on said device at a time subsequent to the initial device software load.

21. The method of claim 19, further comprising integrating said persistent control mechanism with the operating system of said device, integrating said persistent control mechanism with said application, or installing said persistent control mechanism as part of or bound with said application.

22. The method of claim 19, further comprising associating said persistent control mechanism with a structure in the operating system designed to support pluggable mediation modules.

23. The method of claim 19, further comprising registering said persistent control mechanism with said operating system of said device and receiving an operating system call at said persistent control mechanism.

24. The method of claim 23, further comprising passing said operating system call from said persistent control mechanism as necessary.

25. The method of claim 23, wherein said operating system uses vector hooking, and said persistent control mechanism responds to said request by blocking the request, passing the request to the original operating system function specified by said request, modifying the request before passing it to the original operating system function specified by said request, redirecting said request, or modifying said request and then redirecting said request, to a different operating system function.

26. The method of claim 24, wherein said operating system and said application use a shared memory region for communication between said application and services provided by said operating system, and said method further comprises replacing that portion of the operating system service that receives notification of requests, or which reads requests from a shared memory buffer, or both, with a portion of said request mediation module.

27. The method of claim 19, further comprising providing a second persistent control mechanism, said second persistent control mechanism being bound to said application and implemented externally to said operating system, said second persistent control mechanism being configured to intercept and mediate requests between the application and the operating system in accordance with specifications contained within the policies of said first domain without modifying said application and without requiring operating system privileges, over said computer data processing device application associated with said first domain, said second persistent control mechanism being subject to policies defined for said first domain, and said second persistent control mechanism being located logically between said first data processing device application and said operating system;

receiving an application request at said second persistent control mechanism;

processing said application request by said second persistent control mechanism, said second persistent control mechanism determining how to process said application request using one or more of;

an aspect of the domain of the requesting application, the domain the data belongs to, and the policies for the application and data domains; and

responding to said application by said second persistent control mechanism by either blocking the request completely, modifying at least one aspect of a requested operation before permitting the modified operation to proceed, or redirecting said request to a different function.

28. A computer data processing system including two or more electronically encoded data security domains, said system comprising:

electronic computer memory in electronic communication with said computer data processing device, said electronic computer memory holding in electronic encoded format at least one external policy defining a first domain;

a first computer data processing device application encoded in in electronic data memory associated with said first domain and operating under electronic computer control;

a persistent control mechanism in electronic format in electronic memory and operating under electronic computer control, said persistent control mechanism being bound to said application and Implemented to operate electronically externally to said operating system, said persistent control mechanism being configured to intercept and mediate requests between the application and the operating system in accordance with specifications contained within the policies of said first domain without modifying said application and without requiring operating system privileges, over said computer data processing device application associated with said first domain, said persistent control mechanism being subject to pollicies defined for said first domain, and said persistent control mechanism being located logically between said first data processing device application and said operating system;

said persistent control mechanism being further implemented to receive electronically encoded application requests and process said electronically encoded application requests under electronic computer control, including determining how to process said application request using one or more of;

an aspect of the domain of the requesting application, the domain the data belongs to, and the policies for the application and data domains; and

said persistent control mechanism responding electronically to said application request under electronic computer control by either blocking said request completely, modifying at least one aspect of a requested operation before permitting the modified operation to proceed, or redirecting said request to a different function.

29. The system of claim 28, wherein said persistent control mechanism is electronically encoded to be loaded at substantially at the time of initial device software loading, or installing said persistent control mechanism on said device at a time subsequent to the initial device software load.

30. The system of claim 28, wherein said persistent control mechanism is electronically encoded to be integrated with the operating system of said device, with said application, or installed as part of or bound with said application.

31. The system of claim 28, wherein said is electronically encoded to be associated with a structure in the operating system designed to support pluggable mediation modules.

32. The system of claim 28, wherein said persistent control mechanism is electronically encoded to be registered with said operating system of said device and receiving an operating system call at said persistent control mechanism.

33. The system of claim 32, wherein said persistent control mechanism is electronically encoded to pass said operating system call as necessary.

34. The system of claim 32, wherein said operating system uses vector hooking, and said persistent control mechanism is electronically encoded to respond to said request by blocking the request, passing the request to the original operating system function specified by said request, modifying the request before passing it to the original operating system function specified by said request, redirecting said request, or modifying said request and then redirecting raid request, to a different operating system function.

35. The system of claim 33, wherein said operating system and said application use a shared memory region for communication between said application and services provided by said operating system, and said persistent control mechanism is further electronically encoded to replace that portion of the operating system service that receives notification of requests, or which read requests from a shared memory buffer, or both, with a portion of said request mediation module.

36. The system of claim 28, further comprising a second persistent control mechanism in electronic format in electronic memory and operating under electronic computer control, said second persistent control mechanism being bound to said application and implemented to operate electronically externally to said operating system, said second persistent control mechanism being configured to intercept and mediate requests between the application and the operating system in accordance with specifications contained within the policies of said first domain without modifying said application and without requiring operating system privileges, over said computer data processing device application associated with said first domain, said second persistent control mechanism being subject to policies defined for said first domain, and said second persistent control mechanism being located logically between said first data processing device application and said operating system;

said second persistent control mechanism being further implemented to receive electronically encoded application requests and process said electronically encoded application requests under electronic computer control, including determining how to process said application request using one or more of;

an aspect of the domain of the requesting application, the domain the data belongs to, and the policies for the application and data domains; and

said second persistent control mechanism responding electronically to said application request under electronic computer control by either blocking said request completely, modifying at least one aspect of a requested operation before permitting the modified operation to proceed, or redirecting said request to a different function.

37. A non-transitory computer-readable medium containing a computer program product for operating a computer data processing device, said computer program product being configured to enable said computer data processing device to operate securely in two or more data security domains, said computer program product being configured to enable said computer data processing device to perform actions comprising:

providing in data memory associated with said computer data processing device at least one external policy defining a first domain;

associating a first computer data processing device application with said first domain;

providing a persistent control mechanism, said persistent control mechanism being bound to said application and implemented externally to said operating system, said persistent control mechanism being configured to intercept and mediate requests between the application and the operating system in accordance with specifications contained within the policies of said first domain without modifying said application and without requiring operating system privileges, over said computer data processing device application associated with said first domain, said persistent control mechanism being subject to policies defined for said first domain, and said persistent control mechanism being located logically between said first data processing device application and said operating system;

receiving an application request as said persistent control mechanism;

processing said application request by said persistent control mechanism, said persistent control mechanism determining how to process said application request using one or more of;

an aspect of the domain of the requesting application, the domain the data belongs to, and the policies for the application and data domains; and

responding to said application request by said persistent control mechanism by either blocking said request completely, modifying at least one aspect of a requested operation before permitting the modified operation to proceed, or redirecting said request to a different function.

38. The non-transitory computer-readable medium of claim 37, further comprising loading said persistent control mechanism substantially at the time of initial device software loading, or installing said persistent control mechanism on said device at a time subsequent to the initial device software load.

39. The non-transitory computer-readable medium of claim 37, further comprising integrating said persistent control mechanism with the operating system of said device, integrating said persistent control mechanism with said application, or installing said persistent control mechanism as part of or bound with said application.

40. The non-transitory computer-readable medium of claim 37, further comprising associating said persistent control mechanism with a structure in the operating system designed to support pluggable mediation modules.

41. The non-transitory computer-readable medium of claim 37, further comprising registering said persistent control mechanism with said operating system of said device and receiving an operating system call at said persistent control mechanism.

42. The non-transitory computer-readable medium of claim 41, further comprising passing said operating system call from said persistent control mechanism as necessary.

43. The non-transitory computer-readable medium of claim 41, wherein said operating system uses vector hooking, and said persistent control mechanism responds to said request by blocking the request, passing the request to the original operating system function specified by said request, modifying the request before passing it to the original operating system function specified by said request, redirecting said request, or modifying said request and then redirecting said request, to a different operating system function.

44. The non-transitory computer-readable medium of claim 42, wherein said operating system and said application use a shared memory region for communication between said application and services provided by said operating system, and said non-transitory computer-readable medium further comprises replacing that portion of the operating system service that receives notification of requests, or which reads requests from a shared memory buffer, or both, with a portion of said request mediation module.

45. The non-transitory computer-readable medium of claim 37, further comprising providing a second persistent control mechanism, said second persistent control mechanism being bound to said application and implemented externally to said operating system, said second persistent control mechanism being configured to intercept and mediate requests between the application and the operating system in accordance with specifications contained within the policies of said first domain without modifying said application and without requiring operating system privileges, over said computer data processing device application associated with said first domain, said second persistent control mechanism being subject to policies defined for said first domain, and said second persistent control mechanism being located logically between said first data processing device application and said operating system;

receiving an application request at said second persistent control mechanism;

processing said application request by said second persistent control mechanism, said second persistent control mechanism determining how to process said application request using one or more of;

an aspect of the domain of the requesting application, the domain the data belongs to, and the policies for the application and data domains; and

responding to said application by said second persistent control mechanism by either blocking the request completely, modifying at least one aspect of a requested operation before permitting the modified operation to proceed, or redirecting said request to a different function.