Crossfoot / Crosswalks / HIPAA Security Rule to ISO 27001:2022
Draft v0.1.024 of 24 objectives have a direct match
HIPAA Security Rule to ISO 27001:2022 crosswalk
24 control objectives in HIPAA Security Rule and Breach Notification Rule are mapped here to ISO/IEC 27001 (Annex A controls and management clauses). Every one has a requirement on the other side. Each row is one shared objective, with the requirement ids on both sides.
| Control objective | HIPAA Security Rule | ISO 27001:2022 |
|---|---|---|
| Security governance and policies | 164.308(a)(1)(i)Security management process164.316(a)Policies and procedures | A.5.1Policies for information securityA.5.36Compliance with policies, rules and standards for information security |
| Security roles and accountability | 164.308(a)(2)Assigned security responsibility | A.5.2Information security roles and responsibilitiesA.5.3Segregation of duties |
| Risk assessment and treatment | 164.308(a)(1)(ii)(A)Risk analysis164.308(a)(1)(ii)(B)Risk management | Clause 6.1.2Information security risk assessmentClause 6.1.3Information security risk treatment |
| Asset and system inventory | 164.310(d)(2)(iii)Accountability (record of hardware and media movements) | A.5.9Inventory of information and other associated assets |
| Data classification and handling | 164.308(a)(1)(ii)(A)Risk analysis (requires identifying where ePHI lives) | A.5.12Classification of informationA.5.13Labelling of information |
| Access provisioning, review and removal | 164.308(a)(3)Workforce security (authorization, supervision, termination)164.308(a)(4)Information access management | A.5.15Access controlA.5.16Identity managementA.5.18Access rights |
| Least privilege and privileged access | 164.312(a)(1)Access control164.308(a)(4)Information access management | A.8.2Privileged access rightsA.8.3Information access restriction |
| Authentication, unique IDs and multi-factor authentication | 164.312(d)Person or entity authentication164.312(a)(2)(i)Unique user identification | A.5.17Authentication informationA.8.5Secure authentication |
| Encryption at rest and key management | 164.312(a)(2)(iv)Encryption and decryption (addressable) | A.8.24Use of cryptography |
| Encryption in transit | 164.312(e)(1)Transmission security | A.5.14Information transferA.8.24Use of cryptography |
| Vulnerability scanning and patching | 164.308(a)(8)Evaluation (periodic technical evaluation) | A.8.8Management of technical vulnerabilities |
| Penetration testing and independent assessment | 164.308(a)(8)Evaluation | A.8.29Security testing in development and acceptanceA.5.35Independent review of information security |
| Logging, log review and monitoring | 164.312(b)Audit controls164.308(a)(1)(ii)(D)Information system activity review | A.8.15LoggingA.8.16Monitoring activitiesA.8.17Clock synchronization |
| Intrusion detection and integrity monitoring | 164.312(c)(1)Integrity | A.8.16Monitoring activities |
| Malware protection | 164.308(a)(5)(ii)(B)Protection from malicious software | A.8.7Protection against malware |
| Incident response and breach notification | 164.308(a)(6)Security incident procedures164.404Notification to individuals (Breach Notification Rule) | A.5.24Information security incident management planning and preparationA.5.25Assessment and decision on information security eventsA.5.26Response to information security incidentsA.5.27Learning from information security incidents |
| Third-party and vendor risk management | 164.308(b)(1)Business associate contracts and other arrangements164.314(a)Business associate contracts or other arrangements | A.5.19Information security in supplier relationshipsA.5.20Addressing information security within supplier agreementsA.5.21Managing information security in the ICT supply chainA.5.22Monitoring, review and change management of supplier servicesA.5.23Information security for use of cloud services |
| Business continuity and disaster recovery | 164.308(a)(7)Contingency plan | A.5.29Information security during disruptionA.5.30ICT readiness for business continuity |
| Backup and redundancy | 164.308(a)(7)(ii)(A)Data backup plan164.308(a)(7)(ii)(B)Disaster recovery plan | A.8.13Information backupA.8.14Redundancy of information processing facilities |
| Security awareness and training | 164.308(a)(5)Security awareness and training | A.6.3Information security awareness, education and training |
| Personnel screening, terms and sanctions | 164.308(a)(3)(ii)(B)Workforce clearance procedure164.308(a)(3)(ii)(C)Termination procedures164.308(a)(1)(ii)(C)Sanction policy | A.6.1ScreeningA.6.2Terms and conditions of employmentA.6.4Disciplinary processA.6.5Responsibilities after termination or change of employment |
| Physical access and facility security | 164.310(a)Facility access controls | A.7.1Physical security perimetersA.7.2Physical entryA.7.4Physical security monitoring |
| Data retention, media handling and secure disposal | 164.310(d)(2)(i)Disposal164.310(d)(2)(ii)Media re-use | A.7.10Storage mediaA.7.14Secure disposal or re-use of equipmentA.8.10Information deletion |
| Ongoing control monitoring and internal audit | 164.308(a)(8)Evaluation | Clause 9.2Internal auditClause 9.3Management review |
Open a control objective for the evidence checklist.ISO 27001:2022 to HIPAA Security Rule →
Scope: Citations are to 45 CFR 164. 'Addressable' vs 'required' implementation specifications are not distinguished here. Several themes have no direct HIPAA citation. Annex A controls are prefixed 'A.'; management-system clauses are prefixed 'Clause'. A mapping means the requirements address the same objective. It does not mean satisfying one satisfies the other, because scope, frequency and evidence rules differ.