IP Library Granted Patent US 10,498,711
Granted Patent B1
US 10,498,711 · App. 15/188,784 · Granted Dec 3, 2019

Providing a booting key to a remote system

Inventors: Justin Cassidy (San Jose, CA); Tristan Smith (Sunnyvale, CA); Kori Oliver (Vienna, VA)
Assignee: Palantir Technologies Inc.
H04L63/061G06F9/4416G06F9/45558G06F21/575H04L63/029
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,498,711
App. No.
15/188,784
Granted
Dec 3, 2019
Kind
B1
Abstract

Aspects of the present disclosure relate to providing a booting key to a remote system. A policy server receives a verification that a predetermined number of user devices provided secret information for booting a remote system. The policy server provides, in response to the received verification, a message for a key server to provide a booting key to the remote system, the key server providing the booting key in response to the message and causing the remote system to complete a booting procedure, in response to the message from the policy server.

Claims (40)

1. A policy server comprising:

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

predetermining, based on a security threat level, a number of user devices;

receiving, at the policy server, a verification that the predetermined number of user devices provided secret information for booting a remote system; and

providing, from the policy server and in response to the received verification, a message for a key server to provide a booting key to the remote system, the key server providing the booting key to the remote system in response to the message and causing the remote system to complete a booting procedure, in response to the message from the policy server, wherein the policy server and the key server are separate machines, wherein communication between the policy server, the key server, and the remote system occurs via a first encrypted tunnel connecting the policy server to the key server and a second encrypted tunnel connecting the key server to the remote system, wherein the policy server and the key server are part of a first running instance of a fully encrypted system, wherein a second running instance of the fully encrypted system is used to decrypt the first running instance, wherein the first running instance and the second running instance are part of a plurality of running instances of the fully encrypted system, and wherein, if all of the plurality of running instances are offline, one of the plurality of running instances is decrypted manually.

2. The policy server of claim 1 , wherein the remote system comprises a virtual system, a container, or a hypervisor.

3. The policy server of claim 1 , wherein the remote system comprises a remote client machine or a remote server.

4. The policy server of claim 1 , the operations further comprising:

receiving, at the policy server, an indication that the remote system has initiated the booting procedure; and

responsive to the indication, prompting for the verification from a plurality of user devices, the plurality of user devices including the predetermined number of user devices.

5. The policy server of claim 4 , the operations further comprising:

receiving, at the policy server, data from a log of the remote system, the data indicating occurrences that occurred prior to the remote system needing to reboot; and

providing the received data to the plurality of user devices together with prompting for the verification from the plurality of user devices.

6. The policy server of claim 1 , wherein the policy server comprises the key server, and wherein the key server stores a plurality of booting keys for a plurality of remote systems, and a mapping of remote system identifiers to booting keys.

7. The policy server of claim 6 , wherein the key server provides the booting key to the remote system via the second encrypted tunnel.

8. The policy server of claim 1 , wherein the verification that the predetermined number of user devices provided the secret information is received via an additional encrypted tunnel connecting the predetermined number of user devices with the policy server.

9. The policy server of claim 1 , wherein the message for the key server to provide the booting key to the remote system is transmitted from the policy server to the key server via the first encrypted tunnel.

10. The policy server of claim 1 , wherein the verification from the predetermined number of user devices is received via a push notification or via a mail server.

11. The policy server of claim 1 , wherein the message for the key server to provide the booting key to the remote system comprises authenticated information for providing the booting key to the remote system.

12. A non-transitory machine-readable medium storing instructions that, when executed by the one or more processors of a machine, cause the one or more processors to perform operations comprising:

predetermining, based on a security threat level, a number of user devices;

receiving, at a policy server, a verification that the predetermined number of user devices provided secret information for booting a remote system; and

providing, from the policy server and in response to the received verification, a message for a key server to provide a booting key to the remote system, the key server providing the booting key to the remote system in response to the message and causing the remote system to complete a booting procedure, in response to the message, wherein the policy server and the key server are separate machines, wherein communication between the policy server, the key server, and the remote system occurs via a first encrypted tunnel connecting the policy server to the key server and a second encrypted tunnel connecting the key server to the remote system, wherein the policy server and the key server are part of a first running instance of a fully encrypted system, wherein a second running instance of the fully encrypted system is used to decrypt the first running instance, wherein the first running instance and the second running instance are part of a plurality of running instances of the fully encrypted system, and wherein, if all of the plurality of running instances are offline, one of the plurality of running instances is decrypted manually.

13. The machine-readable medium of claim 12 , wherein the remote system comprises a virtual system, a container, or a hypervisor.

14. The machine-readable medium of claim 12 , wherein the remote system comprises a remote client machine or a remote server.

15. The machine-readable medium of claim 12 , the operations further comprising:

receiving an indication that the remote system has initiated the booting procedure; and

responsive to the indication, prompting for the verification from a plurality of user devices, the plurality of user devices including the predetermined number of user devices.

16. The machine-readable medium of claim 15 , the operations further comprising:

receiving data from a log of the remote system, the data indicating occurrences that occurred prior to the remote system needing to reboot; and

providing the received data to the plurality of user devices together with prompting for the verification from the plurality of user devices.

17. The machine-readable medium of claim 12 , wherein the verification that the predetermined number of user devices provided the secret information is received via an additional encrypted tunnel connecting the predetermined number of user devices with the policy server.

18. The machine-readable medium of claim 12 , wherein the message for the key server to provide the booting key to the remote system is transmitted from the policy server to the key server via the first encrypted tunnel.

19. The machine-readable medium of claim 12 , wherein the verification from the predetermined number of user devices is received via a push notification or via a mail server.

20. A method comprising:

predetermining, based on a security threat level, a number of user devices;

receiving, at one or more processors of a policy server, a verification that the predetermined number of user devices provided secret information for booting a remote system; and

providing, from the policy server and in response to the received verification, a message for a key server to provide a booting key to the remote system, the key server providing the booting key to the remote system in response to the message and causing the remote system to complete a booting procedure, in response to the message from the policy server, wherein the policy server and the key server are separate machines, wherein communication between the policy server, the key server, and the remote system occurs via a first encrypted tunnel connecting the policy server to the key server and a second encrypted tunnel connecting the key server to the remote system, wherein the policy server and the key server are part of a first running instance of a fully encrypted system, wherein a second running instance of the fully encrypted system is used to decrypt the first running instance, wherein the first running instance and the second running instance are part of a plurality of running instances of the fully encrypted system, and wherein, if all of the plurality of running instances are offline, one of the plurality of running instances is decrypted manually.

21. The method of claim 20 , wherein the number of user devices is a plural number of user devices, and wherein the security threat level represents existence of known security threats.

Assignments (8)
ASSIGNMENT OF INTELLECTUAL PROPERTY SECURITY AGREEMENTS Recorded Jul 3, 2022
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: WELLS FARGO BANK, N.A.
Reel/Frame 060572/0640 →
SECURITY INTEREST Recorded Jul 3, 2022
From: PALANTIR TECHNOLOGIES INC.
To: WELLS FARGO BANK, N.A.
Reel/Frame 060572/0506 →
CORRECTIVE ASSIGNMENT TO CORRECT THE ERRONEOUSLY LISTED PATENT BY REMOVING APPLICATION NO. 16/832267 FROM THE RELEASE OF SECURITY INTEREST PREVIOUSLY RECORDED ON REEL 052856 FRAME 0382. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST. Recorded Aug 26, 2021
From: ROYAL BANK OF CANADA
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 057335/0753 →
SECURITY INTEREST Recorded Jun 4, 2020
From: PALANTIR TECHNOLOGIES INC.
To: MORGAN STANLEY SENIOR FUNDING, INC.
Reel/Frame 052856/0817 →
RELEASE OF SECURITY INTEREST Recorded Jun 4, 2020
From: ROYAL BANK OF CANADA
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 052856/0382 →
SECURITY INTEREST Recorded Jan 27, 2020
From: PALANTIR TECHNOLOGIES INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS ADMINISTRATIVE AGENT
Reel/Frame 051713/0149 →
SECURITY INTEREST Recorded Jan 27, 2020
From: PALANTIR TECHNOLOGIES INC.
To: ROYAL BANK OF CANADA, AS ADMINISTRATIVE AGENT
Reel/Frame 051709/0471 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 23, 2016
From: CASSIDY, JUSTIN; SMITH, TRISTAN; OLIVER, KORI
To: PALANTIR TECHNOLOGIES INC.
Reel/Frame 039510/0867 →
Cited By (1)
US 12,238,076