43% of AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) you already have
EASA Part-IS already covers about 43% of AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association), leaving
21 of 37 controls as genuinely new work.
Already covered 1
Likely covered 15
New work 21
What is genuinely new work
Nothing in EASA Part-IS reaches these. This is the list to scope.
AWWA-1.4Compliance and Regulatory Alignment
AWWA-3.3Wireless Security
AWWA-G430-1Cybersecurity Program Governance
AWWA-G430-11Manual Operations Capability
AWWA-G430-13Supply Chain and Vendor Risk
AWWA-G430-14Personnel Security and Insider Threat
AWWA-G430-15Cybersecurity Training for Operators
AWWA-G430-16Logging and Audit
AWWA-G430-17Physical Security of Cyber Assets
AWWA-G430-18Configuration and Change Management for OT
AWWA-G430-19AWIA Risk and Resilience Assessment Compliance
AWWA-G430-2Asset Inventory and Classification
AWWA-G430-20Information Sharing and Reporting
AWWA-G430-21Cybersecurity Program Review
AWWA-G430-3Risk Assessment for Water Systems
AWWA-G430-4Network Segmentation IT/OT
AWWA-G430-5Access Control for SCADA and Control Systems
AWWA-G430-6Remote Access Management
AWWA-G430-7Patch and Vulnerability Management
AWWA-G430-8Malware Protection
AWWA-G430-9Boundary Protection and Monitoring
Show the 16 you already have
AWWA-1.1Security Policy and Governance
AWWA-1.3Security Awareness and Training
AWWA-2.1User Access Management
AWWA-2.2Authentication Mechanisms
AWWA-2.3Account Management
AWWA-2.4Physical Access Controls
AWWA-3.1Network Segmentation
AWWA-3.2Remote Access Security
AWWA-3.4Encryption and Data Protection
AWWA-4.1Malware Protection
AWWA-4.3Configuration Management
AWWA-4.4Audit Logging and Monitoring
AWWA-G430-10Incident Response for Water Utilities
AWWA-G430-12Backup and Recovery for Control Systems
How this is calculated
Already covered means a mapping runs from a control in EASA Part-IS 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