Framework overlap

Does AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) cover NRF Cybersecurity and Data Privacy Framework (National Retail Federation)?

You hold AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) and have been told to do NRF Cybersecurity and Data Privacy Framework (National Retail Federation). Here is how much overlaps, control by control.

50% of NRF Cybersecurity and Data Privacy Framework (National Retail Federation) you already have

AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) already covers about 50% of NRF Cybersecurity and Data Privacy Framework (National Retail Federation), leaving 4 of 8 controls as genuinely new work.

Already covered 2 Likely covered 2 New work 4

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.

NRFCS-3
Payment Card Data Protection and PCI DSS Scope Management
NRFCS-5
E-Commerce, Mobile, Store Technology, and IoT Security
NRFCS-6
Identity and Access Management, Workforce Security, Training and Awareness
NRFCS-8
Third-Party Risk, Supply Chain, Vendor Management, Resilience, Peak-Season Readiness, Metrics, Continuous Improvement
Show the 4 you already have
NRFCS-1
Retail Cybersecurity Governance, Policy, and Regulatory Change Management
NRFCS-2
Risk Assessment, Customer Data Inventory, Classification, and Retail Threat Model
NRFCS-4
Consumer Privacy Rights, Consent, Marketing, and Loyalty Data
NRFCS-7
Detection, Logging, Incident Response, Breach Notification, and Fraud Detection

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