HIPAA Security Rule
Administrative

HIPAA Security Rule 164.308(a)(2): Assigned Security Responsibility (Standard)

Identify the security official responsible for development and implementation of policies and procedures. NIST recommends a documented appointment, position description, and reporting line to executive leadership.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

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

PCI DSS 4.0 · 6 controls

  • 12.1.4 12.1.4 Executive ownership of information security formally assigned
  • 2.1.2 2.1.2 Requirement 2 roles and responsibilities assigned
  • 4.1.2 4.1.2 Requirement 4 roles and responsibilities assigned
  • 9.1.2 9.1.2 Requirement 9 roles and responsibilities assigned
  • 3.1.2 3.1.2 Assigned duties for Requirement 3 activities
  • 8.1.2 8.1.2 Requirement 8 roles and responsibilities assigned

C5 (Germany) · 3 controls

ISO 27701:2019 · 3 controls

  • 5.3.3 Organizational roles, responsibilities and authorities
  • 6.3 Organization of information security
  • 6.9.1 Operational procedures and responsibilities
  • CPS220-09 Designation of a Chief Risk Officer
  • CPS220-10 Designated Risk Management Function

APRA CPS 234 · 2 controls

  • CPS234-13 Board Responsibility for Information Security
  • CPS234-14 Definition of Information Security Roles and Responsibilities
  • CFTC-SS-2 Enterprise Risk Management and Governance Category
  • CFTC-SS-36 Internal Reporting and Review by Senior Management and the Board

FedRAMP High · 2 controls

  • PL-1 Policy and Procedures
  • PS-9 Position Descriptions (PS-9)

FedRAMP Moderate · 2 controls

  • PL-1 Policy and Procedures
  • PS-9 Position Descriptions (PS-9)

ISO/IEC 42001:2023 · 2 controls

  • 5.3 Roles, responsibilities and authorities
  • A.3.2 AI roles and responsibilities
  • NIST-CSF-GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving
  • NIST-CSF-GV.RR-02 Roles, responsibilities, and authorities related to cybersecurity risk management are established, communicated, understood, and enforced

NIST SP 800-181 · 2 controls

  • ANSSI-HYG-39 Designate an Information System Security Officer and Make the Role Known
  • CPS230-14 Board Setting of Senior Manager Roles and Responsibilities
  • SEC10-BP01 Identify key personnel and external resources
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data
  • GS-1 Align organization roles, responsibilities and accountabilities

CIS Controls v8 · 1 control

  • CIS-17.1 Designate Personnel to Manage Incident Handling

ISO 22301:2019 · 1 control

  • 5.3 Roles, responsibilities and authorities

ISO 27001:2022 · 1 control

  • 5.2 Information security roles and responsibilities

ISO 27002:2022 · 1 control

  • 5.2 Information security roles and responsibilities
  • 161R1-PM-2 Information Security Program Leadership Role
  • NIST800-PM-2 PM-2 Information Security Program Leadership Role

SOC 2 · 1 control

  • SOC2-CC1.3 CC1.3 Structures, reporting lines, authorities and responsibilities (COSO principle 3)

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.

Other controls in Administrative

You are reading one control. How much of HIPAA Security Rule have you already done?

HIPAA Security Rule 164.308(a)(2) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of HIPAA Security Rule your existing evidence covers. Hold ISO 27001:2022 and 53 of 67 HIPAA Security Rule controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 64 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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