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

6.2.4 — Secure software engineering techniques

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

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

Software engineering techniques prevent or mitigate common software attacks in bespoke software.

How we check it

Review secure coding standards and confirm developer training completion for the period.

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
Secure coding training completion (94%)
Manual284 KB
AttestationValid16 Jul 202616 Jan 2027
Workday
Ruben Castillo
1c72d83e94fa…
Problems
Open issues tied to this requirement. 0 total.
No open findings
Test record
Framework
NIST 800-53 5.1.1
Domain
Secure SDLC
Test method
Manual
Last tested
16 Jul 2026
Next due
16 Jan 2027
Retest window
in 146d
Accountable owner
Tomas LindqvistApplication Securitytomas.l@northwind.io
Audit period
NIST SP 800-53 Revision 5
Window
— – —
Authority
NIST
Assessor
Internal audit