← NIST CSF 2.0 · PROTECT — Platform Security
PR.PS-06 — Secure software development practices are integrated
Requirement
Secure software development practices are integrated and their performance is monitored throughout the software development life cycle.
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.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared 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 |
| GLBA | 314.4(c)(4) | Secure development and assessment of applications | secure-development sdlc |
| 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 |