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

A.8.25 — Secure development lifecycle

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

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

Rules for the secure development of software and systems shall be established and applied.

How we check it

Confirm threat modelling is completed for every new service before production release.

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
Threat model index by service
Manual233 KB
Policy documentExpiring1 Jul 20261 Sep 2026
Confluence
Hannah Feld
72d83e94fa50…
Problems
Open issues tied to this requirement. 1 total.
FND-1022MediumRemediating
Threat models absent for three services released this period

Three services reached production without a recorded threat model, contrary to the secure development lifecycle requirement.

Remediation Complete retrospective threat models and add the artifact as a release checklist gate.

Manual testsvc-ledger, svc-notify, svc-searchopened 1 Jul 2026due 29 Aug 2026
Test record
Framework
NIST 800-53 5.1.1
Domain
Secure SDLC
Test method
Manual
Last tested
1 Jul 2026
Next due
19 Aug 2026
Retest window
4d overdue
Accountable owner
Tomas LindqvistApplication Securitytomas.l@northwind.io
Audit period
NIST SP 800-53 Revision 5
Window
— – —
Authority
NIST
Assessor
Internal audit