Requirement
The entity authorises, designs, develops or acquires, configures, documents, tests, approves and implements changes to infrastructure, data, software and procedures to meet its objectives.
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 |
|---|---|---|---|
| GDPR | Art.25 | Data protection by design and by default | sdlc |
| ISO 27001 | A.5.8 | Information security in project management | sdlc |
| ISO 27001 | A.8.25 | Secure development life cycle | sdlc |
| ISO 27001 | A.8.31 | Separation of development, test and production environments | sdlc |
| ISO 27001 | A.8.32 | Change management | change-management |
| PCI DSS 4.0.1 | 6.2 | Bespoke and custom software is developed securely | sdlc |
| PCI DSS 4.0.1 | 6.5 | Change management and separation of environments | change-management |
| GLBA | 314.4(c)(4) | Secure development and assessment of applications | sdlc |