← SOC 2 · CC7 — System Operations
CC7.1 — Detection of configuration changes and vulnerabilities
Requirement
The entity uses detection and monitoring procedures to identify changes to configurations that introduce new vulnerabilities, and susceptibilities to newly discovered vulnerabilities.
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.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.5.7 | Threat intelligence | vulnerability-management |
| ISO 27001 | A.8.8 | Management of technical vulnerabilities | vulnerability-management |
| ISO 27001 | A.8.9 | Configuration management | config-management |
| PCI DSS 4.0.1 | 1.2 | Network security control configuration and review | config-management |
| PCI DSS 4.0.1 | 2.2 | Secure configuration of system components | config-management |
| PCI DSS 4.0.1 | 6.3.3 | Security patches installed within defined timeframes | vulnerability-management |
| PCI DSS 4.0.1 | 11.3 | Internal and external vulnerability scanning every three months | vulnerability-management |
| NIST CSF 2.0 | ID.RA-01 | Vulnerabilities are identified, validated and recorded | vulnerability-management |