Security Context Permissions Adapted to Device State
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing systems fail to adjust security contexts provisioned to a computing device based on varying device states, leading to either unnecessary restrictions or security vulnerabilities.
Innovation Solution
Provisioning devices with device state access control policies that define different permissions for different device states, allowing the computing device to modify existing security contexts based on the device's state, thereby granting appropriate access to data assets without compromising security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If security contexts are provisioned with fixed permissions in NVM or OTP memory, then security is maintained through hardware-enforced access controls, but the system cannot adapt permissions based on varying device states, leading to either unnecessary restrictions or security vulnerabilities
Solution Approach 1:
The permission system is segmented into two distinct layers: (1) base permissions stored in secure hardware memory (NVM/OTP) that cannot be modified, and (2) dynamic permission modifications stored in volatile memory that can be updated based on device state. This segmentation allows the system to maintain the security guarantees of hardware-enforced access controls while adding the flexibility of runtime permission adjustments through the device state access control policy.
Solution Approach 2:
The system performs preliminary action by provisioning base security contexts with default permissions in secure hardware memory before the application runs. The device state access control policy is also pre-configured with the mapping between device states and permission modifications. At runtime, the system simply applies the pre-determined modifications based on the current device state, avoiding the need for complex runtime decision-making while maintaining both security and adaptability.
2Ease of operation
If fixed permissions are applied to applications, then security context verification is simplified at the root of trust, but applications cannot access necessary data assets when device conditions change, leading to operational limitations
Solution Approach 1:
The permission system transitions from a static, fixed-state model to a dynamic model where permissions are determined at runtime based on the current device state. The device state access control policy enables the system to automatically adjust permissions according to the device's current conditions (e.g., temperature, power state, security level), allowing applications to access necessary data assets when device conditions are favorable while maintaining security constraints when conditions are not favorable.
3Adaptability or versatility
If permissions are modified based on device state, then applications can access appropriate data assets under varying conditions, but the system complexity increases with additional policy management requirements
Solution Approach 1:
The device state access control policy acts as an intermediary layer between the secure hardware memory and the application execution environment. This policy layer absorbs the complexity of permission management by maintaining the mapping between device states and permission modifications, while presenting a simplified interface to both the hardware security subsystem and the applications. The policy management complexity is confined to this intermediary layer, preventing it from propagating to other system components.
Data Source
AI summary
A computing device receives a request to run an application. The application is associated with a security context. The computing device obtains one or more permissions associated with the security context and modifies the one or more permissions based on a state of the computing device. The application is run based on the modified one or more permissions.