Hardware security module access management in a cloud computing environment

US9836308B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9836308-B2
Application numberUS-201414574728-A
CountryUS
Kind codeB2
Filing dateDec 18, 2014
Priority dateSep 30, 2014
Publication dateDec 5, 2017
Grant dateDec 5, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Trusted firmware on a host server is used for managing access to a hardware security module (HSM) connected to the host server. The HSM stores confidential information associated with an operating system. As part of access management, the firmware detects a boot device identifier associated with a boot device configured to boot the operating system on the host server. The firmware then receives a second boot device identifier from the HSM. The boot device identifier and the second boot device identifier are then compared by the firmware. Based on the comparison, the firmware determines that the boot device identifier matches with the second boot device identifier. Based on this determination, the firmware grants the operating system access to the HSM.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for managing access to a hardware security module (HSM) connected to a host server, the HSM having confidential information associated with an operating system stored thereon, the method comprising: detecting a boot device identifier associated with a boot device configured to boot the operating system on the host server; receiving a second boot device identifier from the HSM; comparing the boot device identifier to the second boot device identifier; determining, based on the comparing, that the boot device identifier matches with the second boot device identifier; and granting, subsequent to the determining, the operating system access to the HSM. 2. The method of claim 1 , wherein the comparing is performed by a device selected from the group consisting of firmware running on the host server and a hypervisor. 3. The method of claim 1 , further comprising: detecting a third boot device identifier associated with a second boot device configured to boot a second operating system on the host server; comparing the second boot device identifier to the third boot device identifier; determining, based on the comparing the second boot device identifier to the third boot device identifier, that the second boot device identifier does not match with the third boot device identifier; and denying, subsequent to the determining that the second boot device identifier does not match with the third boot device identifier, the second operating system access to the HSM. 4. The method of claim 3 , further comprising: receiving a fourth boot device identifier from a second HSM connected to the host server, the second HSM having second confidential information associated with the second operating system stored thereon; comparing the third boot device identifier to the fourth boot device identifier; determining, based on the comparing the third boot device identifier to the fourth boot device identifier, that the third boot device identifier matches with the fourth boot device identifier; and granting, subsequent to the determining that the third boot device identifier matches with the fourth boot device identifier, the second operating system access to the second HSM. 5. The method of claim 4 , wherein the HSM and the second HSM are contained on a single card as partitioned portions. 6. The method of claim 1 , further comprising: storing the confidential information combined with the second boot device identifier on the HSM via a secure protocol. 7. The method of claim 1 , wherein the second boot device identifier is in the form of a hash value of data stored on the boot device. 8. The method of claim 1 , wherein the HSM comprises an adapter card with a crypto co-processor. 9. The method of claim 1 , wherein the operating system is a guest operating system. 10. The method of claim 1 , wherein the operating system is an instance of a guest operating system running on the host server, the method further comprising: booting, prior to the detecting, the guest operating system on the host server using the boot device. 11. The method of claim 1 , wherein the second boot device identifier is a copy of the boot device identifier.

Assignees

Inventors

Classifications

  • Secure firmware programming, e.g. of basic input output system [BIOS] · CPC title

  • Isolation or security of virtual machine instances · CPC title

  • Secure boot · CPC title

  • G06F9/4408Primary

    Boot device selection · CPC title

  • Hypervisor-specific management and integration aspects · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9836308B2 cover?
Trusted firmware on a host server is used for managing access to a hardware security module (HSM) connected to the host server. The HSM stores confidential information associated with an operating system. As part of access management, the firmware detects a boot device identifier associated with a boot device configured to boot the operating system on the host server. The firmware then receives…
Who is the assignee on this patent?
IBM
What technology area does this patent fall under?
Primary CPC classification G06F9/4408. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Dec 05 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).