NIST SP 800-66
Security Management Process - Risk Analysis and Risk Management

NIST SP 800-66 1: Security Management Process: Risk Analysis and Risk Management for ePHI

Implement the HIPAA Security Rule Security Management Process Administrative Safeguard at 45 CFR 164.308(a)(1) per NIST SP 800-66 Rev 2. Conduct an accurate and thorough Risk Analysis per 45 CFR 164.308(a)(1)(ii)(A) of the potential risks and vulnerabilities to the confidentiality + integrity + availability of electronic protected health information (ePHI) held by the covered entity or business associate using NIST SP 800-30 Rev 1 risk assessment methodology. Implement Risk Management per 45 CFR 164.308(a)(1)(ii)(B) sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level to comply with 45 CFR 164.306(a). Apply Sanction Policy per 45 CFR 164.308(a)(1)(ii)(C) for workforce members who fail to comply with security policies and procedures. Conduct Information System Activity Review per 45 CFR 164.308(a)(1)(ii)(D) to regularly review records of information system activity (audit logs + access reports + security incident tracking reports). Risk analysis must address all ePHI created + received + maintained + transmitted across the enterprise + cover ePHI at rest + in transit + in use across all environments + applications + endpoints + cloud + third parties.

What else in your programme already covers this

This control maps to 102 controls across 58 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

BSI IT-Grundschutz · 3 controls

  • BSI-13 Risk assessment procedures
  • BSI-15 Security categorization
  • BSI-17 Continuous monitoring strategy

ISO 27005 · 3 controls

ISO 31000 · 3 controls

ISO/IEC 23894:2023 · 3 controls

ISO/IEC 29134:2023 · 3 controls

API 1164 · 2 controls

IEC 62443 · 2 controls

ISO 27019 · 2 controls

ISO/IEC 27003:2017 · 2 controls

ISO/IEC 27014:2020 · 2 controls

  • NIST-CSF-GV.RM-07 Strategic opportunities (i.e., positive risks) are characterized and are included in organizational cybersecurity risk discussions
  • NIST-CSF-ID.RA-09 The authenticity and integrity of hardware and software are assessed prior to acquisition and use

NIST SP 1800-32 · 2 controls

  • NZISM-1 NZISM Governance, Documentation, and Classification System
  • NZISM-3 Personnel Security, Physical Security, and Cryptography
  • ASTWO-1 Audit Planning, Scaling, Risk Assessment, and Integration
  • ASTWO-3 Entity-Level Controls and Period-End Financial Reporting Process
  • 2.4.4 Hazard Analysis and Risk Assessment
  • 2.7.2 Food Fraud Plan

South Korea ISMS-P · 2 controls

  • CH-FADP-21 Data protection impact assessments
  • FADP-7 Data Protection Impact Assessment (Articles 9-10)
  • CRM-1 AML/CFT Compliance
  • CRM-4 Business Risk Assessment
  • CPS230-11 Identification, Assessment and Management of Operational Risk
  • 4.3.1 Risk Assessment and Impact Analysis

Bahrain PDPL · 1 control

  • BB-DPA-20 Sections 50-60 - Registration and Responsibilities

GDPR · 1 control

ISO 13485 · 1 control

  • ISO13485-06 Security management process and risk analysis

ISO 22000 · 1 control

ISO 27017 · 1 control

ISO 27018 · 1 control

ISO 27799 · 1 control

  • ISO27799-06 Security management process and risk analysis

ISO 45001 · 1 control

ISO/IEC 27031:2011 · 1 control

ISO/IEC 29147:2018 · 1 control

  • 29147-5.11 Researcher Safe Harbour and Legal Posture
  • 3.11 Encrypt Sensitive Data at Rest

NIST SP 800-190 · 1 control

  • NJDPA-7 Data Protection Assessments and Processor Contracts
  • NGOB-1 Open Banking Registry Participation, Tiered Categorisation, and KYP
  • AUPRV-6 Sensitive Information, PIA, Privacy by Design, Children

South Korea PIPA · 1 control

Turkey KVKK · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Query this from an agent

The graph holds this control, the 102 it maps to, and the evidence behind each claim, over MCP and REST.