Android Security Modules Framework Extensible Reference Monitor
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Android operating systems lack an extensible security framework that can effectively manage different classes of users, such as consumers, enterprises, and governments, due to insufficient protection semantics in existing security architectures.
Innovation Solution
The Android Security Modules (ASM) framework provides a programmable interface for building reference monitors, allowing for the registration of security authorization hooks, callbacks for protected events, and access control decisions, enabling extensible security enhancements while minimizing performance overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If existing security architectures are used in Android, then basic security protection is provided, but they lack sufficient protection semantics for different classes of OS customers and cannot effectively manage consumers, enterprises, and governments
Solution Approach 1:
The security framework employs dynamic access control decisions where the reference monitor can grant or deny permissions based on real-time conditions. The system dynamically adjusts security policies for different customer classes (consumer, enterprise, government) without requiring firmware modifications, allowing the same hardware platform to serve multiple security requirements flexibly
Solution Approach 2:
The security architecture segments protection into distinct classes through separate reference monitors and authorization hooks. Each customer class can have its own security module (e.g., consumer security module, enterprise security module) that operates independently but coordinates through the unified reference monitor interface, enabling tailored protection semantics for different organizational needs
2Reliability
If security enhancements are added to Android, then protection semantics are improved, but the system complexity increases due to multiple security modules and hooks
Solution Approach 1:
The reference monitor serves as a universal interface that handles security enforcement for multiple customer classes and security modules through a single standardized API. Rather than requiring separate enforcement mechanisms for each security requirement, the reference monitor consolidates access control decisions, permission management, and authorization hooks into one multi-functional component that reduces overall system complexity
Solution Approach 2:
The reference monitor acts as an intermediary between security modules and the rest of the system. Security modules register their authorization hooks with the reference monitor, which then mediates all access control decisions. This intermediary layer abstracts the complexity of multiple security modules from the applications and system components, presenting a simplified unified security interface
3Stability of the object's composition
If traditional desktop and server OS security designs are used, then established security models are maintained, but they do not adequately support new application architectures with semantically rich APIs
Solution Approach 1:
The patent replaces traditional mechanical permission strings and access control lists with a programmable security model using authorization hooks and callbacks. Instead of static permission declarations, the system uses dynamic hook functions that can be registered, unregistered, and modified programmatically, allowing security policies to adapt to semantically rich APIs and complex application architectures while maintaining stable enforcement through the reference monitor
Data Source
AI summary
Methods, systems, and computer readable media for extending security of an application-based computer operating system are disclosed. One system includes a memory. The system also includes an application-based operating system security module bridge implemented using the memory. The application-based operating system security module bridge is for receiving, from a reference monitor, a registration for at least one security authorization hook, for receiving a callback when a protected event occurs, for communicating with the reference monitor that registered the at least one security authorization hook corresponding to the callback, and for receiving, from the reference monitor, an access control decision associated with the protected event.