×

Secure key management

  • US 9,264,230 B2
  • Filed: 03/14/2011
  • Issued: 02/16/2016
  • Est. Priority Date: 03/14/2011
  • Status: Expired due to Fees
First Claim
Patent Images

1. A computer program product for secure key management, the computer program product comprising:

  • a non-transitory computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method, comprising;

    creating a token and populating a payload section of the token with key material;

    selecting a wrapping method from a plurality of supported wrapping methods that specifies how the key material is securely bound to key control information, wherein a structure of the key control information in the token is independent of the wrapping method, and wherein the plurality of supported wrapping methods comprises advanced encryption standard key wrap (AESKW), Rivest Shamir Adelman (RSA) with Optimal Asymmetric Encryption Padding (OAEP), data encryption standard (DES), Elliptic Curve, and message authentication code (MAC); and

    wrapping the key material and binding key control information to the key material in the token, the key control information including information relating to usage and management of the key material, wherein the token comprises the key control information, the payload section and a description of the wrapping method, the description of the wrapping method being in a selected section of the token, where sections of the token are known by a party accessing the token, the description of the wrapping method corresponding to one of the plurality of supported wrapping methods wherein the key control information further comprises a label for the token that is recoverable from the token, the label comprising an unencrypted user-specified name of the token, andthe information relating to management of the key material comprises extensible fields that are configured to describe a history and life cycle of the key material and allow updates to the extensible fields after receiving the token by the party accessing the token, and wherein a policy specifying when to retire the token and allowable methods for wrapping the token is configured to be created after receiving the token by the party accessing the token based on the extensible fields.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×