Cross-Framework Mapping

AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)vsIACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems

See exactly how AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls map to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems. Pre-computed mappings, identified gaps, and coverage analysis.

23
Controls Mapped
2
Gaps Found
56%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) maps to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems with 56% coverage across 14 directly mapped controls. Analysis of 25 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls identifies 11 compliance gaps — primarily concentrated in Incident Response and Recovery.

Source: TheArtOfService Knowledge Graph | 25 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 20 of 23 mapped controls across 5 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Security Management and Governance(1 mappings)

AWWA-1.2Risk Assessment
E26-R3Risk assessment

Access Control and Identity Management(4 mappings)

AWWA-2.1User Access Management
E26-R5Access control
AWWA-2.2Authentication Mechanisms
E27-R3User authentication
AWWA-2.4Physical Access Controls2 targets
E26-R5Access control
E26-R7Physical security of systems

Network and Communications Security(3 mappings)

AWWA-3.1Network Segmentation
E26-R4Network segmentation
AWWA-3.2Remote Access Security
E26-R6Secure remote access
AWWA-3.4Encryption and Data Protection
E26-R6Secure remote access

System Security and Operations(3 mappings)

AWWA-4.3Configuration Management
E27-R1System hardening
AWWA-4.4Audit Logging and Monitoring2 targets
E26-R11Logging and audit trail
E27-R5Security event logging

Incident Response and Recovery(9 mappings)

AWWA-5.1Incident Response Plan2 targets
E26-R13Incident response plan
E27-R5Security event logging
AWWA-5.3Business Continuity and Disaster Recovery2 targets
E26-R15Recovery planning
E26-R16Backup and restoration
AWWA-5.4Backup and Restoration2 targets
E26-R15Recovery planning
E26-R16Backup and restoration
AWWA-5.5Exercises and Testing3 targets
E26-R13Incident response plan
E26-R15Recovery planning
E26-R16Backup and restoration

+3 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 693 frameworks.

Create Free Account →

Free forever — no credit card required

Related Comparisons

Other AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) comparisons

Other IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems comparisons

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 693 framework browser
  • Cross-framework mappings (819K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) has 25 controls across its framework, while IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems covers 22 controls. Direct mapping analysis identifies 14 overlapping controls (56% coverage). The frameworks diverge most significantly in Incident Response and Recovery, where 4 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls have no direct IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems equivalent.

How many controls map between AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

Of 25 total AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls, 14 map directly to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems controls — representing 56% coverage. The remaining 11 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) to IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

11 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls have no direct equivalent in IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems. The highest concentration of gaps is in Incident Response and Recovery with 4 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) and IACS Unified Requirements E26/E27 — Cyber Resilience of Ships and On-Board Systems?

The domain with the highest gap count is Incident Response and Recovery (4 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.