Cross-Framework Mapping

ISO 27799vsMaryland Online Data Privacy Act of 2024

See exactly how ISO 27799 controls map to Maryland Online Data Privacy Act of 2024. Pre-computed mappings, identified gaps, and coverage analysis.

12
Controls Mapped
34
Gaps Found
20%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

ISO 27799 maps to Maryland Online Data Privacy Act of 2024 with 20% coverage across 9 directly mapped controls. Analysis of 46 ISO 27799 controls identifies 37 compliance gaps — primarily concentrated in Operations.

Source: TheArtOfService Knowledge Graph | 46 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 12 of 12 mapped controls across 4 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

ISO 27799: Patient Data Protection(8 mappings)

ISO27799-01ePHI access controls and authorization
MD-MODPA-Sensitive-Data-Health-Biometric-Section-14-4607-Reasonably-Necessary-Proportionate-Data-MinimizationMaryland MODPA Data Minimization + Sensitive + Health + Biometric + Section 14-4607 + Reasonably Necessary + Proportionate
ISO27799-02ePHI encryption at rest and in transit
MD-MODPA-Sensitive-Data-Health-Biometric-Section-14-4607-Reasonably-Necessary-Proportionate-Data-MinimizationMaryland MODPA Data Minimization + Sensitive + Health + Biometric + Section 14-4607 + Reasonably Necessary + Proportionate
ISO27799-03Minimum necessary standard enforcement2 targets
MD-MODPA-Controller-Duties-Security-DPA-Section-14-4608-14-4609-Processor-Contract-AssessmentMaryland MODPA Controller Duties + Section 14-4608 + Section 14-4609 + Processor Contract + DPA
MD-MODPA-Pseudonymisation-De-Identification-Section-14-4610-4611-Internal-Research-AggregatedMaryland MODPA Pseudonymisation + De-Identification + Section 14-4610 + 14-4611 + Internal Research + Aggregated
ISO27799-04Patient data de-identification procedures2 targets
MD-MODPA-Controller-Duties-Security-DPA-Section-14-4608-14-4609-Processor-Contract-AssessmentMaryland MODPA Controller Duties + Section 14-4608 + Section 14-4609 + Processor Contract + DPA
MD-MODPA-Pseudonymisation-De-Identification-Section-14-4610-4611-Internal-Research-AggregatedMaryland MODPA Pseudonymisation + De-Identification + Section 14-4610 + 14-4611 + Internal Research + Aggregated
ISO27799-05Audit trail for ePHI access2 targets
MD-MODPA-Controller-Duties-Security-DPA-Section-14-4608-14-4609-Processor-Contract-AssessmentMaryland MODPA Controller Duties + Section 14-4608 + Section 14-4609 + Processor Contract + DPA
MD-MODPA-Pseudonymisation-De-Identification-Section-14-4610-4611-Internal-Research-AggregatedMaryland MODPA Pseudonymisation + De-Identification + Section 14-4610 + 14-4611 + Internal Research + Aggregated

ISO 27799: Administrative Safeguards(2 mappings)

ISO27799-06Security management process and risk analysis
MD-MODPA-Pseudonymisation-De-Identification-Section-14-4610-4611-Internal-Research-AggregatedMaryland MODPA Pseudonymisation + De-Identification + Section 14-4610 + 14-4611 + Internal Research + Aggregated
ISO27799-08Information access management
MD-MODPA-Sensitive-Data-Health-Biometric-Section-14-4607-Reasonably-Necessary-Proportionate-Data-MinimizationMaryland MODPA Data Minimization + Sensitive + Health + Biometric + Section 14-4607 + Reasonably Necessary + Proportionate

ISO 27799: Technical Safeguards(1 mappings)

ISO27799-16Transmission security and encryption
MD-MODPA-Sensitive-Data-Health-Biometric-Section-14-4607-Reasonably-Necessary-Proportionate-Data-MinimizationMaryland MODPA Data Minimization + Sensitive + Health + Biometric + Section 14-4607 + Reasonably Necessary + Proportionate

ISO 27799: Physical Safeguards(1 mappings)

ISO27799-17Facility access controls
MD-MODPA-Sensitive-Data-Health-Biometric-Section-14-4607-Reasonably-Necessary-Proportionate-Data-MinimizationMaryland MODPA Data Minimization + Sensitive + Health + Biometric + Section 14-4607 + Reasonably Necessary + Proportionate

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 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 ISO 27799 and Maryland Online Data Privacy Act of 2024?

ISO 27799 has 46 controls across its framework, while Maryland Online Data Privacy Act of 2024 covers 8 controls. Direct mapping analysis identifies 9 overlapping controls (20% coverage). The frameworks diverge most significantly in Operations, where 4 ISO 27799 controls have no direct Maryland Online Data Privacy Act of 2024 equivalent.

How many controls map between ISO 27799 and Maryland Online Data Privacy Act of 2024?

Of 46 total ISO 27799 controls, 9 map directly to Maryland Online Data Privacy Act of 2024 controls — representing 20% coverage. The remaining 37 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping ISO 27799 to Maryland Online Data Privacy Act of 2024?

37 ISO 27799 controls have no direct equivalent in Maryland Online Data Privacy Act of 2024. The highest concentration of gaps is in Operations with 4 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 ISO 27799 and Maryland Online Data Privacy Act of 2024?

The domain with the highest gap count is Operations (4 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.