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

11.4.1 — Penetration testing methodology

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

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

A defined penetration testing methodology is implemented and followed.

How we check it

Review the pentest methodology document and the most recent engagement report.

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
Penetration test report — Helios engagement
Manual343 KB
AttestationValid5 Jun 20265 Dec 2026
Bishop Fox
Ruben Castillo
2d83e94fa50b…
Problems
Open issues tied to this requirement. 0 total.
No open findings
Test record
Framework
NIST 800-53 5.1.1
Domain
Pen Testing
Test method
Manual
Last tested
5 Jun 2026
Next due
5 Dec 2026
Retest window
in 104d
Accountable owner
Tomas LindqvistApplication Securitytomas.l@northwind.io
Audit period
NIST SP 800-53 Revision 5
Window
— – —
Authority
NIST
Assessor
Internal audit