myctrl.tools
Compare

AC-25Reference Monitor

>Control Description

Implement a reference monitor for organization-defined access control policies that is tamperproof, always invoked, and small enough to be subject to analysis and testing, the completeness of which can be assured.

>Cross-Framework Mappings

>Supplemental Guidance

A reference monitor is a set of design requirements on a reference validation mechanism that, as a key component of an operating system, enforces an access control policy over all subjects and objects. A reference validation mechanism is always invoked, tamper-proof, and small enough to be subject to analysis and tests, the completeness of which can be assured (i.e., verifiable). Information is represented internally within systems using abstractions known as data structures.

Internal data structures can represent different types of entities, both active and passive. Active entities, also known as subjects, are associated with individuals, devices, or processes acting on behalf of individuals. Passive entities, also known as objects, are associated with data structures, such as records, buffers, communications ports, tables, files, and inter-process pipes.

Reference monitors enforce access control policies that restrict access to objects based on the identity of subjects or groups to which the subjects belong. The system enforces the access control policy based on the rule set established by the policy. The tamper-proof property of the reference monitor prevents determined adversaries from compromising the functioning of the reference validation mechanism.

The always invoked property prevents adversaries from bypassing the mechanism and violating the security policy. The smallness property helps to ensure completeness in the analysis and testing of the mechanism to detect any weaknesses or deficiencies (i.e., latent flaws) that would prevent the enforcement of the security policy.

>Related Controls

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

  • What formal policies and procedures govern the implementation of AC-25 (Reference Monitor)?
  • Who are the designated roles responsible for implementing, maintaining, and monitoring AC-25?
  • How frequently is the AC-25 policy reviewed and updated, and what triggers policy changes?
  • What training or awareness programs ensure personnel understand their responsibilities related to AC-25?

Technical Implementation:

  • Describe the specific technical mechanisms or controls used to enforce AC-25 requirements.
  • What automated tools, systems, or technologies are deployed to implement AC-25?
  • How is AC-25 integrated into your system architecture and overall security posture?
  • What configuration settings, parameters, or technical specifications enforce AC-25 requirements?

Evidence & Documentation:

  • What documentation demonstrates the complete implementation of AC-25?
  • What audit logs, records, reports, or monitoring data validate AC-25 compliance?
  • Can you provide evidence of periodic reviews, assessments, or testing of AC-25 effectiveness?
  • What artifacts would you present during a FedRAMP assessment to demonstrate AC-25 compliance?

Ask AI

Configure your API key to use AI features.