TheArtOfService
Cross-Framework Mapping

HITECH ActvsNIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)

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

1
Controls Mapped
10
Gaps Found
9%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

HITECH Act maps to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) with 9% coverage across 1 directly mapped controls. Analysis of 11 HITECH Act controls identifies 10 compliance gaps — primarily concentrated in HITECH 2024-2025 Pipeline: NPRM Security Rule Modernisation, Reproductive Health, Information Blocking, Sectoral Application.

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

Control Mappings

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

HITECH Coordination with HIPAA Privacy + Security Rules (Verified Separately) + 21st Century Cures Act + ONC(1 mappings)

HITECH-Coord-HIPAA-Privacy-Security-Cures-ONCHITECH Coordination with HIPAA Privacy Rule + HIPAA Security Rule (Verified Separately) + 21st Century Cures Act + ONC
→PQC-2FIPS 203 ML-KEM Implementation - Module-Lattice Key-Encapsulation Mechanism

Related Comparisons

Other HITECH Act comparisons

HITECH Act vs Azure Security Benchmark5 mappingsHITECH Act vs Privacy Act 1988 (Australia)4 mappingsHITECH Act vs Ley Orgánica de Protección de Datos Personales (LOPDP)4 mappingsHITECH Act vs Law No. 172-13 on the Protection of Personal Data4 mappingsHITECH Act vs India DPDP Act4 mappingsHITECH Act vs APPI4 mappingsHITECH Act vs Bahrain PDPL4 mappingsHITECH Act vs DAMA-DMBOK2 - Data Management Body of Knowledge (2nd Edition)4 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 (330K+)
  • ✓ 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 HITECH Act and NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

HITECH Act has 11 controls across its framework, while NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) covers 8 controls. Direct mapping analysis identifies 1 overlapping controls (9% coverage). The frameworks diverge most significantly in HITECH 2024-2025 Pipeline: NPRM Security Rule Modernisation, Reproductive Health, Information Blocking, Sectoral Application, where 4 HITECH Act controls have no direct NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) equivalent.

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

Of 11 total HITECH Act controls, 1 map directly to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205) controls — representing 9% coverage. The remaining 10 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping HITECH Act to NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

10 HITECH Act controls have no direct equivalent in NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205). The highest concentration of gaps is in HITECH 2024-2025 Pipeline: NPRM Security Rule Modernisation, Reproductive Health, Information Blocking, Sectoral Application 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 HITECH Act and NIST Post-Quantum Cryptography Standards (FIPS 203, 204, 205)?

The domain with the highest gap count is HITECH 2024-2025 Pipeline: NPRM Security Rule Modernisation, Reproductive Health, Information Blocking, Sectoral Application (4 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.