NIST SP 800-53 Rev. 5 SA-5(3) — High-Level Design

What this control requires

Include security requirements in acquisition processes to ensure high-level design meets protection needs. This control supports the System Design Document capability within the System and Services Acquisition family.

In plain English

Include security requirements in acquisition processes to ensure high-level design meets protection needs. In practice, this means you can prove you policy 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.

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-5(3)) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Policy. Document the trigger, the owner and the cadence.
• Security. Document the trigger, the owner and the cadence.
• Protection. Document the trigger, the owner and the cadence.
• System. Document the trigger, the owner and the cadence.
• Control. Document the trigger, the owner and the cadence.
• Scope: management, system, protection, services, capability, policy, requirements, security.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.
• Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Signed policy or standard documents the safeguard. Focus: High-Level Design.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

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.23 — Information security for use of cloud services
• HIPAA (45 CFR Part 164) 164.314(a)(2)(ii) — Other Arrangements
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions
• NIST SP 800-171 Rev. 3 3.4.11 — Information Location
• SOC 2 (2017 TSC) PI1.3 — Processing Controls

Related controls in NIST SP 800-53 Rev. 5

• Control SA-5(4) — Low-Level Design
• Control SA-12(1) — Acquisition Strategies, Tools, And Methods
• Control SA-5(1) — Functional Properties Of Security Controls
• Control SA-21(1) — Validation Of Screening
• Control SA-8(26) — Performance Security
• Control SA-2 — Allocation Of Resources

References

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

Topics: governance riskpolicy management