Which control best enforces separation between development/testing environments and production in change management?

• A. No separation is required.
• B. Physical separation without access controls.
• C. Logical separation alone is sufficient.
• D. Separation from development/testing to production enforced by access controls and separate environments.

Answer: (D)

Separating development and testing from production and enforcing access controls on changes is essential to prevent untested changes from impacting live systems and to ensure every modification goes through formal, auditable processes. The best option combines both: you keep distinct environments for development/testing and production, and you restrict who can move or apply changes to production. This means developers can work in non-production spaces, while production changes are gated by access controls and a formal change-management workflow, ensuring proper testing, approval, and traceability. This approach directly reduces risks of accidental or malicious changes and supports accountability and compliance.

Simply having separation in one form isn’t enough. Physical separation without access controls could still be bypassed by those with physical or administrative access. Logical separation alone may not prevent production changes from slipping through if there aren’t separate environments and strict controls tying changes to an approved process. No separation at all leaves production vulnerable to untested updates and data exposure.