← ISO 27001 · A.5 — Organisational
A.5.7 — Threat intelligence
low
monitoringvulnerability-management
Requirement
Information relating to information security threats shall be collected and analysed to produce threat intelligence.
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
threat intelligencethreat feedadvisorycve feedthreat landscape
Supporting terms — specificity signals
cisavendor bulletinsubscribeisacanalysed
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| SOC 2 | CC4.1 | Ongoing and separate evaluations | monitoring |
| SOC 2 | CC7.1 | Detection of configuration changes and vulnerabilities | vulnerability-management |
| PCI DSS 4.0.1 | 6.3.3 | Security patches installed within defined timeframes | vulnerability-management |
| PCI DSS 4.0.1 | 10.4 | Audit logs are reviewed, using automated mechanisms | monitoring |
| PCI DSS 4.0.1 | 10.7 | Failures of critical security controls are detected and addressed | monitoring |
| PCI DSS 4.0.1 | 11.3 | Internal and external vulnerability scanning every three months | vulnerability-management |
| PCI DSS 4.0.1 | 11.5 | Intrusion detection and change detection | monitoring |
| PCI DSS 4.0.1 | 11.6.1 | Payment page change and tamper detection | monitoring |