TEE Capability Exposure via SE Certificate-Based Security Gating
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The security of executing a service using a TEE + SE security architecture is not ensured due to the lower security level of the TEE, which can be vulnerable to attacks.
Innovation Solution
The secure element (SE) establishes a session with the TEE, obtains a security certificate, and determines the TEE's secure state based on the certificate and a preset policy, enabling capabilities only when the TEE is secure, thereby ensuring the security of service execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the TEE + SE security architecture is used to execute services, then the service execution capability is improved, but the security level is reduced due to the TEE's lower security level compared to SE
Solution Approach 1:
The patent applies preliminary action by verifying the TEE's security state before enabling service execution. The SE checks the security certificate and determines the TEE's secure state in advance, and only then enables the capability for third-party services. This ensures that services are only executed when the TEE is confirmed to be in a secure state, preventing security vulnerabilities from compromising service execution.
2Adaptability or versatility
If the TEE's capability is enabled for third-party services, then the service functionality is improved, but the security risk increases when the TEE has security vulnerabilities
Solution Approach 1:
The patent uses the SE as an intermediary between the TEE and third-party services. The SE acts as a mediator that verifies the TEE's security state through security certificates and determines whether to enable TEE capabilities for third-party services. This intermediary mechanism isolates the direct connection between TEE and third-party services, adding a security verification layer that prevents harmful factors from affecting the system when TEE vulnerabilities exist.
Solution Approach 2:
The system performs preliminary verification of the TEE's security state before enabling third-party service access. By checking the security certificate and determining the secure state in advance, the system ensures that TEE capabilities are only exposed to third-party services when security requirements are met, thereby reducing security risks while maintaining service functionality.
3Reliability
If the SE verifies the TEE's security state before enabling capabilities, then the security level is improved, but the system complexity increases
Solution Approach 1:
The TEE performs self-verification by generating and providing its own security certificate to the SE. The TEE autonomously manages its security state information and presents it for verification, reducing the need for complex external verification mechanisms. This self-service approach simplifies the overall system complexity while maintaining high security levels through the verification process.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A capability enabling method and apparatus are provided, to resolve a prior-art problem that security of executing a service by using a TEE + SE security architecture cannot be ensured. In this application, an SE establishes, with a TEE, a session used for communication. The SE sends, to the TEE by using the session, an obtaining instruction used to obtain a security certificate of the TEE. The TEE receives, by using the session, the obtaining instruction from the SE. After receiving the obtaining instruction, the TEE generates the security certificate based on attribute information of the TEE, and sends the generated security certificate to the SE by using the session. After the SE receives, by using the session, the security certificate sent by the TEE, the SE determines, based on the security certificate and a preset security policy, that the TEE is in a secure state. After the SE determines that the TEE is in the secure state, the SE enables a first capability for a third-party service in the SE, where the first capability is implemented based on a second capability of the TEE.