IP Library Granted Patent US 10,089,482
Granted Patent B2
US 10,089,482 · App. 14/975,474 · Granted Oct 2, 2018

Enforcement mitigations for a protected file

Inventors: Chad Skipper (Granger, TX); Elliot D. Lewis (Henderson, NV); David Konetski (Austin, TX); Christopher Burchett (Lewisville, TX); Richard William Schuckle (Austin, TX); James Michael Burke (Frisco, TX); Warren Wade Robbins (Celina, TX); Carrie Elaine Gates (Livermore, CA)
Assignee: DELL PRODUCTS LP
G06F21/6209G06F21/604H04L63/10H04L63/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,089,482
App. No.
14/975,474
Filed
Dec 18, 2015
Granted
Oct 2, 2018
Kind
B2
Art Unit
2438
USPC
726/1
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.

Claims (56)

1. A computer-implemented method for accessing a file on a computing device, the method comprising:

receiving a request to access a payload of the file, the file comprising the payload in an encrypted format and metadata, the metadata comprising information related to one or more policies regarding one or more enforcement mitigations under which usable access to the payload is granted and mitigates security risks to the payload and which granting access to the payload via an enforcement mitigation is determined by the computing device independent of any third-party computing device, 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;

using one or more components of the computing device to obtain situational data about the file that is relevant to the one or more policies;

applying at least one or more data of the situational data to the one or more policies to identify one or more enforcement mitigations that are available to be used to grant usable access to the payload; and

granting, via the computing device, usable access to the payload using at least one of the identified enforcement mitigations.

2. The computer-implemented method of claim 1 wherein the step of using one or more components of the computing device to obtain situational data about the file that is relevant to the one or more policies comprises:

collecting one or more situational data as indicated by the one or more policies, the situational 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.

3. The computer-implemented method of claim 1 wherein the metadata comprising the information related to one or more policies regarding one or more enforcement mitigations under which access to the payload in an unencrypted format is granted and mitigates security risks to the payload comprises:

the one or more policies or one or more identifiers for accessing the one or more policies from a policy dataset.

4. The computer-implemented method of claim 3 further comprising:

obtaining from a data storage the one or more policies.

5. The computer-implemented method of claim 4 wherein the step of obtaining from a data storage the one or more policies comprises:

obtaining the one or more policies from the metadata of the file, from a policy dataset, or both.

6. The computer-implemented method of claim 5 wherein the policy dataset is obtained from at least one of:

a policy module on the computing device; and

a secure data access system management server that is communicatively coupled to the computing device.

7. The computer-implemented method of claim 1 wherein:

the step of applying at least one or more data of the situational data to the one or more policies to identify one or more enforcement mitigations that are available to be used to grant usable access to the payload comprises determining that no access is appropriate given the situational data and the one or more policies associated with the file; and

the step of granting, via the computing device, usable access to the payload using at least one of the identified enforcement mitigations comprises not granting access to the payload in the unencrypted format.

8. The computer-implemented method of claim 1 wherein the step of granting, via the computing device, usable access to the payload using at least one of the identified enforcement mitigations further comprising:

taking one or more actions, according to the at least one of the identified enforcement mitigations, to affect one or more conditions of the computing device to increase security for accessing the payload.

9. The computer-implemented method of claim 8 further comprising:

responsive to the payload comprising a nested payload and additional metadata identifying one or more additional policies related to conditions under which access are available to be granted to the nested payload, analyzing the one or more additional policies;

collecting, if needed for the one or more additional policies, additional situational data relevant to the one or more additional policies; and

applying at least one or more data of the situational data, additional situational data, or both to the one or more additional policies to identify one or more enforcement mitigations that are available to be used to grant access to the nested payload.

10. A system for applying an enforcement mitigation for accessing 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 one or more enforcement mitigations under which usable access to the payload is granted and which granting access to the payload via an enforcement mitigation is determined by the system independent of any third-party computing device, the metadata further comprising a set of operations in a set order;

a secure data format processor that coordinates system components to determine which of one or more enforcement mitigations are available for the protected file and applies an identified enforcement mitigation;

an access control engine that is communicatively coupled to the secure data format processor and identifies one or more enforcement mitigations that are appropriate based, at least in part, upon applying a set of situational data regarding the protected file to the one or more policies;

one or more extensible content transformation modules, communicatively coupled to the secure data format processor 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 transformative capabilities being used by the secure data format processor according to the set order as identified in the metadata to decode the payload into a usable format;

a policy/rules module, communicatively coupled a secure data access system management server and to the access control engine, that stores or acquires the one or more policies; and

an access environmental controls module, communicatively coupled to the access control engine, that applies one or more access control directives of the one or more enforcement mitigations determined to be appropriate by the access control engine for granting usable access to the payload.

11. The system of claim 10 wherein the set of situational data regarding the protected file comprises a set of access controls available on the system which are received by the access controls engine from the access environmental controls module.

12. The system of claim 11 wherein the access control engine identifies the one or more enforcement mitigations that are appropriate based, at least in part, upon applying a set of situational data regarding the protected file by performing the steps comprising:

obtaining the set of situational data regarding the protected file comprising the set of access controls from the access environmental controls module that are available for the system;

determining the one or more enforcement mitigations that are appropriate for the system based, at least in part, on the set of situational data; and

providing the one or more access control directives to the access environmental controls module to apply an appropriate security for granting usable access to the payload.

13. The system of claim 11 wherein the one or more access control directives comprises:

responsive to the system having a level of security below a first threshold, granting usable access via a secure browser to a copy of the payload stored at a secure datacenter.

14. The system of claim 11 wherein the one or more access control directives comprises:

responsive to the system having a level of security below a second threshold, granting usable access to the payload via a container on the system so that the payload is contained within an environment to prevent data leaks.

15. The system of claim 11 wherein the one or more access control directives comprises:

responsive to the system not meeting a minimum threshold level of security, having the system destroy the protected file.

16. A non-transitory computer-readable medium or media comprising one or more sequences of instructions which, when executed by at least one processor of a computing device, causes steps to be performed for providing one or more of a plurality of access levels to a protected file, the steps comprising:

receiving a request to access a payload of the file, the file comprising the payload in an encrypted format and metadata, the metadata comprising information related to one or more policies regarding one or more enforcement mitigations under which usable access to the payload is granted and mitigates security risks to the payload and which granting access to the payload via an enforcement mitigation is determined by the computing device independent of any third-party computing device, 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

using one or more components of the computing device to obtain situational data about the file that is relevant to the one or more policies;

applying at least one or more data of the situational data to the one or more policies to identify one or more enforcement mitigations that are available to be used to grant usable access to the payload; and

granting, via the computing device, usable access to the payload using at least one of the identified enforcement mitigations.

17. The non-transitory computer-readable medium or media of claim 16 wherein the step of using one or more components of the computing device to obtain situational data about the file that is relevant to the one or more policies comprises:

collecting one or more situational data as indicated by the one or more policies, the situational 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.

18. The non-transitory computer-readable medium or media of claim 16 wherein:

the step of applying at least some of the situational data to the one or more policies to identify one or more enforcement mitigations that are available to be used to grant usable access to the payload comprises determining that no access is appropriate given the situational data and the one or more policies associated with the file; and

the step of granting, via the computing device, usable access to the payload using at least one of the identified enforcement mitigations comprises not granting access to the payload in the unencrypted format.

19. The non-transitory computer-readable medium or media of claim 16 wherein the step of granting, via the computing device, usable access to the payload using at least one of the identified enforcement mitigations further comprising:

taking one or more actions, according to the at least one of the identified enforcement mitigations, to affect one or more conditions of the computing device to increase security for accessing the payload.

20. The computer-implemented method of claim 1 , wherein, responsive to the computing device not having a transformative capability identified in the set of operations in the metadata, obtaining an extensible content transformation module that provides the transformative capability, in which the secure data format processor verifies that the extensible content transformation module is a trusted module.

Assignments (15)
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (053546/0001) Recorded Jun 23, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC IP HOLDING COMPANY LLC
Reel/Frame 071642/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001) Recorded May 20, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061753/0001 →
RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001) Recorded Apr 26, 2022
From: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
To: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.); DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.); DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL PRODUCTS L.P.; DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.); EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC); EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.); SCALEIO LLC
Reel/Frame 061324/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 3, 2021
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH
To: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL, L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; WYSE TECHNOLOGY L.L.C.
Reel/Frame 058216/0001 →
SECURITY AGREEMENT Recorded Apr 22, 2020
From: CREDANT TECHNOLOGIES INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 053546/0001 →
SECURITY AGREEMENT Recorded Mar 21, 2019
From: CREDANT TECHNOLOGIES, INC.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL USA L.P.; EMC CORPORATION; FORCE10 NETWORKS, INC.; WYSE TECHNOLOGY L.L.C.; EMC IP HOLDING COMPANY LLC
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.
Reel/Frame 049452/0223 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 040134/0001 →
SECURITY AGREEMENT Recorded Sep 21, 2016
From: ASAP SOFTWARE EXPRESS, INC.; AVENTAIL LLC; CREDANT TECHNOLOGIES, INC.; DELL USA L.P.; DELL INTERNATIONAL L.L.C.; DELL MARKETING L.P.; DELL PRODUCTS L.P.; DELL SOFTWARE INC.; DELL SYSTEMS CORPORATION; EMC CORPORATION; EMC IP HOLDING COMPANY LLC; FORCE10 NETWORKS, INC.; MAGINATICS LLC; MOZY, INC.; SCALEIO LLC; SPANNING CLOUD APPS LLC; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 040136/0001 →
RELEASE OF REEL 037848 FRAME 0001 (TL) Recorded Sep 14, 2016
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040028/0152 →
RELEASE OF REEL 037848 FRAME 0210 (NOTE) Recorded Sep 14, 2016
From: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040031/0725 →
RELEASE OF REEL 037847 FRAME 0843 (ABL) Recorded Sep 13, 2016
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; WYSE TECHNOLOGY L.L.C.
Reel/Frame 040017/0366 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 18, 2016
From: SKIPPER, CHAD; LEWIS, ELLIOT D; KONETSKI, DAVID; BURCHETT, CHRISTOPHER; SCHUCKLE, RICHARD WILLIAM; BURKE, JAMES MICHAEL; ROBBINS, WARREN WADE; GATES, CARRIE ELAINE
To: DELL PRODUCTS L.P.
Reel/Frame 038036/0642 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL) Recorded Feb 18, 2016
From: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; WYSE TECHNOLOGY L.L.C.
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 037847/0843 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN) Recorded Feb 18, 2016
From: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; WYSE TECHNOLOGY L.L.C.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037848/0001 →
SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES) Recorded Feb 18, 2016
From: DELL SOFTWARE INC.; DELL PRODUCTS L.P.; WYSE TECHNOLOGY L.L.C.
To: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT
Reel/Frame 037848/0210 →
Continuity (2)
Continuation 14819322 · Aug 5, 2015
Related Publication 20170039378A1 · Feb 9, 2017
Cited By (1)
US 12,682,249