Cross-Framework Mapping

FTC Health Breach Notification RulevsISO/IEC 29147:2018

See exactly how FTC Health Breach Notification Rule controls map to ISO/IEC 29147:2018. Pre-computed mappings, identified gaps, and coverage analysis.

19
Controls Mapped
31
Gaps Found
18%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

FTC Health Breach Notification Rule maps to ISO/IEC 29147:2018 with 18% coverage across 9 directly mapped controls. Analysis of 50 FTC Health Breach Notification Rule controls identifies 41 compliance gaps — primarily concentrated in Compliance and Enforcement.

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

Control Mappings

Showing 19 of 19 mapped controls across 2 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

Scope and Definitions(6 mappings)

64.2003Definitions3 targets
29147-3Terms and definitions
29147-9.2Contact mechanisms and scope
30111-3Terms and definitions
Art. 2Consent Definition3 targets
29147-3Terms and definitions
29147-9.2Contact mechanisms and scope
30111-3Terms and definitions

Compliance and Enforcement(13 mappings)

EAR-COMP-01Export Compliance Programme
29147-5.11Vulnerabilities and risk
EU-NIS2-EN-CE-02Supply Chain and SBOM
29147-5.11Vulnerabilities and risk
HBNR-ENF-01Record-Keeping Requirements
29147-5.11Vulnerabilities and risk
NDB-DATA-BREACH-PLANData breach response plan
30111-3Terms and definitions
US-ITAR-EAR-CE-02Violation Reporting5 targets
29147-5.6Vulnerability handling process summary
29147-5.8Confidentiality
29147-7.8Remediation information
30111-1Scope
30111-3Terms and definitions
US-ITAR-EAR-CE-03Penalties
29147-5.8Confidentiality
US-SEC-DA-CE-02Custody and Reporting3 targets
29147-3Terms and definitions
29147-9.2Contact mechanisms and scope
30111-3Terms and definitions

Related 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 FTC Health Breach Notification Rule and ISO/IEC 29147:2018?

FTC Health Breach Notification Rule has 50 controls across its framework, while ISO/IEC 29147:2018 covers 32 controls. Direct mapping analysis identifies 9 overlapping controls (18% coverage). The frameworks diverge most significantly in Compliance and Enforcement, where 31 FTC Health Breach Notification Rule controls have no direct ISO/IEC 29147:2018 equivalent.

How many controls map between FTC Health Breach Notification Rule and ISO/IEC 29147:2018?

Of 50 total FTC Health Breach Notification Rule controls, 9 map directly to ISO/IEC 29147:2018 controls — representing 18% coverage. The remaining 41 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping FTC Health Breach Notification Rule to ISO/IEC 29147:2018?

41 FTC Health Breach Notification Rule controls have no direct equivalent in ISO/IEC 29147:2018. The highest concentration of gaps is in Compliance and Enforcement with 31 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 FTC Health Breach Notification Rule and ISO/IEC 29147:2018?

The domain with the highest gap count is Compliance and Enforcement (31 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.