HIPAA Security Rule
Policies and Procedures

HIPAA Security Rule 164.316(b)(2)(iii): Updates (Documentation)

Review documentation periodically, and update as needed, in response to environmental or operational changes affecting the security of ePHI.

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

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 5 controls

CIS Controls v8 · 4 controls

  • CIS-12.4 Establish and Maintain Architecture Diagram(s)
  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-17.8 Conduct Post-Incident Reviews
  • CIS-4.1 Establish and Maintain a Secure Configuration Process

ISO 22301:2019 · 3 controls

  • 10.1 Nonconformity and corrective action
  • 7.5.2 Creating and updating
  • 7.5.3 Control of documented information

SOC 2 · 3 controls

  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

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

ISO 27001:2022 · 2 controls

  • 5.1 Policies for information security
  • 5.37 Documented operating procedures

ISO 27002:2022 · 2 controls

  • 5.1 Policies for information security
  • 5.37 Documented operating procedures

ISO/IEC 42001:2023 · 2 controls

  • 7.5.2 Creating and updating documented information
  • 7.5.3 Control of documented information

NIST SP 800-171 Rev 3 · 2 controls

PCI DSS 4.0 · 2 controls

  • 12.1.2 12.1.2 Security policy reviewed annually and updated as needed
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change
  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions
  • CPS220-P36 Monitoring of Policy Review Dates and Ownership
  • CPS230-P45 Annual Update of the Business Continuity Plan

APRA CPS 234 · 1 control

  • CPS234-P17 Active Maintenance of Capability Against Change
  • AUCDR-IS-STEP1 Step 1 - Define and implement security governance for CDR data

C5 (Germany) · 1 control

  • C5-SP-02 Review and Approval of Policies and Instructions
  • CFTC-SS-24 Periodic Update of the Recovery Plan and Emergency Procedures

CMMC 2.0 · 1 control

ISO 27701:2019 · 1 control

  • 5.5.5 Documented information
  • 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

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(b)(2)(iii) 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 43 it maps to, and the evidence behind each claim, over MCP and REST.