Seeded demo · auth off · no application database · GitLab SoT / GitHub twin · not an ATO
2.2.1 — System component configuration standards
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.
Configuration standards are developed, implemented, and maintained to cover all system components.
How we check it
Sample 15 hosts and compare against the CIS benchmark baseline.
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 |
|---|---|---|---|---|---|---|
| CIS benchmark scan — 15 host sample Auto-collected267 KB | Scan report | Expiring | 25 Jul 2026 | 8 Sep 2026 | Wiz collector-bot | 3e94fa50b61c… |
Problems
Open issues tied to this requirement. 1 total.
FND-1008LowResolved
Baseline standard not updated for the new ARM host class
A newly introduced ARM instance family has no corresponding entry in the configuration standard, so hosts in that class are unbaselined.
Remediation Standard extended to the ARM family and applied via the hardening playbook.
Manual testaws/prod-458821opened 18 Apr 2026due 1 Jun 2026
Test record
- Framework
- NIST 800-53 5.1.1
- Domain
- Configuration
- Test method
- Automated
- Last tested
- 25 Jul 2026
- Next due
- 22 Aug 2026
- Retest window
- 1d overdue
Accountable owner
Audit period
NIST SP 800-53 Revision 5
- Window
- — – —
- Authority
- NIST
- Assessor
- Internal audit