A security control is a measure chosen to address a specific threat or meet an applicable security obligation. Start with the risk or requirement, not a generic security tier: a payments service and a marketing website face different threats and may justify different controls. Regulatory obligations are a separate question—first establish which ones apply, then decide how to meet them. section 2.3
A practical way to select controls is to:
- Identify applicable obligations. PCI DSS, for example, prescribes controls for companies processing credit card data; other standards and sector mandates create different requirements. section 2.3.3
- Identify threats particular to the system, beyond those anticipated by broad standards. Use each threat to establish a security requirement and select a control that addresses it. section 2.3 section 2.3.3
- Check relevant internal requirements, ideally through a centralized catalog organized by use case, and involve legal, privacy, and security stakeholders while architectural options remain open. section 2.3.3 section 2.3.4
Protecting personal data at rest
A requirement to protect stored personal data does not automatically call for application-level encryption with a full key lifecycle. Cloud-platform storage encryption may be a reasonable alternative. Compare the protection gained with implementation and operational costs, and agree on a proportionate approach with compliance stakeholders. section 2.3.4
A control must work in practice, not merely exist on a checklist. Excessive access reviews can become rubber-stamping, leaving the control ineffective while burdening teams. Reassess controls against the risk they are meant to address and the cost of operating them. section 2.3.4

