# US 8,544,106 B2 · System and method for enabling access to a protected hardware resource

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 8,544,106 B2
- Document ID: US8544106B2
- Status: Granted
- Kind: B2
- Application number: 12/848,184
- Filed: 2010-08-01
- Published: 2012-02-02
- Granted: 2013-09-24
- Earliest claimed: 2010-08-01
- Assignees: Cavium, Inc.
- Applicants: Amer Haider; Steven Craig Barner; Richard Eugene Kessler
- Inventors: Amer Haider; Steven Craig Barner; Richard Eugene Kessler
- Web page: https://patentgrep.com/patent/US8544106B2

## CPC

- G06F 21/34: involving the use of external additional devices, e.g. dongles or smart cards
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods are disclosed for enabling access to a protected hardware resource. A hardware component includes at least one protected hardware resource. A unique hardware ID and a unique cryptographically secure or randomly generated enable value (EV) are integrated in the hardware component at the time of manufacturing. At run-time, special software generates or receives from an external source an enable register (ER) value and a comparison is made with the stored enable value. If the ER value and the EV match, access to the protected hardware resource is allowed.

## Claims

### Claim 1

A method for selectively enabling access to a protected resource, the method comprising:
providing a unique hardware ID associated with a hardware component having a protected resource;
receiving a restricted software module based on at least the unique hardware ID;
executing the restricted software module on the hardware component to generate or access an enable register (ER) value;
comparing the ER value with a unique stored enable value (EV) stored in a secure location in the hardware component and the protected resource; and
allowing access to the protected resource if the ER value and the EV match.

### Claim 2 (depends on 1)

The method of claim 1, wherein providing the unique hardware ID is achieved through secure communication and authentication.

### Claim 3 (depends on 1)

The method of claim 1, wherein receiving the restricted software module is achieved through secure communication and authentication.

### Claim 4 (depends on 1)

The method of claim 1, wherein the EV has a relationship to the hardware ID.

### Claim 5 (depends on 4)

The method of claim 4, wherein the relationship is defined by one of a proprietary function or a standard cryptographic function.

### Claim 6 (depends on 1)

The method of claim 1, wherein the EV is not related to the hardware ID by any mathematical relationship.

### Claim 7 (depends on 1)

The method of claim 1, wherein the protected resource is a cryptographic engine or module.

### Claim 8 (depends on 1)

The method of claim 1, wherein access to the protected resource is allowed for a predetermined amount of time.

### Claim 9 (depends on 1)

The method of claim 1, wherein access to the protected resource is allowed for a predetermined number of uses.

### Claim 10

A method for enabling access to a protected resource, the method comprising:
receiving a unique hardware ID associated with a hardware component having a protected resource; and
providing a restricted software module based on at least the unique hardware ID, wherein the restricted software module is configured to generate or access an enable register (ER) value; wherein the restricted software module is configured to compare the ER value with a unique stored enable value (EV) stored in a secure location in the hardware component and the protected resource and to allow access to the protected resource if the ER value and the EV match.

### Claim 11 (depends on 10)

The method of claim 10, wherein receiving the unique hardware ID is achieved through secure communication and authentication.

### Claim 12 (depends on 10)

The method of claim 10, wherein providing the restricted software module is achieved through secure communication and authentication.

### Claim 13 (depends on 10)

The method of claim 10, wherein the EV has a relationship to the hardware ID.

### Claim 14 (depends on 13)

The method of claim 13, wherein the relationship is one of a proprietary function or a standard cryptographic function.

### Claim 15 (depends on 10)

The method of claim 10, wherein the EV is not related to the hardware ID by any mathematical relationship.

### Claim 16 (depends on 10)

The method of claim 10, wherein the protected resource is a cryptographic engine or module.

### Claim 17 (depends on 10)

The method of claim 10, wherein access to the protected resource is allowed for a predetermined amount of time.

### Claim 18 (depends on 10)

The method of claim 10, wherein access to the protected resource is allowed for a predetermined number of uses.

### Claim 19

A hardware component, comprising:
a unique hardware ID associated with the hardware component;
a protected resource;
a permanently stored unique enable value (EV) associated with the hardware component and the protected resource, wherein the EV is stored in a secure location within the hardware component; and
a restricted software module based on at least the unique hardware ID for selectively enabling access to the protected resource, wherein the restricted software module is executed by the hardware component to:
generate or access an enable register (ER) value;
compare the ER value with the EV; and
allow access to the protected resource if the ER value and the EV match.