Control statement
- a.Develop, document, and disseminate to [Organization-defined: organization-defined personnel or roles]:
- 1.[Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy that:
- (a)Addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and
- (b)Is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines; and
- 2.Procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and the associated assessment, authorization, and monitoring controls;
- 1.[Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy that:
- b.Designate an [Organization-defined: official] to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures; and
- c.Review and update the current assessment, authorization, and monitoring:
- 1.Policy [Organization-defined: frequency] and following [Organization-defined: events] ; and
- 2.Procedures [Organization-defined: frequency] and following [Organization-defined: events].
Discussion
Assessment, authorization, and monitoring policy and procedures address the controls in the CA family that are implemented within systems and organizations. The risk management strategy is an important factor in establishing such policies and procedures. Policies and procedures contribute to security and privacy assurance. Therefore, it is important that security and privacy programs collaborate on the development of assessment, authorization, and monitoring policy and procedures. Security and privacy program policies and procedures at the organization level are preferable, in general, and may obviate the need for mission- or system-specific policies and procedures. The policy can be included as part of the general security and privacy policy or be represented by multiple policies that reflect the complex nature of organizations. Procedures can be established for security and privacy programs, for mission or business processes, and for systems, if needed. Procedures describe how the policies or controls are implemented and can be directed at the individual or role that is the object of the procedure. Procedures can be documented in system security and privacy plans or in one or more separate documents. Events that may precipitate an update to assessment, authorization, and monitoring policy and procedures include assessment or audit findings, security incidents or breaches, or changes in applicable laws, executive orders, directives, regulations, policies, standards, and guidelines. Simply restating controls does not constitute an organizational policy or procedure.
Organization-defined parameters
These values must be resolved through the organization’s tailoring and governance process. Bracketed parameter references in the control text identify where a decision is required.
From control text to operational evidence
Use Policy and Procedures as a testable risk decision. Translate the official statement into accountable people, repeatable processes, configured technology, and evidence that demonstrates the outcome over time. In this family, pay particular attention to assessment independence, authorization evidence, remediation, and continuous monitoring.
Implementation workflow
- Define the control boundary, responsible owner, inherited portions, and systems or processes in scope.
- Resolve each organization-defined parameter before declaring the control implemented.
- Document how the implementation satisfies every clause of the official control statement.
- Collect evidence as a normal byproduct of operation rather than only before an assessment.
- Review exceptions, changes, and monitoring results on a risk-based cadence.
Evidence examples
- assessment plans and reports
- plans of action and milestones
- authorization decisions and risk acceptances
- continuous monitoring results
Common failure patterns
- control status based only on owner assertion
- findings closed without evidence
- assessment scope that misses inherited services
- monitoring data disconnected from authorization decisions
Questions practitioners should ask
- What risk decision is this control intended to support in this system?
- Which parts are implemented locally, inherited, shared, or not applicable—and what evidence supports that decision?
- Do the documented narrative, deployed configuration, operating process, and collected evidence agree?
- What event or threshold requires the implementation to be reviewed or changed?
Assessment objectives and methods
Show the assessment objective
- CA-01a.
- CA-01a.[01]an assessment, authorization, and monitoring policy is developed and documented;
- CA-01a.[02]the assessment, authorization, and monitoring policy is disseminated to [Organization-defined: personnel or roles];
- CA-01a.[03]assessment, authorization, and monitoring procedures to facilitate the implementation of the assessment, authorization, and monitoring policy and associated assessment, authorization, and monitoring controls are developed and documented;
- CA-01a.[04]the assessment, authorization, and monitoring procedures are disseminated to [Organization-defined: personnel or roles];
- CA-01a.01
- CA-01a.01(a)
- CA-01a.01(a)[01]the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy addresses purpose;
- CA-01a.01(a)[02]the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy addresses scope;
- CA-01a.01(a)[03]the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy addresses roles;
- CA-01a.01(a)[04]the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy addresses responsibilities;
- CA-01a.01(a)[05]the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy addresses management commitment;
- CA-01a.01(a)[06]the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy addresses coordination among organizational entities;
- CA-01a.01(a)[07]the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy addresses compliance;
- CA-01a.01(b)the [Organization-defined: ca-01_odp.03] assessment, authorization, and monitoring policy is consistent with applicable laws, executive orders, directives, regulations, policies, standards, and guidelines;
- CA-01a.01(a)
- CA-01b.the [Organization-defined: official] is designated to manage the development, documentation, and dissemination of the assessment, authorization, and monitoring policy and procedures;
- CA-01c.
- CA-01c.01
- CA-01c.01[01]the current assessment, authorization, and monitoring policy is reviewed and updated [Organization-defined: frequency];
- CA-01c.01[02]the current assessment, authorization, and monitoring policy is reviewed and updated following [Organization-defined: events];
- CA-01c.02
- CA-01c.02[01]the current assessment, authorization, and monitoring procedures are reviewed and updated [Organization-defined: frequency];
- CA-01c.02[02]the current assessment, authorization, and monitoring procedures are reviewed and updated following [Organization-defined: events].
- CA-01c.01
Examine
- Assessment, authorization, and monitoring policy and procedures
- system security plan
- privacy plan
- other relevant documents or records
Interview
- Organizational personnel with assessment, authorization, and monitoring policy responsibilities
- organizational personnel with information security and privacy responsibilities
Related controls
These relationships come from the official OSCAL catalog. They indicate useful dependencies or context, not automatic inheritance or equivalence.
Authoritative sources
- OMB A-130 ↗
- SP 800-12 ↗
- SP 800-30 ↗
- SP 800-37 ↗
- SP 800-39 ↗
- SP 800-53A ↗
- SP 800-100 ↗
- SP 800-137 ↗
- SP 800-137A ↗
- IR 8062 ↗
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. Official control requirements and interpretations remain with NIST and the responsible authorizing organization.