3.4.3
CM.L2-3.4.3 · Level 2
Track, review, approve or disapprove, and log changes to organizational systems.
NIST SP 800-171 Rev 2 · §3.4.3
Track, review, approve or disapprove, and log changes to organizational systems.
Assessment objectives
From NIST SP 800-171A · 4 objectives must be met to satisfy this control
Examine
[SELECT FROM: Configuration management policy; procedures addressing system configuration change control; configuration management plan; system architecture and configuration documentation; security plan; change control records; system audit logs and records; change control audit and review reports; agenda/minutes from configuration change control oversight meetings; other relevant documents or records].
Interview
[SELECT FROM: Personnel with configuration change control responsibilities; personnel with information security responsibilities; system or network administrators; members of change control board or similar].
Test
[SELECT FROM: Organizational processes for configuration change control; mechanisms that implement configuration change control].
Examine
[SELECT FROM: Configuration management policy; procedures addressing system configuration change control; configuration management plan; system architecture and configuration documentation; security plan; change control records; system audit logs and records; change control audit and review reports; agenda/minutes from configuration change control oversight meetings; other relevant documents or records].
Interview
[SELECT FROM: Personnel with configuration change control responsibilities; personnel with information security responsibilities; system or network administrators; members of change control board or similar].
Test
[SELECT FROM: Organizational processes for configuration change control; mechanisms that implement configuration change control].
Examine
[SELECT FROM: Configuration management policy; procedures addressing system configuration change control; configuration management plan; system architecture and configuration documentation; security plan; change control records; system audit logs and records; change control audit and review reports; agenda/minutes from configuration change control oversight meetings; other relevant documents or records].
Interview
[SELECT FROM: Personnel with configuration change control responsibilities; personnel with information security responsibilities; system or network administrators; members of change control board or similar].
Test
[SELECT FROM: Organizational processes for configuration change control; mechanisms that implement configuration change control].
Examine
[SELECT FROM: Configuration management policy; procedures addressing system configuration change control; configuration management plan; system architecture and configuration documentation; security plan; change control records; system audit logs and records; change control audit and review reports; agenda/minutes from configuration change control oversight meetings; other relevant documents or records].
Interview
[SELECT FROM: Personnel with configuration change control responsibilities; personnel with information security responsibilities; system or network administrators; members of change control board or similar].
Test
[SELECT FROM: Organizational processes for configuration change control; mechanisms that implement configuration change control].
What we look for in practice
The following are placeholder notes that should be refined based on practice experience.
What assessors look for in practice. Documented evidence that this control is implemented across all CUI-handling systems within scope. Specific artifacts vary, but expect requests for written procedures, system configurations, and operational records demonstrating the control is active.
Common failure patterns. Typical issues include incomplete documentation, inconsistent implementation across systems, and missing periodic review records. Refine this section as your practice accumulates direct assessment experience.
Strong evidence looks like. Formal policy referencing this control, technical configurations demonstrating enforcement, periodic review logs with sign-off, and procedures for handling exceptions.
Scoring and POA&M context. 1-point control under the DoD Assessment Methodology. Lower scoring impact, but still required for full compliance. POA&M-eligible — deferral up to 180 days is allowed under conditional certification per 32 CFR 170.21.