Back to results
US 11,836,254 B2Granted
System and method for securing a series of firmware function calls using session tokens
AssigneeInsyde Software Corp.
InventorTimothy Andrew Lewis
Life of this patent
Estimating the term…
Abstract
A mechanism for securing a series of related function calls for firmware services using session tokens is discussed.
Claims17
A non-transitory medium holding computer-executable instructions for authenticating related firmware service calls in a computing device that includes firmware and at least one processor, the firmware when executed causing the computing device to:
- receive a request with the firmware to open a session from an operating system-based calling entity, the request accompanied by authentication data;
- authenticate the operating system-based calling entity based on the authentication data;
- establish the session between the operating system-based calling entity and the firmware, the session including a privilege level for multiple firmware service requests made in the session that is associated with a specified portion of a boot sequence or a physical security condition of the computing device, a session token returned to the operating system-based calling entity, the firmware rejecting any additional session requests after establishing the session until the established session is closed;
- receive a firmware service call from the operating system-based calling entity accompanied by the session token as a calling parameter;
- verify the session token and that the privilege level is adequate for the firmware service call;
- perform the firmware service call based on the verifying;
- return an updated session token with a firmware service call return to the operating system-based calling entity after the performing of the firmware service call, the updated session token based on a randomly generated number that is not a pseudo random number;
- receive a subsequent related firmware service call accompanied by the updated session token as a calling parameter;
- verify the updated session token and that the privilege level is adequate for the subsequent related firmware service call;
- and
- perform the subsequent related firmware service call based on the verifying of the updated session token and the privilege level.
8 more elements
A method for authenticating firmware service calls in a computing device equipped with at least one processor, comprising:
- receiving a request with the firmware to open a session from an operating system-based calling entity, the request accompanied by authentication data;
- authenticating with the firmware the operating system-based calling entity based on the authentication data;
- establishing the session between the operating system-based calling entity and firmware executing on the computing device, the session including a privilege level for multiple firmware service requests made in the session that is associated with a specified portion of a boot sequence or a physical security condition of the computing device, a session token returned to the operating system-based calling entity, the firmware rejecting any additional session requests after establishing the session until the established session is closed;
- receiving with the firmware a firmware service call from the calling entity accompanied by the session token as a calling parameter;
- verifying the session token and that the privilege level is adequate for the firmware service call;
- performing the firmware service call with the firmware based on the verifying;
- returning an updated session token with a firmware service call return to the operating system-based calling entity after the performing of the firmware service call, the updated session token based on a randomly generated number that is not a pseudo random number;
- receiving a subsequent related firmware service call accompanied by the updated session token as a calling parameter;
- verifying the updated session token and that the privilege level is adequate for the subsequent related firmware service call;
- and
- performing the subsequent related firmware service call with the firmware based on the verifying of the updated session token and the privilege level.
8 more elements
A computing device configured to securely handle related function calls to firmware, the computing device comprising:
- at least one processor;
- an operating system;
- and
- firmware, the firmware when executed:
- receiving a request to open a session from an operating system-based calling entity, the request accompanied by authentication data,
- authenticating the operating system-based calling entity based on the authentication data,
- establishing the session between the operating system-based calling entity and the firmware, the session including a privilege level for multiple firmware service requests made in the session that is associated with a specified portion of a boot sequence or a physical security condition of the computing device, a session token returned to the operating system-based calling entity, the firmware rejecting any additional session requests after establishing the session until the established session is closed,
- receiving a firmware service call from the operating system-based calling entity accompanied by the session token as a calling parameter,
- verifying the session token and that the privilege level is adequate for the firmware service call,
- performing the firmware service call based on the verifying,
- returning an updated session token with a firmware service call return to the operating system-based calling entity after the performing of the firmware service call, the updated session token based on a randomly generated number that is not a pseudo random number,
- receiving a subsequent related firmware service call accompanied by the updated session token as a calling parameter,
- verifying the updated session token and that the privilege level is adequate for the subsequent related firmware service call, and
- performing the subsequent related firmware service call based on the verifying of the updated session token and the privilege level.
11 more elements
Dependencies are inferred from the claim text.