80% of OWASP Top 10:2025 you already have
AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) already covers about 80% of OWASP Top 10:2025, leaving
2 of 10 controls as genuinely new work.
Already covered 1
Likely covered 7
New work 2
What is genuinely new work
Nothing in AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) reaches these. This is the list to scope.
OWASPTOP10-10A10:2025 Server-Side Request Forgery (SSRF)
OWASPTOP10-5A05:2025 Security Misconfiguration
Show the 8 you already have
OWASPTOP10-1A01:2025 Broken Access Control
OWASPTOP10-2A02:2025 Cryptographic Failures and Secret Management
OWASPTOP10-3A03:2025 Injection Including Cross-Site Scripting
OWASPTOP10-4A04:2025 Insecure Design and Business Logic (incl. A11 API Abuse)
OWASPTOP10-6A06:2025 Vulnerable and Outdated Components
OWASPTOP10-7A07:2025 Identification and Authentication Failures
OWASPTOP10-8A08:2025 Software and Data Integrity Failures
OWASPTOP10-9A09:2025 Security Logging and Monitoring Failures
How this is calculated
Already covered means a mapping runs from a control in AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) to that control. Likely
covered means no direct mapping exists but both frameworks map to the same control in a third
standard. New work means neither. We keep those separate rather than adding them into one
friendlier number, because blending them would present a two-hop inference as a verified
fact.
Coverage is not symmetric.
Run it the other way and you will get a
different number; both are correct.
From 332,959 cross-framework control
mappings across 723 frameworks, 531 of them verified against
their source documents. It does not tell you that you are compliant: a mapped control means
the two standards ask for the same thing, not that you have done it.
Try another pair ยท
Today's edition