NIST SP 800-53 Rev. 5 SA-17(3) — Formal Correspondence

What this control requires

Require developers to produce a formal top-level specification for interfaces to security-relevant components. Demonstrate consistency with the formal policy model through proof and informal methods, ensure complete coverage, and describe internal mechanisms not addressed in the specification. This control supports the Formal Correspondence Validation Protocol capability within the System and Services Acquisition family.

In plain English

Require developers to produce a formal top-level specification for interfaces to security-relevant components. 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.

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-17(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-Relevant. Document the trigger, the owner and the cadence.
• Validation. Document the trigger, the owner and the cadence.
• Internal. Document the trigger, the owner and the cadence.
• System. Document the trigger, the owner and the cadence.
• Scope: management, system, components, services, capability, proof, policy, security.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Formal Correspondence.

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.

• HIPAA (45 CFR Part 164) 164.308(a)(5)(i) — Security Awareness and Training
• NIST SP 800-171 Rev. 3 3.4.11 — Information Location
• BSI C5:2020 SP-01 — Documentation, communication and provision of policies and instructions
• ISO/IEC 27001:2022 A.5.21 — Managing information security in the ICT supply chain

Related controls in NIST SP 800-53 Rev. 5

• Control SA-17(4) — Informal Correspondence
• Control SA-8(17) — Secure Distributed Composition
• Control SA-18 — Tamper Resistance And Detection
• Control SA-17(1) — Formal Policy Model
• Control SA-19(1) — Anti-Counterfeit Training
• Control SA-22(1) — Alternative Sources For Continued Support

References

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

Topics: governance riskpolicy management