← GLBA · Safeguards Rule (16 CFR 314)
314.4(d) — Continuous monitoring, or annual penetration tests and six-monthly vulnerability assessments
Requirement
The effectiveness of safeguards is regularly tested or monitored. For information systems this means continuous monitoring, or annual penetration testing plus vulnerability assessments (including systemic scans) at least every six months, whenever there are material changes, and whenever circumstances may have a material impact.
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.8.29 | Security testing in development and acceptance | security-testing pen-test |
| PCI DSS 4.0.1 | 11.4 | Penetration testing at least every 12 months | pen-test security-testing |
| CCPA/CPRA | Regs (cybersecurity audits) | Annual independent cybersecurity audit | security-testing |
| SOC 2 | CC7.1 | Detection of configuration changes and vulnerabilities | vulnerability-management |
| ISO 27001 | A.5.7 | Threat intelligence | vulnerability-management |
| ISO 27001 | A.8.8 | Management of technical vulnerabilities | vulnerability-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 |