Page Table Entry Security Configurations for Execution Domains
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional computer security systems rely on static domain hierarchies to enforce access control, which limits flexibility and effectiveness in protecting data and code between different execution domains, particularly when routines from different domains interact.
Innovation Solution
Implementing a non-hierarchical domain structure where page table entries specify sandboxing configurations to selectively deploy security measures, such as shadow stacks, based on the execution domains of calling and called routines, allowing for independent protection without relying on a predefined hierarchy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If static domain hierarchies are used to enforce access control, then access control is simplified, but flexibility and effectiveness in protecting data and code between different execution domains is limited
Solution Approach 1:
The patent segments the domain hierarchy into non-hierarchical execution domains, where each domain is independently defined rather than being part of a static hierarchy. This allows flexible configuration of access control policies between domains without being constrained by predefined hierarchical levels, thereby improving adaptability while reducing structural complexity.
Solution Approach 2:
The patent introduces dynamic domain configurations through page table entries that can be modified at runtime. Instead of a static hierarchy, domains can be dynamically created, merged, or have their access policies changed based on execution context, enabling flexible protection strategies without requiring complex hierarchical reconfiguration.
2Manufacturing precision
If hierarchical protection rings are used, then access control is enforced, but finer control over security operations and isolation between domains is limited
Solution Approach 1:
The patent applies local quality by allowing different access control policies to be applied to different domain pairs independently. Instead of uniform hierarchical protection, each domain combination can have customized security measures (such as shadow stacks) enabled or disabled based on specific execution context, achieving finer-grained control without requiring complex ring structures.
Solution Approach 2:
The patent changes the parameter of domain organization from hierarchical to non-hierarchical, allowing security control to be adjusted through page table entry configurations rather than fixed ring levels. This enables precise control over which security measures apply to which domain interactions, improving control precision while simplifying the overall structure.
3Reliability
If sandboxing is applied to all domain interactions, then data security is improved, but performance overhead increases
Solution Approach 1:
The patent applies partial sandboxing by selectively enabling security measures only for specific domain interactions that require them. Rather than applying sandboxing universally, the system uses page table entries to identify which domain pairs need protection and applies shadow stacks only in those cases, maintaining data security for critical interactions while avoiding unnecessary performance overhead for safe domain communications.
Data Source
AI summary
Systems, apparatuses, and methods related to a computer system having a page table entry containing security settings for calls from predefined domains are described. The page table entry can be used to map a virtual memory address to a physical memory address. In response to a call to execute a routine identified using the virtual memory address, a security setting corresponding to the execution domain from which the call initiates can be extracted from the page table entry to determine whether a security measure is to be used. For example, a shadow stack structure can be used to protect the private stack content of the routine from being access by a caller and/or to protect the private stack content of the caller from being access by the callee.