HSM Cryptographic Algorithm Execution With Policy-Constrained Code
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing hardware security modules (HSMs) face challenges in efficiently adding new cryptographic algorithms without disrupting service and maintaining security, particularly when combining operations and managing cryptographic keys with complex policies.
Innovation Solution
A method and device that allow new cryptographic algorithms to be executed on HSMs by providing client-provided program code, constrained by policies embedded in access control lists, enabling secure execution without firmware upgrades, and allowing flexible algorithm combinations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If new cryptographic algorithms are added to HSM through firmware upgrades, then the algorithm support is improved, but service interruption occurs and device complexity increases
Solution Approach 1:
The patent segments the cryptographic algorithm implementation into two parts: (1) a trusted firmware layer that provides the secure execution environment and key management, and (2) user-provided algorithm code that can be loaded and executed without firmware updates. This allows new algorithms to be added by loading new code segments rather than updating the entire firmware, thus avoiding service interruption while maintaining security through the trusted firmware layer.
Solution Approach 2:
The patent implements preliminary action by pre-establishing a trusted execution environment and policy enforcement mechanism in the firmware before new algorithms are needed. The firmware includes pre-configured access control lists and policy evaluation capabilities that can constrain and control user-provided algorithm code. This preliminary setup allows rapid deployment of new algorithms without requiring firmware reconfiguration or service interruption.
2Adaptability or versatility
If user-provided code is executed on HSM, then algorithm flexibility is improved, but security risk increases
Solution Approach 1:
The patent introduces an intermediary layer consisting of access control lists and policy evaluation mechanisms that stand between the user-provided algorithm code and the cryptographic key material. These intermediaries enforce security policies, validate code permissions, and control access to sensitive resources. This allows flexible user-provided code to execute while maintaining security through the intermediary policy enforcement layer.
Solution Approach 2:
The patent applies local quality by assigning different security policies and access control permissions to different parts of the user-provided code. Instead of treating all user code uniformly, the system can apply fine-grained access control lists that constrain specific code segments to specific operations or data. This enables algorithm flexibility while maintaining security through localized policy enforcement at critical points in the code execution.
3Reliability
If complex cryptographic policies are enforced, then security is improved, but operational complexity increases
Solution Approach 1:
The patent implements self-service by enabling the HSM to automatically evaluate and enforce security policies without requiring manual intervention. The firmware includes built-in policy evaluation capabilities that automatically check access control lists, validate code permissions, and enforce cryptographic policies during algorithm execution. This automated self-service approach maintains complex security enforcement while simplifying operations by eliminating the need for manual policy management.
Data Source
AI summary
A computer implemented method comprising: obtaining first data, comprising a representation of computer program code that embodies a cryptographic algorithm; obtaining second data; receiving a request for a first mechanism to be performed, the request comprising information identifying the first mechanism, and information identifying the first data as corresponding to a program and the second data as corresponding to an input; performing the first mechanism, wherein performing the first mechanism comprises: performing a first determination, the first determination comprising: determining whether a first policy associated with the second data permits the second data to be used with the program represented in the first data, and determining whether a third policy associated with the computer program code permits the computer program code to be used with the second data; and if the first determination is successful, executing the program represented in the first data taking the second data as input.