Cross-Framework Mapping

DORAvsFrench Sapin II Law (Law No. 2016-1691)

See exactly how DORA controls map to French Sapin II Law (Law No. 2016-1691). Pre-computed mappings, identified gaps, and coverage analysis.

13
Controls Mapped
76
Gaps Found
13%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

DORA maps to French Sapin II Law (Law No. 2016-1691) with 13% coverage across 12 directly mapped controls. Analysis of 89 DORA controls identifies 77 compliance gaps — primarily concentrated in ICT Risk Management.

Source: TheArtOfService Knowledge Graph | 89 controls analysed | 769 frameworks | 815K+ cross-framework mappings

Control Mappings

Showing 13 of 13 mapped controls across 6 domains. Sign up to explore all 815K+ mappings across 769 frameworks.

ICT Risk Management(5 mappings)

Art.10Cases When Authorization Is Not Required
SAPIN2-1Code of Conduct
Art.12Prohibition of Illegal Interception
LAOS-CC-Art22LaoCERT
Art.2Scope
SAPIN2-1Code of Conduct
Art.51Exercise of the power to impose administrative penalties and remedial measures
SAPIN2-7Disciplinary Sanctions
Art.8Rights of Data Subjects
SAPIN2-1Code of Conduct

Incident Reporting(1 mappings)

Art.21Functions of the SIC Specific to Personal Data
SAPIN2-7Disciplinary Sanctions

Resilience Testing(2 mappings)

Art.25Preservation of Stored Data2 targets
SAPIN2-2Corruption Risk Assessment
SAPIN2-3Third-Party Due Diligence

DORA: Information Security Governance(1 mappings)

DORA-05Roles and responsibilities definition
SAPIN2-1Code of Conduct

DORA: Cybersecurity Controls(1 mappings)

DORA-06Network security and segmentation
LAOS-CC-Art21Network Security

DORA: Incident Management & Reporting(3 mappings)

DORA-22Incident response and containment
LAOS-CC-Art22LaoCERT
DORA-24Customer notification procedures
LAOS-CC-Art22LaoCERT
DORA-25Post-incident review and improvement
LAOS-CC-Art22LaoCERT

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 769 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 769 framework browser
  • Cross-framework mappings (815K+)
  • 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 DORA and French Sapin II Law (Law No. 2016-1691)?

DORA has 89 controls across its framework, while French Sapin II Law (Law No. 2016-1691) covers 33 controls. Direct mapping analysis identifies 12 overlapping controls (13% coverage). The frameworks diverge most significantly in ICT Risk Management, where 30 DORA controls have no direct French Sapin II Law (Law No. 2016-1691) equivalent.

How many controls map between DORA and French Sapin II Law (Law No. 2016-1691)?

Of 89 total DORA controls, 12 map directly to French Sapin II Law (Law No. 2016-1691) controls — representing 13% coverage. The remaining 77 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping DORA to French Sapin II Law (Law No. 2016-1691)?

77 DORA controls have no direct equivalent in French Sapin II Law (Law No. 2016-1691). The highest concentration of gaps is in ICT Risk Management with 30 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 DORA and French Sapin II Law (Law No. 2016-1691)?

The domain with the highest gap count is ICT Risk Management (30 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.