75% of NIST SP 800-63-4 you already have
CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 already covers about 75% of NIST SP 800-63-4, leaving
2 of 8 controls as genuinely new work.
Already covered 5
Likely covered 1
New work 2
What is genuinely new work
Nothing in CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 reaches these. This is the list to scope.
NISTSP63R4-2Identity Proofing: Evidence Collection, Remote Proofing, and Identity Validation Services
NISTSP63R4-6Equity, Accessibility, and Inclusive Identity Service Design
Show the 6 you already have
NISTSP63R4-1Digital Identity Risk Management and IAL/AAL/FAL Assurance Level Selection
NISTSP63R4-3Authentication: Authenticator Types, MFA, Phishing-Resistance, and Syncable Authenticators
NISTSP63R4-5Federation: Assertions, Trust Agreements, RP Validation, Pseudonymous Identifiers
NISTSP63R4-7Privacy, Records Retention, and User-Controlled Wallets
NISTSP63R4-8Operational Audit, Session Management, Recovery, and Cross-cutting Controls
NISTSP63R4-4Authenticator Lifecycle: Binding, Recovery, Replacement, Suspension, Revocation
How this is calculated
Already covered means a mapping runs from a control in CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 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