HIPAA Security Rule
Policies and Procedures

HIPAA Security Rule 164.316(a): Policies and Procedures (Standard)

Implement reasonable and appropriate policies and procedures to comply with the Security Rule standards. NIST recommends a managed policy hierarchy with ownership, version control, and review cadence.

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

What else in your programme already covers this

This control maps to 79 controls across 27 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 · 11 controls

  • 11.4.1 11.4.1 Penetration testing methodology defined and implemented
  • 12.1.1 12.1.1 Overall information security policy established and disseminated
  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed
  • 12.10.1 12.10.1 Incident response plan ready for activation
  • 2.1.1 2.1.1 Requirement 2 policies and procedures governed
  • 2.1.2 2.1.2 Requirement 2 roles and responsibilities assigned
  • 3.3.3 3.3.3 Issuer SAD storage limited, justified and encrypted
  • 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.1 3.1.1 Requirement 3 policies and procedures maintained and in use
  • 8.1.2 8.1.2 Requirement 8 roles and responsibilities assigned

ISO 22301:2019 · 10 controls

  • 4.2.1 General
  • 4.3.1 General
  • 5.2.1 Establishing the business continuity policy
  • 6.1.1 Determining risks and opportunities
  • 7.5.2 Creating and updating
  • 7.5.3 Control of documented information
  • 8.1 Operational planning and control
  • 8.2.1 General
  • 8.4.4 Business continuity plans
  • 9.3.2 Management review input

ISO 27701:2019 · 7 controls

  • 6.11.1 Security requirements of information systems
  • 6.2.1 Management direction for information security
  • 6.3 Organization of information security
  • 6.9.1 Operational procedures and responsibilities
  • 7.4 Privacy by design and privacy by default
  • 8.2 Conditions for collection and processing
  • 8.4 Privacy by design and privacy by default

ISO 27001:2022 · 5 controls

  • 5.1 Policies for information security
  • 5.2 Information security roles and responsibilities
  • 5.34 Privacy and protection of personal identifiable information (PII)
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures

NIST SP 800-53 Rev 5 · 5 controls

ISO 27002:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.37 Documented operating procedures
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles

C5 (Germany) · 3 controls

  • C5-OIS-02 Information Security Policy
  • C5-SP-01 Documentation, communication and provision of policies and instructions
  • C5-SP-02 Review and Approval of Policies and Instructions

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 3 controls

NIST Cybersecurity Framework 2.0 · 3 controls

  • NIST-CSF-GV.OC-03 Legal, regulatory, and contractual requirements regarding cybersecurity - including privacy and civil liberties obligations - are understood and managed
  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

SOC 2 · 3 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-PI1.1 PI1.1 Quality information about processing objectives, data definitions and specifications

APEC Cross-Border Privacy Rules (CBPR) System · 2 controls

APRA CPS 234 · 2 controls

  • CPS234-19 Information Security Policy Framework
  • CPS234-P19 Policy Direction to All Responsible Parties

Azure Security Benchmark · 2 controls

  • ASBv3-GS-3 Define and implement data protection strategy
  • ASBv3-GS-5 Define and implement security posture management strategy

CIS Controls v8 · 2 controls

  • CIS-15.2 Establish and Maintain a Service Provider Management Policy
  • CIS-16.4 Establish and Manage an Inventory of Third-Party Software Components

FedRAMP High · 2 controls

  • PL-1 Policy and Procedures
  • PL-2 System Security and Privacy Plans

FedRAMP Moderate · 2 controls

  • PL-1 Policy and Procedures
  • PL-2 System Security and Privacy Plans

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

APRA CPS 220 Risk Management · 1 control

  • CPS220-P36 Monitoring of Policy Review Dates and Ownership

APRA CPS 230 Operational Risk Management · 1 control

AWS Well-Architected Security Pillar · 1 control

  • SEC01-BP03 Identify and validate control objectives

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data

Australia My Health Records Act 2012 · 1 control

Australian Privacy Principles (APPs) · 1 control

  • APP-1 APP 1 - Open and transparent management of personal information

Authorised Economic Operator (AEO) Programmes - Global Standards · 1 control

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-1 Program of Risk Analysis and Oversight

CMMC 2.0 · 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.

Other controls in Policies and Procedures

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

HIPAA Security Rule 164.316(a) 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.

If you hold ISO 27001:202279.1% covered · 14 gapsIf you hold ISO 27002:202279.1% covered · 14 gapsIf you hold FedRAMP Moderate77.6% covered · 15 gapsIf you hold NIST SP 800-53 Rev 577.6% covered · 15 gapsIf you hold C5 (Germany)76.1% covered · 16 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.167.2% covered · 22 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll HIPAA Security Rule controls