Control 3.4.3
Track, Review, Approve, and Log Configuration Changes
Official Requirement
Track, review, approve, or disapprove, and log changes to organizational information systems.
What This Means in Plain English
Every change to your IT systems must go through a formal process: proposed, reviewed, approved (or rejected), implemented, and logged. This prevents unauthorized changes and provides a record for troubleshooting and auditing.
How Petronella Implements This Control
Petronella Technology Group implements this control through:
- Formal change management process with change request, review, and approval stages
- Change Advisory Board (CAB) reviewing all significant system changes
- Arctic Wolf SIEM detecting and alerting on unauthorized configuration changes
- ComplianceArmor change management module tracking all changes from request through implementation
- Version control for firewall rules, GPOs, and infrastructure-as-code configurations
Assessment Guidance
Assessors will review the change management process documentation, verify that recent changes went through the approval process, check change logs for completeness, and test that unauthorized changes are detected and flagged.
Common Implementation Gaps
- No formal change management process
- Changes made directly to production without approval
- Change logs incomplete or not maintained
- Emergency changes not retroactively documented
- No detection mechanism for unauthorized changes
Cross-Framework Mapping
| Framework | Mapped Controls |
|---|---|
| NIST SP 800-53 | CM-3 |
| PCI DSS | Req 6.4 - Follow change control processes for all changes |
Need Help Implementing 3.4.3?
Our CMMC-RP certified team can assess your current compliance posture and build a remediation plan.
Schedule a Compliance Assessment