US 2021/0334380 A1 · TRUSTED FIRMWARE VERIFICATION

Abstract

Disclosed are various examples for verification and management of firmware for client devices enrolled with a management service of an enterprise. The firmware verification includes a verification process using multiple checkpoints for determining whether status responses associated with firmware installed on and received from a managed client device can be trusted. The multiple checkpoints can include verifying certificate data, signature data, and an exit code included in status responses received from managed devices. In the event that one of the verification steps fails, the device can be considered compromised and subject to various compliance actions. The compliance actions can include limiting access to enterprise data, limiting access to one or more applications, wiping a device clean to reset the devices to the original factory settings, sending a notification to an enterprise administrator providing an indication of the detected compromise, and other types of compliance actions.

Claims20

Dependent claims

A system, comprising:

a computing device comprising a processor and a memory;
and
machine-readable instructions stored in the memory which, when executed by the processor, cause the computing device to at least:
send a request to a client device for a status of firmware installed on the client device;
receive a status response file and an exit code associated with the firmware from the client device, the status response file comprising at least a signature and a certificate, and the exit code being generated by a firmware utility on the client device;
perform at least one of a plurality of verification steps to determine whether the status response file is compromised, the plurality of verification steps comprising at least one of a certificate verification, a signature verification, or an exit code verification;
and
perform a compliance action in an instance in which the status response file is determined to be compromised.

5 more elements

A non-transitory computer-readable medium embodying executable instructions which, when executed by a computing device, cause the computing device to at least:

send a request to a client device for a status of firmware installed on the client device;
receive a status response file and an exit code associated with the firmware from the client device, the status response file comprising at least a signature and a certificate, and the exit code being generated by a firmware utility on the client device;
perform at least one of a plurality of verification steps to determine whether the status response file is compromised, the plurality of verification steps comprising at least one of a certificate verification, a signature verification, or an exit code verification;
and
perform a compliance action in an instance in which the status response file is determined to be compromised.

2 more elements

A computer-implemented method, comprising:

sending, by at least one computing device, a request to a client device for a status of firmware installed on the client device;
receiving, by the at least one computing device, a status response file and an exit code associated with the firmware from the client device, the status response file comprising at least a signature and a certificate, and the exit code being generated by a firmware utility on the client device;
performing, by the at least one computing device, at least one of a plurality of verification steps to determine whether the status response file is compromised, the plurality of verification steps comprising at least one of a certificate verification, a signature verification, or an exit code verification;
and
performing, by the at least one computing device, a compliance action in an instance in which the status response file is determined to be compromised.

2 more elements

Dependencies are inferred from the claim text.

Trusted firmware verification

Life of this patent

Trusted firmware verification

Life of this patent

Abstract

Claims20