Consistency Analysis
LOW MODERATE HIGHRequirements NIST SOURCE
Employ the following actions to validate that policies are established and implemented controls are operating in a consistent manner: [organization-defined actions].
Discussion (NIST Supplemental Guidance)
Security and privacy controls are often added incrementally to a system. As a result, policies for selecting and implementing controls may be inconsistent, and the controls could fail to work together in a consistent or coordinated manner. At a minimum, the lack of consistency and coordination could mean that there are unacceptable security and privacy gaps in the system. At worst, it could mean that some of the controls implemented in one location or by one component are actually impeding the functionality of other controls (e.g., encrypting internal network traffic can impede monitoring). In other situations, failing to consistently monitor all implemented network protocols (e.g., a dual stack of IPv4 and IPv6) may create unintended vulnerabilities in the system that could be exploited by adversaries. It is important to validate—through testing, monitoring, and analysis—that the implemented controls are operating in a consistent, coordinated, non-interfering manner.
Implementation Guidance
Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.
No engineering interpretation has been authored for CA-7(5) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.
Assessment
Assessment Objectives
- actions to validate that policies are established are defined;
- actions to validate that implemented controls are operating in a consistent manner are defined;
- <CA-07(05)_ODP[01] actions> are employed to validate that policies are established;
- <CA-07(05)_ODP[02] actions> are employed to validate that implemented controls are operating in a consistent manner.
Examine
[SELECT FROM: Assessment, authorization, and monitoring policy; organizational continuous monitoring strategy; system-level continuous monitoring strategy; procedures addressing continuous monitoring of system security controls; assessment report; plan of action and milestones; system monitoring records; security impact analyses; status reports; system security plan; other relevant documents or records].
Interview
[SELECT FROM: Organizational personnel with continuous monitoring responsibilities; organizational personnel with information security and privacy responsibilities].
Test
[SELECT FROM: Mechanisms supporting consistency analyses].
Overlays
STIGs & CCIs
No STIG checks or CCI mappings are currently loaded for CA-7(5). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.
Learn more about STIG/CCI integration →Evidence
Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.
Policy
- Assessment, authorization, and monitoring policy
- organizational continuous monitoring strategy
- system-level continuous monitoring strategy
- plan of action and milestones
- system security plan
Testing
- Mechanisms supporting consistency analyses
Other Records
- procedures addressing continuous monitoring of system security controls
- assessment report
- system monitoring records
- security impact analyses
- status reports
- other relevant documents or records