Cross-Framework Mapping

AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)vsPCI DSS v4.0

See exactly how AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls map to PCI DSS v4.0. Pre-computed mappings, identified gaps, and coverage analysis.

37
Controls Mapped
0
Gaps Found
56%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) maps to PCI DSS v4.0 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 37 mapped controls across 5 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Security Management and Governance(6 mappings)

AWWA-1.1Security Policy and Governance3 targets
PCI-10.1Processes for logging and monitoring access are defined and understood
PCI-5.1Processes for protecting against malicious software are defined and understood
PCI-6.1Processes for developing secure systems and software are defined and understood
AWWA-1.3Security Awareness and Training3 targets
PCI-12.6Security awareness education is an ongoing activity
PCI-3.3Sensitive authentication data is not stored after authorization
PCI-5.4Anti-phishing mechanisms protect users against phishing attacks

Access Control and Identity Management(10 mappings)

AWWA-2.1User Access Management3 targets
PCI-3.3Sensitive authentication data is not stored after authorization
PCI-7.3Access to system components and data is managed via an access control system
PCI-9.2Physical access controls manage entry into facilities with cardholder data
AWWA-2.2Authentication Mechanisms3 targets
PCI-3.3Sensitive authentication data is not stored after authorization
PCI-8.1Processes for identification and authentication are defined and understood
PCI-8.4Multi-factor authentication is implemented for access into the CDE
AWWA-2.4Physical Access Controls4 targets
PCI-7.3Access to system components and data is managed via an access control system
PCI-9.1Processes for restricting physical access to cardholder data are defined
PCI-9.2Physical access controls manage entry into facilities with cardholder data
PCI-9.4Media with cardholder data is securely stored, accessed, distributed, and destroyed

Network and Communications Security(4 mappings)

AWWA-3.1Network Segmentation3 targets
PCI-1.2Network security controls are configured and maintained
PCI-1.3Network access to and from the cardholder data environment is restricted
PCI-1.5Risks to the CDE from computing devices connecting to untrusted networks are mitigated
AWWA-3.2Remote Access Security
PCI-3.6Cryptographic keys used to protect stored account data are secured

+17 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 PCI DSS v4.0 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 PCI DSS v4.0?

AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) has 25 controls across its framework, while PCI DSS v4.0 covers 63 controls. Direct mapping analysis identifies 14 overlapping controls (56% coverage). The frameworks diverge most significantly in Incident Response and Recovery, where 6 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls have no direct PCI DSS v4.0 equivalent.

How many controls map between AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) and PCI DSS v4.0?

Of 25 total AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls, 14 map directly to PCI DSS v4.0 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 PCI DSS v4.0?

11 AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) controls have no direct equivalent in PCI DSS v4.0. The highest concentration of gaps is in Incident Response and Recovery with 6 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 PCI DSS v4.0?

The domain with the highest gap count is Incident Response and Recovery (6 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.