IP Library › Granted Patent US 12,277,201
Granted Patent B2
US 12,277,201 · App. 18/363,632 · Granted Apr 15, 2025

Secure deployment of a software package

Inventors: Daniel Fox (London, GB); Felix Mance (London, GB); Jelena Cvitanovic (London, GB)
Assignee: Palantir Technologies Inc.
G06F21/121G06F8/60G06F16/254G06F16/9566H04L67/02H04L67/146H04L67/34G06F21/1014
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,277,201
App. No.
18/363,632
Filed
Aug 1, 2023
Granted
Apr 15, 2025
Kind
B2
Examiner
WONG, LESLIE
Art Unit
2164
USPC
726/27
Abstract

A method of securely deploying a software package comprises storing validity data describing restricted use of a restricted use token; receiving a command including a URL to deploy a software package; testing validity of the URL based on the validity data; and downloading, when the testing is successful, the software package via a secure channel, wherein the method is performed using one or more processors.

Claims (59)

1. A method of securely deploying a software package, comprising:

storing validity data describing restricted use of a restricted use token comprising a plurality of randomly-selected natural language words;

receiving a command including a URL to deploy a software package;

testing validity of the URL based on the validity data, including verifying that the URL includes the restricted use token;

causing downloading from on the URL, when the testing is successful, the software package via a secure channel,

wherein the method is performed using one or more processors.

2. The method of claim 1 , further comprising:

receiving a request to generate the software package and generating the software package;

generating the restricted use token for deploying the software package.

3. The method of claim 2 , further comprising:

concatenating the restricted use token with a URL root string into a target URL;

sending the target URL to a first device over a first computer network,

the command being received from a second device over a second computer network.

4. The method of claim 1 , the validity data including a use threshold value indicating a number of times the restricted use token may be used or a time window during which the restricted use token remains valid.

5. The method of claim 4 , further comprising:

determining whether use of the restricted use token exceeds the use threshold;

in response to determining that the use of the restricted use token does not exceed the use threshold, determining whether the use of the restricted use token remains within the time window,

the downloading being performed in response to determining that the use of the restricted use token remains within the time window.

6. The method of claim 4 ,

the validity data further including a number of times the restricted use token has been used;

the method further comprising updating the number of times the restricted use token has been used in response to a positive result of the testing.

7. The method of claim 1 ,

the validity data further including one or more previous restricted use tokens,

the testing comprising matching the URL with the one or more previous restricted use tokens.

8. The method of claim 1 , further comprising:

receiving a second command including a second URL;

determining that the second URL is invalid based on the validity data;

closing the secure channel.

9. The method of claim 1 , the testing comprising extracting the restricted use token out of the URL.

10. The method of claim 1 , the downloading comprising sending the software package to a computing device specified in the command.

11. A computer-readable, non-transitory storage medium storing computer-executable instructions, which when executed cause one or more processors to perform a method of securely deploying a software package, the method comprising:

storing validity data describing restricted use of a restricted use token comprising a plurality of randomly-selected natural language words;

receiving a command including a URL to deploy a software package;

testing validity of the URL based on the validity data, including verifying that the URL includes the restricted use token;

causing downloading from on the URL, when the testing is successful, the software package via a secure channel.

12. The computer-readable, non-transitory storage medium of claim 11 , the method further comprising:

receiving a request to generate the software package and generating the software package;

generating the restricted use token for deploying the software package.

13. The computer-readable, non-transitory storage medium of claim 12 , the method further comprising:

concatenating the restricted use token with a URL root string into a target URL;

sending the target URL to a first device over a first computer network,

the command being received from a second device over a second computer network.

14. The computer-readable, non-transitory storage medium of claim 11 , the validity data including a use threshold value indicating a number of times the restricted use token may be used or a time window during which the restricted use token remains valid.

15. The computer-readable, non-transitory storage medium of claim 14 , the method further comprising:

determining whether use of the restricted use token exceeds the use threshold;

in response to determining that the use of the restricted use token does not exceed the use threshold, determining whether the use of the restricted use token remains within the time window,

the downloading being performed in response to determining that the use of the restricted use token remains within the time window.

16. The computer-readable, non-transitory storage medium of claim 14 ,

the validity data further including a number of times the restricted use token has been used;

the method further comprising updating the number of times the restricted use token has been used in response to a positive result of the testing.

17. The computer-readable, non-transitory storage medium of claim 11 ,

the validity data further including one or more previous restricted use tokens,

the testing comprising matching the URL with the one or more previous restricted use tokens.

18. The computer-readable, non-transitory storage medium of claim 11 , the method further comprising:

receiving a second command including a second URL;

determining that the second URL is invalid based on the validity data;

closing the secure channel.

19. The computer-readable, non-transitory storage medium of claim 11 , the testing comprising extracting the restricted use token out of the URL.

20. The computer-readable, non-transitory storage medium of claim 11 , the downloading comprising sending the software package to a computing device specified in the command.

Continuity (4)
Continuation 16844855 · Apr 9, 2020
Continuation 15697270 · Sep 6, 2017
Continuation In Part 15225437 · Aug 1, 2016
Related Publication 20230376576A1 · Nov 23, 2023
References Cited (28)
US 7181731B2 · Pace et al. · 2007 [cited by applicant]
US 7711775B2 · Tavis et al. · 2010 [cited by applicant]
US 8200775B2 · Moore · 2012 [cited by applicant]
US 8671222B2 · Gass et al. · 2014 [cited by applicant]
US 8862602B1 · Sisson · 2014 [cited by applicant]
US 9712456B2 · Anumalasetty et al. · 2017 [cited by applicant]
US 9753715B2 · Sakai et al. · 2017 [cited by applicant]
US 9864735B1 · Lamprecht · 2018 [cited by applicant]
US 20040030932A1 · Juels et al. · 2004 [cited by applicant]
US 20040073903A1 · Melchione · 2004 [cited by examiner]
US 20050033728A1 · James et al. · 2005 [cited by applicant]
US 20070192863A1 · Kapoor et al. · 2007 [cited by applicant]
US 20120254289A1 · Sathish · 2012 [cited by applicant]
US 20120331529A1 · Ibel et al. · 2012 [cited by applicant]
US 20130132091A1 · Skerpac · 2013 [cited by examiner]
US 20140282464A1 · El-Gillani · 2014 [cited by applicant]
US 20150012476A1 · Seng et al. · 2015 [cited by applicant]
US 20150281225A1 · Schoen et al. · 2015 [cited by applicant]
US 20160132484A1 · Nauze et al. · 2016 [cited by applicant]
US 20160378439A1 · Straub et al. · 2016 [cited by applicant]
US 20160381023A1 · Dulce et al. · 2016 [cited by applicant]
US 20170068655A1 · Wang et al. · 2017 [cited by applicant]
US 20170141926A1 · Xu et al. · 2017 [cited by applicant]
US 20170200013A1 · Sechman et al. · 2017 [cited by applicant]
US 20170214683A1 · Kroehling et al. · 2017 [cited by applicant]
US 20170223005A1 · Birgisson et al. · 2017 [cited by applicant]
US 20170249132A1 · Andrews · 2017 [cited by examiner]
US 20200372205A1 · Jones et al. · 2020 [cited by applicant]
Cited By (1)
US 12,592,824