IP Library Granted Patent US 9,350,536
Granted Patent B2
US 9,350,536 · App. 13/733,646 · Granted May 24, 2016

Cloud key management system

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 9,350,536
App. No.
13/733,646
Granted
May 24, 2016
Kind
B2
Abstract

This invention uses a cloud-based key management system to store, retrieve, generate, and perform other key operations. The cloud-based system ensures security of the keys while preventing their loss or destruction. Using this invention, a company can now manage, audit, and maintain control and security around their keys. Security event auditing permits evaluation of the operations to ensure that each step is completely secure.

Claims (74)

1. A method for encrypted email key management, comprising:

creating, by a key agent executing on a processor, a secure tunnel between the key agent and a cloud key service executing on a processor;

receiving, by the cloud key service from the key agent, a request for key generation for the email sender, the request including email sender credentials;

verifying, by the cloud key service, the request for key generation;

identifying, by the cloud key service, a tenant location on the cloud key service, the tenant location being associated with the email sender;

creating, by the cloud key service, a key pair and corresponding digital certificate for the email sender;

encrypting, by the cloud key service, the key pair and corresponding digital certificate with a key controlled by the key agent;

storing the encrypted key pair and corresponding digital certificate at the identified tenant location;

transmitting a public key from the key pair and the corresponding digital certificate to an email address specified in the digital certificate; and

closing the secure tunnel.

2. A method according to claim 1 , where the key agent local to email sender.

3. A method according to claim 1 , wherein verifying the request for key generation comprises evaluating a cloud-based key policy.

4. A method according to claim 1 , wherein verifying the request for key generation comprises verifying an identity of the email sender.

5. A method according to claim 1 , further comprising:

creating, by the key agent, a second secure tunnel between the key agent and the cloud key service;

receiving, by the cloud key service from the key agent, a request for use of the key by a mail server;

identifying, by the cloud key service, the tenant location storing the encrypted key pair and corresponding digital certificate;

receiving, by the cloud key service, the key controlled by the key agent;

decrypting, by the cloud key service, the encrypted key pair and corresponding digital certificate;

performing, by the cloud key service, a key service using the decrypted key pair; and

closing the second secure tunnel.

6. A method according to claim 1 , where the cloud key service accesses a segmented location associated with the tenant location on the cloud-based system for decrypting, encrypting and signing key services.

7. A method according to claim 6 , where the segmented location is associated with the email sender.

8. A method according to claim 1 , where the key agent communicates information about the key service to the email sender.

9. A method according to claim 8 , where the information comprises a digital certificate.

10. A method according to claim 8 , where the information comprises a digital key.

11. A method according to claim 8 , where the information comprises security events that document actions taken by the cloud key service.

12. A method according to claim 1 , where the key generation is performed in accordance with a key policy located on the cloud key service.

13. A method according to claim 5 , where the key service comprises deleting or revoking a key.

14. A method according to claim 13 , where the key is deleted or revoked by a key provisioner.

15. A method according to claim 1 , where the encrypted key pair and corresponding digital certificate is stored on a segmented location of the cloud based service.

16. A method according to claim 1 , further comprising creating, by the cloud key service, at least one security event that document actions taken by the cloud key service.

17. A method according to claim 16 , further comprising transmitting, by the cloud key service, at least one security event to a security events collector.

18. A method according to claim 5 , where the performance of the key services are evaluated by a key validator to ensure the key service complies with the key policy, where the key policy is stored by the cloud key service.

19. A method for using keys in an email system, comprising:

receiving a request for key generation at a key agent executing on a processor from an email server, the request associated with an email sender;

creating a first secure tunnel between the key agent and a cloud key service executing on a processor;

communicating the first request to the cloud key service over the first secure tunnel;

generating a key pair at the cloud key service;

storing the generated key in an encrypted store on a segmented location on the cloud key service, where the encrypted store is encrypted using a store key controlled by the key agent;

receiving a request for a key operation at the key agent from the email server and for the email sender;

create a second secure tunnel between the key agent and the cloud key service;

communicating the request for a key operation to the cloud key service of the second secure tunnel;

assessing the segmented location on the cloud key service;

decrypting the generated key stored at the segmented location using the key controlled by the key agent; and

performing the key operation by the cloud key service.

20. A method according to claim 19 , further comprising validating, by the key agent, the identity of an email sender.

21. A method according to claim 19 , where the key is generated on a tenant location.

22. A method according to claim 21 , where the tenant location is selected by a multi-tenant manager.

23. A method according to claim 19 , where the key is encrypted using a store key transmitted to the cloud key service by the key agent.

24. A system for email key management, comprising:

a key agent comprising a computer processor and computer readable memory storing instructions that cause the key agent to receive a request for key services for an email sender from a mail server and transmit the request to a cloud key service;

a cloud key service comprising:

an encrypted key store located on a segmented location of the cloud key service, the encrypted key store comprising computer readable memory configured to store keys and wherein the encrypted key store is encrypted using a store key controlled by the key agent;

a multi-tenancy manager comprising a computer processor and computer readable memory storing instructions that cause the multi-tenancy manager to route a request from the key agent and identify a tenant store in the cloud key service, wherein the tenant store is associated with the email sender; and

a server manager comprising a computer processor and computer readable memory storing instructions that cause the server manager to perform a key service associated with a key stored at the tenant store.

25. A system according to claim 24 , further comprising a mail server that uses the key agent to communicate with the cloud-based service.

26. A system according to claim 24 , further comprising a key validator configured to ensure that the cloud key service complies with a key policy, where the key policy is located on the cloud key service.

27. A system according to claim 24 , further comprising a security event collector to receive, collect or distribute security events.

28. A system according to claim 24 , further comprising an identity service configured to authenticate an identity.

29. A system according to claim 24 , further comprising a key provisioner.

30. An apparatus for providing cloud-based email key services, comprising:

a processor; and

non-transitory memory storing computer executable instructions that, when executed by the processor, cause the apparatus to at least:

accept requests for use of a key associated with an email sender, the requests being made by an email server through a key agent;

validate an identity of the email sender;

identify that a key associated with the email sender does not exist at a tenant location on the cloud key service;

in response to determining that a key associated with the email sender does not exist, generate a key for the email sender;

identify a tenant location on the cloud key service for storing the key;

encrypting the key using a store key, wherein the store key is controlled by the key agent; and

verify that the key generation is performed correctly.

31. An apparatus according to claim 30 , where the computer executable instructions further cause the apparatus to create security events that document actions taken by the apparatus and the security events are sent to a security events collector.

32. An apparatus according to claim 30 , where the computer executable instructions further cause the apparatus to generate a digital certificate for the email sender.

33. An apparatus according to claim 30 , where the computer executable instructions further cause the apparatus to open and close a secure tunnel between the key service and the key agent.

Assignments (19)
ASSIGNMENT OF SECURITY INTERESTS IN INTELLECTUAL PROPERTY (FIRST LIEN), RECORDED ON OCTOBER 16, 2019 AT REEL 050741 FRAME 0918 Recorded Sep 24, 2025
From: UBS AG, STAMFORD BRANCH, AS SUCCESSOR TO CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS RESIGNING AGENT
To: HPS INVESTMENT PARTNERS, LLC, AS SUCCESSOR AGENT
Reel/Frame 072947/0157 →
SECOND LIEN NOTICE OF SUCCESSION OF AGENCY Recorded Jul 30, 2025
From: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS PRIOR AGENT
To: UBS AG, STAMFORD BRANCH, AS SUCCESSOR AGENT
Reel/Frame 072300/0068 →
ASSIGNMENT OF INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Feb 19, 2021
From: JEFFERIES FINANCE LLC, AS EXISTING AGENT
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS SUCCESSOR AGENT
Reel/Frame 055345/0042 →
RELEASE OF FIRST LIEN SECURITY INTEREST IN PATENTS Recorded Oct 17, 2019
From: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
To: DIGICERT, INC.; GEOTRUST, LLC
Reel/Frame 050746/0973 →
RELEASE OF SECOND LIEN SECURITY INTEREST IN PATENTS Recorded Oct 17, 2019
From: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
To: DIGICERT, INC.; GEOTRUST, LLC
Reel/Frame 050747/0001 →
SECOND LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 16, 2019
From: DIGICERT, INC.
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 050741/0899 →
FIRST LIEN INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Oct 16, 2019
From: DIGICERT, INC.
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 050741/0918 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Nov 3, 2017
From: DIGICERT, INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 044681/0556 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Nov 3, 2017
From: DIGICERT, INC.
To: UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT
Reel/Frame 044710/0529 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 036912/0839 Recorded Nov 1, 2017
From: OAKTREE FUND ADMINISTRATION, LLC (AS SUCCESSOR TO FIFTH STREET MANAGEMENT LLC)
To: DIGICERT, INC.
Reel/Frame 044348/0001 →
RELEASE OF SECURITY INTEREST Recorded Oct 31, 2017
From: JEFFERIES FINANCE LLC
To: DIGICERT, INC.
Reel/Frame 043990/0809 →
ASSIGNMENT OF SECOND LIEN PATENT SECURITY AGREEMENT Recorded Oct 20, 2017
From: FIFTH STREET MANAGEMENT LLC
To: OAKTREE FUND ADMINISTRATION, LLC
Reel/Frame 044242/0788 →
RELEASE OF SECURITY INTEREST Recorded Oct 21, 2015
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: DIGICERT, INC.
Reel/Frame 036848/0402 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Oct 21, 2015
From: FIFTH STREET FINANCE CORP.
To: DIGICERT, INC.
Reel/Frame 036912/0633 →
SECOND LIEN PATENT SECURITY AGREEMENT Recorded Oct 21, 2015
From: DIGICERT, INC.
To: FIFTH STREET MANAGEMENT LLC
Reel/Frame 036912/0839 →
FIRST LIEN PATENT SECURITY AGREEMENT Recorded Oct 21, 2015
From: DIGICERT, INC.
To: JEFFERIES FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 036908/0381 →
SECURITY INTEREST Recorded Jun 2, 2014
From: DIGICERT, INC.
To: SILICON VALLEY BANK
Reel/Frame 033009/0488 →
SECURITY INTEREST Recorded Jun 2, 2014
From: DIGICERT, INC.
To: FIFTH STREET FINANCE CORP.
Reel/Frame 033072/0471 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2014
From: SABIN, JASON ALLEN
To: DIGICERT, INC.
Reel/Frame 032924/0020 →