TheArtOfService
Cross-Framework Mapping

MDS2 (Medical Device)vsITU-T X.805 - Security Architecture for End-to-End Communications

See exactly how MDS2 (Medical Device) controls map to ITU-T X.805 - Security Architecture for End-to-End Communications. Pre-computed mappings, identified gaps, and coverage analysis.

4
Controls Mapped
4
Gaps Found
38%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

MDS2 (Medical Device) maps to ITU-T X.805 - Security Architecture for End-to-End Communications with 38% coverage across 3 directly mapped controls. Analysis of 8 MDS2 (Medical Device) controls identifies 5 compliance gaps — primarily concentrated in Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2.

Source: TheArtOfService Knowledge Graph | 8 controls analysed | 706 frameworks | 324K+ cross-framework mappings

Control Mappings

Showing 4 of 4 mapped controls across 3 domains. Sign up to explore all 324K+ mappings across 706 frameworks.

PHI Data Handling Storage and Transmission - MDS2(1 mappings)

MDS2-PHI-Data-Handling-DATA-Storage-STCF-Transmission-TXCF-TXIG-Encryption-FIPSMDS2 PHI Handling + DATA + STCF Storage + TXCF Transmission + TXIG Integrity + Encryption + FIPS
→X805-Dim1-Access-Control-RBAC-Authorization-Resources-Network-Elements-Services-ApplicationsITU-T X.805 Security Dimension 1 - Access Control + Role-Based Access Control (RBAC) + Authorization + Resources + Network Elements + Services + Applications + Access Limitations + Authorized Personnel + Discretionary + Mandatory Access Control

Authentication and Authorization - MDS2(2 mappings)

MDS2-Person-Node-Authentication-Authorization-Auto-Logoff-AUTH-PAUT-NAUTMDS2 Authentication + Authorization + Auto Logoff + PAUT + NAUT + AUTH + Identity Management2 targets
→X805-Dim1-Access-Control-RBAC-Authorization-Resources-Network-Elements-Services-ApplicationsITU-T X.805 Security Dimension 1 - Access Control + Role-Based Access Control (RBAC) + Authorization + Resources + Network Elements + Services + Applications + Access Limitations + Authorized Personnel + Discretionary + Mandatory Access Control
→X805-Dim2-Authentication-Identity-Verification-Claimed-Identities-Entities-CommunicationITU-T X.805 Security Dimension 2 - Authentication + Identity Verification + Claimed Identity + Entity Authentication + Data Origin Authentication + Mutual Authentication + Multi-Factor + Cryptographic Authentication

Physical Security Workstation Disposal and Backup - MDS2(1 mappings)

MDS2-Physical-Security-PLOK-Workstation-Disposal-Backup-DTBK-Disaster-RecoveryMDS2 Physical Security + PLOK + Workstation + Disposal + Backup + DTBK + Disaster Recovery
→X805-Dim1-Access-Control-RBAC-Authorization-Resources-Network-Elements-Services-ApplicationsITU-T X.805 Security Dimension 1 - Access Control + Role-Based Access Control (RBAC) + Authorization + Resources + Network Elements + Services + Applications + Access Limitations + Authorized Personnel + Discretionary + Mandatory Access Control

Related Comparisons

Other MDS2 (Medical Device) comparisons

MDS2 (Medical Device) vs OWASP DevSecOps Maturity Model (DSOMM)5 mappingsMDS2 (Medical Device) vs NIST SP 800-171A - Assessing Security Requirements for Controlled Unclassified Information (CUI)5 mappingsMDS2 (Medical Device) vs ISO 28001:2007 Supply Chain Security Management5 mappingsMDS2 (Medical Device) vs NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements5 mappingsMDS2 (Medical Device) vs ISO/IEC 27011:20245 mappingsMDS2 (Medical Device) vs CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.05 mappingsMDS2 (Medical Device) vs FTC GLBA Safeguards Rule (16 CFR Part 314)5 mappingsMDS2 (Medical Device) vs AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)5 mappings

Other ITU-T X.805 - Security Architecture for End-to-End Communications comparisons

NIST Privacy Framework vs ITU-T X.805 - Security Architecture for End-to-End Communications4 mappingsISO 27001:2022 vs ITU-T X.805 - Security Architecture for End-to-End Communications4 mappingsOman National Cybersecurity Framework vs ITU-T X.805 - Security Architecture for End-to-End Communications3 mappingsNAIC Insurance Data Security Model Law (MDL-668) vs ITU-T X.805 - Security Architecture for End-to-End Communications3 mappingsMARS-E vs ITU-T X.805 - Security Architecture for End-to-End Communications3 mappingsSSAE 18 - Attestation Standards (SOC Reporting) vs ITU-T X.805 - Security Architecture for End-to-End Communications3 mappingsSOC 2 vs ITU-T X.805 - Security Architecture for End-to-End Communications3 mappingsMARS-E - Minimum Acceptable Risk Standards for Exchanges vs ITU-T X.805 - Security Architecture for End-to-End Communications3 mappings

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • ✓ 706 framework browser
  • ✓ Cross-framework mappings (324K+)
  • ✓ 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 →

Popular framework comparisons

NIST CSF vs NIST 800-53ISO 27001 vs NIST CSFCMMC vs NIST 800-53FedRAMP vs NIST 800-53NIST CSF vs SOC 2HIPAA vs NIST 800-53ISO 27001 vs SOC 2ISO 27001 vs ISO 27701

What are the key differences between MDS2 (Medical Device) and ITU-T X.805 - Security Architecture for End-to-End Communications?

MDS2 (Medical Device) has 8 controls across its framework, while ITU-T X.805 - Security Architecture for End-to-End Communications covers 13 controls. Direct mapping analysis identifies 3 overlapping controls (38% coverage). The frameworks diverge most significantly in Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2, where 1 MDS2 (Medical Device) controls have no direct ITU-T X.805 - Security Architecture for End-to-End Communications equivalent.

How many controls map between MDS2 (Medical Device) and ITU-T X.805 - Security Architecture for End-to-End Communications?

Of 8 total MDS2 (Medical Device) controls, 3 map directly to ITU-T X.805 - Security Architecture for End-to-End Communications controls — representing 38% coverage. The remaining 5 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping MDS2 (Medical Device) to ITU-T X.805 - Security Architecture for End-to-End Communications?

5 MDS2 (Medical Device) controls have no direct equivalent in ITU-T X.805 - Security Architecture for End-to-End Communications. The highest concentration of gaps is in Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2 with 1 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 MDS2 (Medical Device) and ITU-T X.805 - Security Architecture for End-to-End Communications?

The domain with the highest gap count is Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2 (1 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.