Framework overlap

Does NIST SP 1800-32 cover Florida Digital Bill of Rights (FDBR)?

You hold NIST SP 1800-32 and have been told to do Florida Digital Bill of Rights (FDBR). Here is how much overlaps, control by control.

33% of Florida Digital Bill of Rights (FDBR) you already have

NIST SP 1800-32 already covers about 33% of Florida Digital Bill of Rights (FDBR), leaving 8 of 12 controls as genuinely new work.

Already covered 1 Likely covered 3 New work 8

What is genuinely new work

Nothing in NIST SP 1800-32 reaches these. This is the list to scope.

FDBR-Compliance-Crosswalk-NIST-ISO-SOC
FDBR Crosswalk to NIST CSF, ISO 27001, SOC 2 and Federal/Sectoral Frameworks
FDBR-ConsumerRights
Consumer Rights (Fla. Stat. 501.705, 501.706, 501.707)
FDBR-Coord-CCPA-CPRA-State-Privacy
Coordination with US State Privacy Laws (CCPA/CPRA, VCDPA, CPA, CTDPA, UCPA, ICDPA, TIPA, RIDTPPA, WDPA, MMCL, OCPA, NHDPA, MDPA, TDPSA, KCDPA, NJDPA, DPDPA, INCDPA)
FDBR-Coord-COPPA-FERPA-HIPAA-Sectoral
Coordination with COPPA, FERPA, HIPAA, GLBA, FCRA and Sectoral Federal Laws
FDBR-PIPL-Comparison
Comparison with GDPR + Comprehensive Privacy Laws + APRA Federal Preemption Tracking
FDBR-Section112.23-Government-Moderation
Government-Directed Content Moderation Prohibition (Fla. Stat. 112.23)
FDBR-Status-Implementation-Org
FDBR Compliance Program Implementation - Organizational Roles and Operational Controls
FDBR-Status-Pipeline-Litigation
FDBR Implementation Status, 2024-2025 Amendments, Litigation and Pipeline
Show the 4 you already have
FDBR-Enforcement-AG-CurePeriod
Enforcement by Florida Department of Legal Affairs + Penalties + 45-Day Cure (Fla. Stat. 501.72, 501.721, 501.722)
FDBR-ControllerObligations-DPA-Notice
Controller + Processor Obligations + Data Protection Assessments (Fla. Stat. 501.707, 501.708, 501.71, 501.711)
FDBR-Scope-Defs
Scope, Applicability Thresholds and Definitions (Fla. Stat. 501.701, 501.702, 501.703, 501.704)
FDBR-SensitiveData-Children-VoiceFacial
Sensitive Data, Children's Privacy and Voice/Facial Recognition (Fla. Stat. 501.711, 501.1735)

How this is calculated

Already covered means a mapping runs from a control in NIST SP 1800-32 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