What this control covers
The security and privacy architectures are developed to safeguard the confidentiality, integrity, and availability of organizational information, minimize privacy risks to individuals, and integrate into the enterprise architecture. The architecture considers dependencies on external systems and services, while being regularly updated and reflected in security and privacy plans. This control supports the Security Architecture Model 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: Defense In Depth.
Quick checklist
- Policy — Management / Information
- Information — Management / Information
- Security — Management / Information
- Control — Management / Information
- Individuals — Management / Information
- Privacy — Management / Information
Related articles on this site
- NIST 800-171 3.2.1 Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to
- 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 AT.2.056 Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to t