Abstract: Disclosed herein are system, method, and computer program product embodiments for enabling access to a firmware-locked function of a secure device. A secure device may be production hardware that has locked certain functions not available for public use. In an embodiment, the secure device may receive a request to access a firmware-locked function. The request may include an authorization token that includes an identifier specific to the particular secure device and a permission identifier identifying the firmware-locked function. Based on the receipt of the authorization token, the secure device may retrieve authorization data from the firmware memory of the secure device to determine whether the provided authorization token matches the firmware authorization data. Using the authorization token, the secure device may determine whether to grant access to the firmware-locked function.

Abstract: Disclosed herein are system, method, and computer program product embodiments for enabling access to a firmware-locked function of a secure device. A secure device may be production hardware that has locked certain functions not available for public use. In an embodiment, the secure device may receive a request to access a firmware-locked function. The request may include an authorization token that includes an identifier specific to the particular secure device and a permission identifier identifying the firmware-locked function. Based on the receipt of the authorization token, the secure device may retrieve authorization data from the firmware memory of the secure device to determine whether the provided authorization token matches the firmware authorization data. Using the authorization token, the secure device may determine whether to grant access to the firmware-locked function.

Abstract: Disclosed herein are system, method, and computer program product embodiments for enabling access to a firmware-locked function of a secure device. A secure device may be production hardware that has locked certain functions not available for public use. In an embodiment, the secure device may receive a request to access a firmware-locked function. The request may include an authorization token that includes an identifier specific to the particular secure device. Based on the receipt of the authorization token, the secure device may retrieve authorization data from the firmware memory of the secure device to determine whether the provided authorization token matches the firmware authorization data. In an embodiment, the secure device may also utilize channel information for authentication purposes. Using the authorization token and/or channel information, the secure device may determine whether to grant access to the firmware-locked function.

Abstract: Disclosed herein are system, method, and computer program product embodiments for enabling access to a firmware-locked function of a secure device. A secure device may be production hardware that has locked certain functions not available for public use. In an embodiment, the secure device may receive a request to access a firmware-locked function. The request may include an authorization token that includes an identifier specific to the particular secure device. Based on the receipt of the authorization token, the secure device may retrieve authorization data from the firmware memory of the secure device to determine whether the provided authorization token matches the firmware authorization data. In an embodiment, the secure device may also utilize channel information for authentication purposes. Using the authorization token and/or channel information, the secure device may determine whether to grant access to the firmware-locked function.