NIST SP 800-53 Rev. 5 SA-3 — System Development Life Cycle

What this control requires

Use a defined system development life cycle to guide acquisition and management, integrating security and privacy requirements from early design through deployment, and assigning clear roles and responsibilities. This control supports the Secure Lifecycle Framework capability within the System and Services Acquisition family.

In plain English

Use a defined system development life cycle to guide acquisition and management, integrating security and privacy requirements from early design through deployment, and assigning clear roles and responsibilities. In practice, this means you can prove you access management-level controls on a defined cadence.

Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within System and Services Acquisition, the assessor will trace your implementation back to the catalogue reference (Control SA-3) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Access. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Review. Document the trigger, the owner and the cadence.
• System. Document the trigger, the owner and the cadence.
• Identity. Document the trigger, the owner and the cadence.
• Scope: management, privacy, system, identity, review, services, capability, roles.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: System Development Life Cycle.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• ISO/IEC 27001:2022 A.5.15 — Access control
• NIST SP 800-171 Rev. 3 3.15.2 — System Security Plan
• CIS Controls v8 9.2 — Use DNS Filtering Services
• SOC 2 (2017 TSC) P5.1 — Data Subject Access to Personal Information

Related controls in NIST SP 800-53 Rev. 5

• Control SA-8(5) — Efficiently Mediated Access
• Control SA-8(18) — Trusted Communications Channels
• Control SA-18(1) — Multiple Phases Of System Development Life Cycle
• Control PS-9 — Position Descriptions
• Control SA-8(9) — Trusted Components
• Control AT-3 — Role-Based Training

References

• NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5
• Catalogue identifier: Control SA-3

Topics: identity accessidentity managementaccess reviewprivileged accessprivacy management