← SOC 2 · C1 — Confidentiality
C1.1 — Identification and protection of confidential information
high
data-classificationconfidentiality
Requirement
The entity identifies and maintains confidential information to meet its objectives related to confidentiality.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Required element 1 — any one of
confidentialclassificationdata classificationsensitiveclassif…
Supporting terms — specificity signals
labeltierhandlingpublicinternalrestrictedinventory
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| GDPR | Art.9 | Special category data | data-classification |
| GDPR | Art.10 | Criminal convictions and offences data | data-classification |
| CCPA/CPRA | 1798.121 | Right to limit use of sensitive personal information | data-classification |
| ISO 27001 | A.5.12 | Classification of information | data-classification |
| ISO 27001 | A.8.3 | Information access restriction | data-classification |
| PCI DSS 4.0.1 | 3.4 | PAN is masked when displayed and protected from copying | data-classification |
| COPPA | 312.2-312.3 | Determine whether COPPA applies | data-classification |
| NIST CSF 2.0 | ID.AM-05 | Assets are prioritised by criticality | data-classification |