# Separation of duty

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

NIST defines separation of duty as the principle that no user should be given enough privileges to misuse the system on their own. In cloud, it means the people who change a control are not the only people who can approve it or erase its logs. It is a reason for separate security and workload roles.

## An example, sourced

The log protection check applies it to audit logs.

## Why it matters here

On Cloud Security Risk Assessment the term appears in the rubric and on the platform pages; the example above was read on 16 Nov 2026 from the page under Sources.

## Related pages

- [Service account key: meaning and an example](/glossary/service-account-key/)
- [Service control policy: meaning and an example](/glossary/service-control-policy/)
- [Standing privilege: meaning and an example](/glossary/standing-privilege/)
- [All of them](/glossary/)

## Sources

- https://csrc.nist.gov/glossary/term/separation_of_duty (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecurityriskassessment.com/glossary/separation-of-duty/
