Platform for adopting settings to secure a protected file

Patent metadata

Field	Value
Publication number	US-10157286-B2
Application number	US-201514975567-A
Country	US
Kind code	B2
Filing date	Dec 18, 2015
Priority date	Aug 5, 2015
Publication date	Dec 18, 2018
Grant date	Dec 18, 2018

Abstract

Aspects of the present invention provide the ability to enforce access methods on data based upon a policy or policies identified within the metadata of a file. The data is self-protected by including or being wrapped with one or more policy/rule identifiers that act as a form of body armor to the data when in transit or in different situations. In embodiments, access is only granted upon successful authentication and compliance with the identified policy or policies. In embodiments, depending upon the conditions and policies, varying level access may be granted. In embodiments, depending upon the conditions and policies, the system may take one or more mitigations or remedial access levels, such as containerizing, sandboxing, granting limited access, or erasing the data.

First claim

What is claimed is:

1. A computer-implemented method for controlling security of a computing device, the method comprising:
responsive to a protected file comprising a payload in an encrypted format and metadata being stored in a memory on the computing device, accessing the metadata of the protected file, the metadata comprising information related to one or more policies regarding security for accessing the payload of the protected file, the metadata further comprising a set of operations in a set order that is associated with one or more extensible content transformation modules, the one or more extensible content transformation modules providing one or more extensible transformative capabilities that are used by a secure data format processor according to the set order to decode the encrypted payload into a user-accessible format;
gathering computing device configuration data and situational data relevant to the one or more policies using one or more components of the computing device;
determining whether the computing device is able to be placed into an appropriate security configuration based upon applying at least some of the computing device configuration data and the situational data to the one or more policies regarding security for accessing the payload; and
responsive to the computing device being able to be placed into the appropriate security configuration, using a trusted platform module that interfaces with one or more components of the computing device to alter one or more configuration settings of the one or more components of the computing device to apply the appropriate security configuration to allow access to contents of the payload.

2. The computer-implemented method of claim 1 wherein the trusted platform module is a root-of-trust module that sets one or more configuration settings in the computing device that are always trusted by an operating system of the computing device.

3. The computer-implemented method of claim 1 wherein the step of gathering computing device configuration data and situational data relevant to the one or more policies using one or more components of the computing device comprises:
collecting, as indicated by the one or more policies, data comprising at least one or more of clock data, location data, BIOS data, operating system data, file system data, network data, connectivity data, security features data, user data, authentication data, user privileges data, software data of the computing device, and hardware data of the computing device.

4. The computer-implemented method of claim 1 wherein the trusted platform module operates in a run-time implementation mode.

5. The computer-implemented method of claim 1 wherein the steps of claim 1 are performed as part of a boot-up procedure of the computing device.

6. The computer-implemented method of claim 5 further comprising:
responsive to the computing device not being able to be placed into at least one appropriate security configuration, not allowing the computing device to complete the boot-up procedure.

7. The computer-implemented method of claim 2 wherein the one or more components with which the trusted platform module interfaces are hardware components, firmware components, or both.

8. The computer-implemented method of claim 7 further comprising:
responsive to the computing device not being able to be placed into an appropriate security configuration, using the trusted platform module that interfaces with one or more components of the computing device to alter one or more configuration settings of the one or more components of the computing device to disable or not enable one or more functions of the computing device.

9. The computer-implemented method of claim 8 wherein the step of disabling or not enabling one or more functions of the computing device comprises:
disabling one or more communication ports on the computing device to prevent data leaks of the protected file.

10. A system for adopting a configuration setting of a computing system to be consistent with a selected policy of a protected file, the system comprising:
a memory that stores the protected file, the protected file comprising a payload that has been encrypted and metadata, the metadata comprising information related to one or more policies regarding security of the payload and in which a policy corresponding to a set of configuration settings for the computing system, the metadata further comprising a set of operations in a set order;
an access control engine, communicatively coupled to a secure data format processor, that analyzes a current status of the computing system based upon the one or more policies and situational data received from one or more system components;
a policy/rules module, communicatively coupled to the access control engine that stores or acquires the one or more policies;
the secure data format processor that detects a presence of the protected file and coordinates selection and application of the selected policy responsive to the computing system being able to be placed into an appropriate security configuration corresponding to the selected policy, the selected policy indicating a set of configuration settings for the computing system;
a trusted platform module, communicatively coupled to the access control engine, that interfaces with one or more components of the computing system to alter one or more configuration settings of the one or more components according to the selected policy; and
one or more extensible content transformation modules, communicatively coupled to the secure data format processor via a security services component, that are associated with the set of operations included in the metadata and provide one or more extensible transformative capabilities to the secure data format processor, the one or more extensible transformative capabilities being used by the secure data format processor according to the set order to decode the encrypted payload into a user-accessible format.

11. The system of claim 10 wherein the trusted platform module comprises a root-of-trust platform for the computing system.

12. The system of claim 11 further comprising a system instrumentation module, communicatively coupled to the access control engine, that provides at least some of the situational data by collecting data relevant to the one or more policies.

13. The system of claim 11 further comprising an access environmental controls module, communicatively coupled to the access control engine, that provides at least some of the situational data by collecting data relevant to the one or more policies related to environmental conditions of the computing system.

14. The system of claim 11 wherein the selected policy is selected and applied as part of a boot-up procedure of the computing system.

15. The system of claim 14 wherein the selected policy comprises:
responsive to the computing system not being able to be placed into at least one appropriate security configuration to allow unencrypted access to the payload, not allowing the computing system to complete the boot-up procedure.

16. The system of claim 11 wherein the selected policy comprises:
disabling or not enabling one or more functions of the computing system as indicated by the selected policy.

17. A computing system for automatically altering its configuration to be consistent with one or more policies of a protected file stored on the computing system, the system comprising:
a memory that stores the protected file, the protected file comprising a payload in an encrypted format and metadata, the m

Assignees

• Dell Products Lp
• Dell Products Lp

Inventors

• Skipper Chad
• Lewis Elliot D
• Konetski David
• Burchett Christopher
• Schuckle Richard William
• Burke James Michael
• Robbins Warren Wade
• Gates Carrie Elaine

Classifications

• G06F21/604

  Tools and structures for managing or administering access control systems · CPC title

• H04L63/10

  for controlling access to devices or network resources · CPC title

• G06F21/6209 Primary

  to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself · CPC title

• H04L63/20

  for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title