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

A.8.8 — Management of technical vulnerabilities

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

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

Information about technical vulnerabilities shall be obtained and appropriate measures taken.

How we check it

Confirm all critical vulnerabilities are remediated within the 14-day policy SLA.

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
Vulnerability SLA compliance report
Auto-collected199 KB
Scan reportValid19 Aug 202619 Sep 2026
Trivy
collector-bot
b61c72d83e94…
Problems
Open issues tied to this requirement. 1 total.
FND-1043CriticalAwaiting verificationCVE-2026-31022
Two internet-facing services affected by known-exploited RCE

Two internet-facing services depend on a library version affected by a remote code execution vulnerability listed in the CISA Known Exploited Vulnerabilities catalog.

Remediation Patch to 4.9.2 in both services, then confirm remediation with an authenticated rescan before closing.

Automated scansvc-gateway, svc-webhooksopened 11 Aug 2026due 25 Aug 2026
Test record
Framework
NIST 800-53 5.1.1
Domain
Vulnerability Mgmt
Test method
Automated
Last tested
19 Aug 2026
Next due
12 Aug 2026
Retest window
11d overdue
Accountable owner
Tomas LindqvistApplication Securitytomas.l@northwind.io
Audit period
NIST SP 800-53 Revision 5
Window
— – —
Authority
NIST
Assessor
Internal audit