← ISO 27001 · A.8 — Technological
A.8.8 — Management of technical vulnerabilities
Requirement
Information about technical vulnerabilities of information systems in use shall be obtained, the organisation's exposure to such vulnerabilities evaluated, and appropriate measures taken.
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 |
|---|---|---|---|
| PCI DSS 4.0.1 | 6.3.3 | Security patches installed within defined timeframes | patching vulnerability-management |
| NIST CSF 2.0 | PR.PS-02 | Software is maintained, replaced and removed commensurate with risk | patching vulnerability-management |
| SOC 2 | CC7.1 | Detection of configuration changes and vulnerabilities | 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 |
| GLBA | 314.4(d) | Continuous monitoring, or annual penetration tests and six-monthly vulnerability assessments | vulnerability-management |