IP Library Granted Patent US 12,488,126
Granted Patent B2
US 12,488,126 · App. 18/046,584 · Granted Dec 2, 2025

Methods for dynamic platform security configuration

Inventors: Bradley K. Goodman (Nashua, NH); Kirk Alan Hutchinson (Londonderry, NH); Joseph Caisse (Burlington, MA)
Assignee: Dell Products L.P.
G06F21/6218H04L9/14
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 12,488,126
App. No.
18/046,584
Filed
Oct 14, 2022
Granted
Dec 2, 2025
Kind
B2
Art Unit
2449
USPC
726/1
Abstract

Systems, devices, and methods for managing data processing systems are disclosed. The data processing systems may be capable of operating in various manners. To manage the data processing systems, onboarding processes may be performed to conform the operation of the data processing systems to meet the expectations of owners of the data processing systems. To manage security policies of the data processing systems during onboarding, ownership vouchers may be generated to provide data necessary for onboarding that defines security policies, hardware policies, and ownership of the data processing systems. The ownership voucher may be deployed to data processing systems during onboarding to reduce the likelihood of undesired use and/or interactions with the data processing systems.

Claims (68)

1 . A method for managing security of a data processing system, the method comprising:

deploying, by a management service, an initial security policy to the data processing system, the initial security policy comprising a public key of a first party and placing the data processing system into a first security state, the first party is a manufacturer of the data processing system, and the initial security policy secures the data processing system against compromise while in a channel of commerce;

generating, by the management service, an ownership voucher for the data processing system, the ownership voucher comprising:

a second security policy, the second security policy being signed and verifiable using the public key of the first party, the second security policy specifying a change from the first security state, and the second security policy being based on information regarding a security framework implemented by an owner of the data processing system,

a cryptographically verifiable delegation of authority over the data processing system to a second party, the cryptographically verifiable delegation comprising a public key of the second party, the second party is the owner of the data processing system after purchase from the channel of commerce, and the second security policy places the data processing system into compliance with the security framework implemented by the owner,

an ownership certificate indicating that the owner owns the data processing system,

a hardware certificate indicating configurations for hardware components of the data processing system,

credentials for the data processing system to allow the data processing system to join a domain indicated by the owner, and

a management agent that indicates a software component designated by the owner for the data processing system; and

deploying, by the management service and during an onboarding of the data processing system by the second party, the ownership voucher to the data processing system to update the data processing system into a second security state specified by a change from the first security state to place the data processing system in compliance with a security framework implemented by the second party.

2 . The method of claim 1 , wherein the first security state is hardened against attacks on the security of the data processing system, and the second security state is less restrictive than the first security state.

3 . The method of claim 1 , wherein the ownership voucher further comprises:

a third security policy, the third security policy being signed and verifiable using a public key of the second party, and the third security policy specifying a change from the second security state.

4 . The method of claim 3 , wherein the second security policy further comprises:

a public key of the second party.

5 . The method of claim 4 , wherein the public key of the second security policy delegates authority over changes in security policies implemented by the data processing system to the second party, and the public key of the second security policy requires that any changes to the second security state be signed by the second party and verifiable with the public key of the second security policy.

6 . The method of claim 1 , further comprising:

obtaining, by the management service, a second public key from the owner;

obtaining, by the management service, the information regarding the security framework implemented by the owner;

generating, by the management service and using the second public key and the information, the second security policy; and

generating, by the management service and using the second security policy, the ownership voucher.

7 . The method of claim 1 , wherein the initial security policy specifies:

a change in Extensible Firmware Interface (EFI) keys used to manage startup of the data processing system.

8 . The method of claim 1 , wherein the initial security policy authorizes a smaller number of types of boots for the data processing system than then the second security policy.

9 . A non-transitory machine-readable medium having instructions stored therein, which when executed by a processor, cause the processor to perform operations for managing security of a data processing system, the operations comprising:

deploying, by a management service, an initial security policy to the data processing system, the initial security policy comprising a public key of a first party and placing the data processing system into a first security state, the first party is a manufacturer of the data processing system, and the initial security policy secures the data processing system against compromise while in a channel of commerce;

generating, by the management service, an ownership voucher for the data processing system, the ownership voucher comprising:

a second security policy, the second security policy being signed and verifiable using the public key of the first party, the second security policy specifying a change from the first security state, and the second security policy being based on information regarding a security framework implemented by an owner of the data processing system,

a cryptographically verifiable delegation of authority over the data processing system to a second party, the cryptographically verifiable delegation comprising a public key of the second party, the second party is the owner of the data processing system after purchase from the channel of commerce, and the second security policy places the data processing system into compliance with the security framework implemented by the owner,

an ownership certificate indicating that the owner owns the data processing system,

a hardware certificate indicating configurations for hardware components of the data processing system, and

credentials for the data processing system to allow the data processing system to join a domain indicated by the owner, and

a management agent that indicates a software component designated by the owner for the data processing system; and

deploying, by the management service and during an onboarding of the data processing system by the second party, the ownership voucher to the data processing system to update the data processing system into a second security state specified by a change from the first security state to place the data processing system in compliance with a security framework implemented by the second party.

10 . The non-transitory machine-readable medium of claim 9 , wherein the first security state is hardened against attacks on the security of the data processing system, and the second security state is less restrictive than the first security state.

11 . The non-transitory machine-readable medium of claim 9 , wherein the operations further comprise:

obtaining, by the management service, a second public key from the owner;

obtaining, by the management service, the information regarding the security framework implemented by the owner;

generating, by the management service and using the second public key and the information, the second security policy; and

generating, by the management service and using the second security policy, the ownership voucher.

12 . A data processing system, comprising:

a processor; and

a memory coupled to the processor to store instructions, which when executed by the processor, cause the processor to perform operations for managing security of a data processing system, the operations comprising:

deploying, by a management service, an initial security policy to the data processing system, the initial security policy comprising a public key of a first party and placing the data processing system into a first security state, the first party is a manufacturer of the data processing system, and the initial security policy secures the data processing system against compromise while in a channel of commerce;

generating, by the management service, an ownership voucher for the data processing system, the ownership voucher comprising:

a second security policy, the second security policy being signed and verifiable using the public key of the first party, the second security policy specifying a change from the first security state, and the second security policy being based on information regarding a security framework implemented by an owner of the data processing system, and

a cryptographically verifiable delegation of authority over the data processing system to a second party, the cryptographically verifiable delegation comprising a public key of the second party, the second party is the owner of the data processing system after purchase from the channel of commerce, and the second security policy places the data processing system into compliance with the security framework implemented by the owner,

an ownership certificate indicating that the owner owns the data processing system,

a hardware certificate indicating configurations for hardware components of the data processing system,

credentials for the data processing system to allow the data processing system to join a domain indicated by the owner, and

a management agent that indicates a software component designated by the owner for the data processing system; and

deploying, by the management service and during an onboarding of the data processing system by the second party, the ownership voucher to the data processing system to update the data processing system into a second security state specified by a change from the first security state to place the data processing system in compliance with a security framework implemented by the second party.

13 . The data processing system of claim 12 , wherein the first security state is hardened against attacks on the security of the data processing system, and the second security state is less restrictive than the first security state.

14 . The data processing system of claim 12 , wherein the operations further comprise:

obtaining, by the management service, a second public key from the owner;

obtaining, by the management service, the information regarding the security framework implemented by the owner;

generating, by the management service and using the second public key and the information, the second security policy; and

generating, by the management service and using the second security policy, the ownership voucher.

15 . The non-transitory machine-readable medium of claim 9 , wherein the ownership voucher further comprises:

a third security policy, the third security policy being signed and verifiable using a public key of the second party, and the third security policy specifying a change from the second security state.

16 . The non-transitory machine-readable medium of claim 15 , wherein the second security policy further comprises:

a public key of the second party.

17 . The non-transitory machine-readable medium of claim 16 , wherein the public key of the second security policy delegates authority over changes in security policies implemented by the data processing system to the second party, and the public key of the second security policy requires that any changes to the second security state be signed by the second party and verifiable with the public key of the second security policy.

18 . The data processing system of claim 12 , wherein the ownership voucher further comprises:

a third security policy, the third security policy being signed and verifiable using a public key of the second party, and the third security policy specifying a change from the second security state.

19 . The data processing system of claim 18 , wherein the second security policy further comprises:

a public key of the second party.

20 . The data processing system of claim 19 , wherein the public key of the second security policy delegates authority over changes in security policies implemented by the data processing system to the second party, and the public key of the second security policy requires that any changes to the second security state be signed by the second party and verifiable with the public key of the second security policy.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 17, 2022
From: GOODMAN, BRADLEY K.; HUTCHINSON, KIRK ALAN; CAISSE, JOSEPH
To: DELL PRODUCTS L.P.
Reel/Frame 061444/0815 →
Continuity (1)
Related Publication 20240126905A1 · Apr 18, 2024
References Cited (25)
US 11552803B1 · Simkhada · 2023 [cited by applicant]
US 20040193917A1 · Drews · 2004 [cited by applicant]
US 20060236111A1 · Bodensjo · 2006 [cited by examiner]
US 20140298040A1 · Ignatchenko · 2014 [cited by applicant]
US 20150023183A1 · Ilsar · 2015 [cited by applicant]
US 20170093815A1 · Chen · 2017 [cited by applicant]
US 20190200405A1 · Gupta · 2019 [cited by applicant]
US 20190384916A1 · Shah · 2019 [cited by examiner]
US 20200213191A1 · Watsen · 2020 [cited by applicant]
US 20200250293A1 · Paulraj · 2020 [cited by examiner]
US 20200327231A1 · Smith · 2020 [cited by examiner]
US 20210409231A1 · Fedorkow · 2021 [cited by applicant]
US 20220303123A1 · Cabre · 2022 [cited by applicant]
US 20230034615A1 · Detienne · 2023 [cited by applicant]
US 20230367489A1 · Dover · 2023 [cited by applicant]
US 20230370454A1 · Mohammed · 2023 [cited by applicant]
US 20230394493A1 · Rao · 2023 [cited by applicant]
US 20240007354A1 · Zoualfaghari · 2024 [cited by applicant]
US 20240039723A1 · Ito · 2024 [cited by applicant]
US 20240064028A1 · Fedorkow · 2024 [cited by applicant]
US 20240243967A1 · Singh · 2024 [cited by applicant]
K. Watsen et al., “A Voucher Artifact for Bootstrapping Protocols”, May 2018, Internet Engineering Task Force (IETF) Request for Comments: 8366 (Year: 2018), pp. 1-23. [cited by applicant]
“Detailed Protocol Description—Secure Device Onboard”, Apr. 28, 2021, obtained online from <https://secure-device-onboard.github.io/docs/1.8.0/protocol-specification/detailed-protocol-description/>, retrieved on Jul. 13… [cited by applicant]
“Secure Device on board”, 2020, obtained online from <https://secure-device-onboard.github.io/docs/1.9.0/>, retrieved on Oct. 11, 2024 (Year: 2020), 7 pages. [cited by applicant]
G. Cooper et al., “FIDO Device on board Specification 1.1”, Apr. 19, 2022, obtained on line from <https://fidoalliance.org/specs/FDO/FIDO-Device-Onboard-PS-v1.1-20220419/FIDO-Device-Onboard-PS-v1.1-20220419.html>, retri… [cited by applicant]