TheArtOfService
Cross-Framework Mapping

MDS2 (Medical Device)vsNIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)

See exactly how MDS2 (Medical Device) controls map to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205). Pre-computed mappings, identified gaps, and coverage analysis.

4
Controls Mapped
4
Gaps Found
12%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

MDS2 (Medical Device) maps to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) with 12% coverage across 1 directly mapped controls. Analysis of 8 MDS2 (Medical Device) controls identifies 7 compliance gaps — primarily concentrated in Roadmap Third Party Security Guidance and Vulnerability Disclosure - MDS2.

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

Control Mappings

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

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

MDS2-PHI-Data-Handling-DATA-Storage-STCF-Transmission-TXCF-TXIG-Encryption-FIPSMDS2 PHI Handling + DATA + STCF Storage + TXCF Transmission + TXIG Integrity + Encryption + FIPS4 targets
→PQC-2FIPS 203 ML-KEM Implementation - Module-Lattice Key-Encapsulation Mechanism
→PQC-5Cryptographic Inventory and PQC Migration Roadmap
→PQC-7FIPS Validated Modules, HSM Readiness, and Algorithm Validation
→PQC-8Implementation Requirements - RNG, Side-Channel, Key Management, Operations, Incident Response

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 NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) comparisons

NIST SP 800-171A Rev 3 - Assessing CUI Security Requirements vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappingsOWASP ASVS vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappingsNIST Special Publication 800-34 Revision 1, Contingency Planning Guide for Federal Information Systems vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappingsCISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappingsAzure Security Benchmark vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappingsFFIEC IT Examination Handbook vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappingsAWWA Cybersecurity Guidance for the Water Sector (American Water Works Association) vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappingsIEC 62351 - Power Systems Communication Security vs NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)5 mappings

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 →

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 NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

MDS2 (Medical Device) has 8 controls across its framework, while NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) covers 8 controls. Direct mapping analysis identifies 1 overlapping controls (12% 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 NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) equivalent.

How many controls map between MDS2 (Medical Device) and NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

Of 8 total MDS2 (Medical Device) controls, 1 map directly to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) controls — representing 12% coverage. The remaining 7 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 NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

7 MDS2 (Medical Device) controls have no direct equivalent in NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205). 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 NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

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.