Compliance constraints are easier to address while architectural choices remain open. Legal obligations often describe outcomes rather than exact implementations, so engineering and compliance experts need to interpret them together. Keep requirements distinct from the controls chosen to meet them. section 2.3.4 section 2.5
Use a risk-proportionate approach:
- Bring legal, privacy, and security stakeholders into early design discussions to identify constraints such as data residency, retention, auditing, and third-party services. section 2.3.4
- Choose safeguards with attention to risk and data sensitivity; a platform’s storage-level encryption may meet an at-rest protection requirement without a more complex application-level scheme. section 2.3.4
- Avoid controls that create burden without meaningful protection: excessive access reviews can become rubber-stamping, while blanket bans on AI agents can delay learning before guidance exists. section 2.3.4















