Attesting a Component of a System During a Boot Process
US-2015007313-A1 · Jan 1, 2015 · US
US9342696B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9342696-B2 |
| Application number | US-201113820039-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 31, 2011 |
| Priority date | Sep 22, 2010 |
| Publication date | May 17, 2016 |
| Grant date | May 17, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for attesting use of an interactive component during a boot process, comprising the steps of: reading, in response to determining use of the interactive component, associated interactive input; determining whether the input should be trusted; and in response to determining that the input should be trusted, processing the input to create a trusted cryptographic value, further comprising: matching, in response to a subsequent interactive input being read, the subsequent interactive input with one or more of the trusted cryptographic values in order to determine whether the subsequent interactive input is trusted.
Opening claim text (preview).
The invention claimed is: 1. A method for attesting a boot process of a managed system, said managed system having an interactive component for receiving an optional interactive user input as part of the boot process, the method comprising the computer-executed steps of: retrieving a record of events occurring during said boot process, the record of events being generated in said managed system during said boot process; determining, using said record of events, whether an interactive user input was received in said managed system using said interactive component as part of said boot process; in response to determining that an interactive user input was received in said managed system using said interactive component: comparing a cryptographic value derived from the interactive user input with a record of any trusted cryptographic values to determine whether the interactive user input which was received using said interactive component as part of said boot process should be trusted; if the cryptographic value derived from the interactive user input matches a trusted cryptographic value in the record of any trusted cryptographic values, then determining that the interactive user input should be trusted; if the cryptographic value derived from the interactive user input does not match any trusted cryptographic value in the record of any trusted cryptographic values, then parsing an event log containing the interactive user input to determine whether the interactive user input should be trusted; and in response to determining that the interactive user input should be trusted as a result of parsing the event log containing the interactive user input to determine whether the interactive user input should be trusted, processing the interactive user input to create a first trusted cryptographic value and adding the first trusted cryptographic value to the record of any trusted cryptographic values. 2. A method as claimed in claim 1 , further comprising the steps of: assigning a platform configuration register (PCR) to the interactive user input; and extending the assigned PCR with the interactive user input. 3. A method as claimed in claim 1 , further comprising the step of: generating metadata associated with the trusted cryptographic value. 4. A method as claimed in claim 1 , further comprising the step of: determining, in response to the subsequent interactive user input matching a trusted cryptographic value, that a system associated with the interactive component is trusted. 5. A method as claimed in claim 1 , wherein parsing an event log containing the interactive user input to determine whether the interactive user input should be trusted comprises: matching an event log entry in the event log with a data structure of known input. 6. A method as claimed in claim 5 , further comprising the step of: determining, in response to the event log entry not matching the data structure of known input, that a system associated with the interactive component is not trusted. 7. A method as claimed in claim 1 , wherein the method is performed in a managing computer system separate from said managed computer system. 8. A computer program comprising computer program code stored on a non-transitory computer readable medium to, when loaded into a computer system and executed thereon, cause said computer system to perform the steps of: retrieving a record of events occurring during a boot process of a managed system, said managed system having an interactive component for receiving an optional interactive user input as part of the boot process, the record of events being generated in said managed system during said boot process; determining, using said record of events whether an interactive user in gut was received in said managed system using said interactive component as part of said boot process; in response to determining that an interactive user input was received in said managed system using said interactive component; comparing a cryptographic value derived from the interactive user input with a record of any trusted cryptographic values to determine whether the interactive user input which was received using said interactive component as part of said boot process should be trusted; if the cryptographic value derived from the interactive user input matches a trusted cryptographic value in the record of any trusted cryptographic values, then determining that the interactive user input should be trusted; if the cryptographic value derived from the interactive user input does not match any trusted cryptographic value in the record of any trusted cryptographic values, then parsing an event log containing the interactive user input to determine whether the interactive user input should be trusted; and in response to determining that the interactive user input should be trusted as a result of parsing the event log containing the interactive user input to determine whether the interactive user input should be trusted, processing the interactive user input to create a first trusted cryptographic value and adding the first trusted cryptographic value to the record of any trusted cryptographic values. 9. The computer program as claimed in claim 8 , wherein the computer program code is executed in a managing computer system separate from said managed computer system.
Secure boot · CPC title
Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.