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

6.3.1 — Identification of security 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.

Security vulnerabilities are identified and managed with an assigned risk ranking.

How we check it

Confirm every identified vulnerability carries a risk ranking and an owner.

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 risk ranking register
Auto-collected292 KB
Scan reportRejected19 Aug 202619 Sep 2026
Trivy
collector-bot
83e94fa50b61…
Problems
Open issues tied to this requirement. 1 total.
FND-1047HighOpen
Vulnerability register missing risk ranking for 34 findings

The vulnerability register contains 34 entries with no assigned risk ranking or owner, so they are excluded from SLA tracking entirely. PCI DSS 6.3.1 requires a risk ranking on every identified vulnerability.

Remediation Backfill rankings using the CVSS-plus-exploitability rubric and reject scanner output that lacks a ranking.

External audittrivy/registry-scanopened 19 Aug 2026due 2 Sep 2026
Test record
Framework
NIST 800-53 5.1.1
Domain
Vulnerability Mgmt
Test method
Automated
Last tested
19 Aug 2026
Next due
10 Aug 2026
Retest window
13d overdue
Accountable owner
Tomas LindqvistApplication Securitytomas.l@northwind.io
Audit period
NIST SP 800-53 Revision 5
Window
— – —
Authority
NIST
Assessor
Internal audit