Seeded demo · auth off · no application database · GitLab SoT / GitHub twin · not an ATO
A.8.9 — Configuration management
NIST SP 800-53 Revision 5 · assessed by internal audit
Data as of23 Aug 2026
What this requires
In plain language: the outcome this security requirement is meant to achieve.
Configurations of hardware, software, services and networks shall be established and maintained.
How we check it
Compare deployed infrastructure against the declared baseline; investigate drift.
Source mappings
Traceability from this Rev. 5 control to DAAG, organizational guidance, and DCSA supplemental guidance.
DAAG reference
Not supplied in uploaded sources
Organization document
Not supplied in uploaded sources
Implementation narrative
Not supplied in uploaded SSP
DCSA supplemental guidance
Not supplied in uploaded sources
Proof
Documents and records that show this requirement is met.
| Artifact | Kind | Status | Collected | Expires | Source | Digest |
|---|---|---|---|---|---|---|
| Infrastructure drift report Auto-collected207 KB | Scan report | Expiring | 30 Jul 2026 | 5 Sep 2026 | Terraform Cloud collector-bot | 2d83e94fa50b… |
Problems
Open issues tied to this requirement. 1 total.
FND-1035MediumRemediating
Configuration drift on 14 EC2 hosts against CIS baseline
Fourteen hosts have drifted from the declared baseline, most commonly re-enabled password authentication over SSH and disabled audit daemon.
Remediation Re-apply the hardening playbook and enable drift auto-remediation for the sshd and auditd resources.
Automated scanaws/prod-458821opened 30 Jul 2026due 27 Aug 2026
Test record
- Framework
- NIST 800-53 5.1.1
- Domain
- Configuration
- Test method
- Automated
- Last tested
- 30 Jul 2026
- Next due
- 30 Aug 2026
- Retest window
- in 7d
Accountable owner
Audit period
NIST SP 800-53 Revision 5
- Window
- — – —
- Authority
- NIST
- Assessor
- Internal audit