Separation of duties is often implemented between developers and administrators in order to separate which of the following?

The correct answer is B. Changes to program code and the ability to deploy to production. Separation of duties (SoD) is a security principle that divides critical tasks among multiple people to prevent fraud, errors, and abuse of privilege. Between developers and administrators, the key separation is: developers write and modify code, while administrators…

Security program management and oversight

Question

Options

AMore experienced employees from less experienced employees
BChanges to program code and the ability to deploy to production
CUpper level management users from standard development employees
DThe network access layer from the application access layer

How the community answered

(43 responses)

A
5% (2)
B
93% (40)
C
2% (1)

Explanation

Separation of duties (SoD) is a security principle that divides critical tasks among multiple people to prevent fraud, errors, and abuse of privilege. Between developers and administrators, the key separation is: developers write and modify code, while administrators (ops/deployment teams) control what gets deployed to production. This prevents a developer from writing malicious code and also deploying it undetected - a second party must approve and execute the production deployment. This is a core control in change management and software security. The other options describe seniority (A), organizational hierarchy (C), or network architecture (D), none of which are the purpose of this specific SoD control.

Topics

#separation of duties#change management#least privilege#access control

Community Discussion

No community discussion yet for this question.

Full SY0-301 Practice