What this control covers
Develop security and privacy architectures that define approaches for protecting organizational information, processing personally identifiable information, and integrating into the enterprise architecture. The architectures should address dependencies on external systems and services, be updated regularly, and reflect planned changes in security and privacy plans, CONOPS, and organizational procedures. This control supports the Security and Privacy Architecture Design capability within the Planning family.
Why it matters
Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.
How to implement
AWS
Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.
Azure
Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.
Google Workspace
Use Data Export (Takeout-style) and Vault search to scope DSARs. Apply Drive labels + DLP so personal data classes are discoverable.
On-premises
Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.
Evidence to collect
policy_document— A signed, version-controlled policy stating leadership intent and the named owner.
Signed policy or standard documents the safeguard. Focus: Security And Privacy Architectures.
Quick checklist
- Policy — Procedures / Management
- Information — Procedures / Management
- Security — Procedures / Management
- Changes — Procedures / Management
- Control — Procedures / Management
- Address — Procedures / Management
Related articles on this site
- NIST 800-171 3.4.2 Establish and enforce security configuration settings for information technology products employed in organizational systems.
- NIST 800-171 3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
- CMMC 2.0 CM.2.064 Establish and enforce security configuration settings for information technology products employed in organizational systems.
- CMMC 2.0 SC.3.180 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.