Seeded demo · auth off · no application database · GitLab SoT / GitHub twin · not an ATO

6.3.3 — Security patch installation within SLA

NIST SP 800-53 Revision 5 · assessed by internal audit

RegisterNot metHighretest overdue
What this requires
In plain language: the outcome this security requirement is meant to achieve.

All system components are protected from known vulnerabilities by installing applicable security patches.

How we check it

Confirm critical patches applied within one month and all others within three months.

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.
ArtifactKindStatusCollectedExpiresSourceDigest
Patch deployment evidence — August
Auto-collected301 KB
Log extractExpired5 May 20265 Aug 2026
Ansible
collector-bot
fa50b61c72d8…
Problems
Open issues tied to this requirement. 1 total.
FND-1044CriticalOpenCVE-2026-21841
Critical container base image patches exceed 30-day SLA

Nine production container images are running base layers with unpatched critical CVEs first detected between 41 and 78 days ago, exceeding the one-month patch window required by PCI DSS 6.3.3.

Remediation Rebuild affected images against the hardened base tag 2026.08 and enable the automated base-image bump job.

Automated scanregistry/northwind/*opened 14 Jun 2026due 14 Jul 2026
Test record
Framework
NIST 800-53 5.1.1
Domain
Vulnerability Mgmt
Test method
Automated
Last tested
19 Aug 2026
Next due
5 Aug 2026
Retest window
18d overdue
Accountable owner
Tomas LindqvistApplication Securitytomas.l@northwind.io
Audit period
NIST SP 800-53 Revision 5
Window
— – —
Authority
NIST
Assessor
Internal audit