← GLBA · Safeguards Rule (16 CFR 314)

314.4(c)(4) — Secure development and assessment of applications

high secure-developmentsdlc

Requirement

Secure development practices are adopted for in-house developed applications used to transmit, access or store customer information, and procedures exist for evaluating, assessing or testing the security of externally developed applications the institution uses.

What the engine looks for

Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.

Required element 1 — any one of
secure developmentsecure codingsdlccode reviewapplication securityappsec
Required element 2 — any one of
in-housedevelopedthird-party applicationsexternal applicationsvendor applicationstestedtestingassess…evaluat…
Supporting terms — specificity signals
314.4(c)(4)owaspsastdast

Equivalent controls elsewhere

Matched on shared topics. Satisfying this control usually moves these too.

FrameworkControlTitleShared topics
ISO 27001 A.8.25 Secure development life cycle sdlc secure-development
PCI DSS 4.0.1 6.2 Bespoke and custom software is developed securely secure-development sdlc
NIST CSF 2.0 PR.PS-06 Secure software development practices are integrated sdlc secure-development
GDPR Art.25 Data protection by design and by default sdlc
SOC 2 CC8.1 Authorised change management sdlc
ISO 27001 A.5.8 Information security in project management sdlc
ISO 27001 A.8.28 Secure coding secure-development
ISO 27001 A.8.31 Separation of development, test and production environments sdlc