During a post-incident review, an auditor asks the development manager which DevSecOps practice MOST directly enforces that no unauthorised or unreviewed change reaches production, regardless of the developer who proposed it. Which practice should the manager identify?
- ABranch protection rules that require peer code review and signed commits before a merge to the release branch is permitted.
- BMandatory secure coding training for all engineers, refreshed annually and tracked through the learning management system.
- CAn immutable, fully automated deployment pipeline whose promotion to production requires a recorded change approval and rejects manually built artefacts. Correct
- DContinuous vulnerability scanning of production workloads with automated ticketing for findings above a defined CVSS threshold.
Why A is wrong: Peer review and signed commits are strong controls over what enters the codebase, but they sit before the deployment step. A reviewed commit can still bypass production controls if the deployment pipeline itself is not gated, so this is necessary but not the most direct answer to the auditor's question.
Why B is wrong: Training raises the floor of developer capability but is a preventative awareness control, not an enforcement mechanism against unauthorised production change. It would not stop a determined or careless developer from pushing an unapproved artefact.
Why C is correct: An automated pipeline that only accepts artefacts produced by the pipeline itself, coupled with a recorded approval gate for production, enforces separation of duties and change management for every promotion, irrespective of who proposed the change. This is the control closest to the auditor's concern.
Why D is wrong: Runtime scanning detects weaknesses after deployment. It does not prevent an unauthorised or unreviewed change from reaching production in the first place, which is precisely what the auditor is probing.