# HIPAA Compliance Checklist for IT and Security Teams (2026): Access, Audit, and AI Agents

> Source: <https://www.c1.ai/guides/hipaa-compliance-checklist>
> Published: 2026-11-19 12:00:00+00:00

# HIPAA Compliance Checklist for IT and Security Teams (2026): Access, Audit, and AI Agents

**Summary:** A HIPAA compliance checklist is a list of the administrative, physical, and technical safeguards the HIPAA Security Rule (45 CFR Part 164, Subpart C) requires to protect electronic protected health information (ePHI), each tied to the section it comes from. For IT and security teams, most items come down to identity: who can reach ePHI, why, and what evidence proves it.

HIPAA does not publish an official checklist. It publishes standards and implementation specifications, and leaves the "how" to you. That flexibility is why audits go sideways: the rule says "implement procedures for terminating access," and the auditor asks for the ticket, the timestamp, and proof the account is gone.

This checklist turns the Security Rule into tasks IT and security teams own, with the citation for each one. It focuses on access control, audit logging, authentication, access reviews, offboarding, and business associate access, and it covers AI agents and service accounts alongside people, because 45 CFR 164.312(a)(1) applies access control to "persons or software programs."

### HIPAA IT compliance checklist at a glance[#](#hipaa-it-compliance-checklist-at-a-glance)

| Area | HIPAA section | What IT and security check | Evidence to keep | 
|---|---|---|---|
| Risk analysis | 164.308(a)(1)(ii)(A) | Every system that creates, receives, stores, or sends ePHI is assessed | Current risk analysis, asset list | 
| Access authorization | 164.308(a)(4) | Access is granted by role and approved | Access policy, approval records | 
| Minimum necessary | 164.502(b), 164.514(d) | Roles get only the PHI their job needs | Role-to-access matrix | 
| Unique user IDs | 164.312(a)(2)(i) | No shared accounts on ePHI systems | Account inventory with owners | 
| Emergency access | 164.312(a)(2)(ii) | Break-glass access exists and is logged | Procedure, usage log, after-action review | 
| Audit controls | 164.312(b) | ePHI system activity is recorded | Log sources and retention settings | 
| Activity review | 164.308(a)(1)(ii)(D) | Someone regularly reviews logs and access reports | Review records with dates and reviewers | 
| Authentication | 164.312(d) | Identity is verified before access | MFA coverage report | 
| Termination | 164.308(a)(3)(ii)(C) | Access ends when employment or the arrangement ends | Offboarding tickets with timestamps | 
| Access review | 164.308(a)(4)(ii)(C), 164.308(a)(8) | Access rights are reviewed and modified | Review campaigns, decisions, revocation proof | 
| Business associates | 164.308(b), 164.314(a) | BAAs exist and vendor access is controlled | Signed BAAs, vendor access list | 
| Documentation | 164.316(b)(2)(i) | Policies and records are retained six years | Document repository with dates | 

**Running HIPAA access controls in spreadsheets?** [Book a demo](https://www.c1.ai/lp/request-demo) or [see how C1.ai automates compliance evidence](https://www.c1.ai/solutions/compliance-risk-management).

## How to use this HIPAA compliance checklist[#](#how-to-use-this-hipaa-compliance-checklist)

Use this HIPAA compliance checklist as a working list, not a one-time audit. Each item names the HIPAA section it comes from, so your compliance team can map it to your risk analysis and policies, and an auditor can trace it back to the rule.

For the identity governance model behind these controls, see [Identity for HIPAA Compliance](https://www.c1.ai/guides/identity-for-hipaa-compliance). Three things to know before you start:

1. **"Addressable" does not mean optional.** HHS is explicit: the addressable designation lets you decide whether a specification is reasonable and appropriate for your environment, but you must either implement it, implement an equivalent alternative, or document why neither fits ([HHS](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html) ). Termination procedures, access authorization, and log-in monitoring are all addressable. Treat them as required unless you have written reasoning otherwise.
2. **The current Security Rule is the one being enforced.** HHS proposed the first major Security Rule update since 2013 in January 2025 ([Federal Register](https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information) ). OMB's regulatory agenda now projects final action for July 2027 ([McDermott Will & Schulte](https://www.mcdermottlaw.com/insights/final-action-on-hipaa-security-rule-modifications-now-projected-for-july-2027/) ). This checklist follows the rule in effect today and flags where the proposal would tighten it.
3. **Risk analysis comes first.** OCR's Risk Analysis Initiative has produced at least 14 enforcement actions, including a March 2026 settlement over a breach affecting about 15 million people ([HHS](https://www.hhs.gov/press-room/ocr-mmg-fusion-hipaa-agreement.html) ;[Nixon Peabody](https://www.nixonpeabody.com/insights/articles/2026/07/21/health-plan-settlement-marks-ocrs-20th-ransomware-and-14th-risk-analysis-initiative) ). Every access control on this list should trace to a risk you identified.

Physical safeguards (164.310) such as facility access and device disposal usually sit with facilities and endpoint teams. This checklist covers them only where identity is involved.

## Administrative safeguards[#](#administrative-safeguards)

Administrative safeguards (45 CFR 164.308) are the policies and processes that decide who gets access to ePHI and how you know the controls work. They are where most HIPAA access findings start, because a technical control without a documented process behind it is hard to defend.

**Security management process, 164.308(a)(1)**

- Complete an accurate and thorough risk analysis covering every system that holds or touches ePHI, including SaaS apps and AI tools. 164.308(a)(1)(ii)(A) (Required)
- Implement a risk management plan that reduces identified risks to a reasonable and appropriate level. 164.308(a)(1)(ii)(B) (Required)
- Maintain a written sanction policy for workforce members who violate security policies. 164.308(a)(1)(ii)(C) (Required)
- Regularly review information system activity: audit logs, access reports, and security incident tracking reports. 164.308(a)(1)(ii)(D) (Required)

**Assigned security responsibility, 164.308(a)(2)**

- Name one security official responsible for the security program, in writing.

**Workforce security, 164.308(a)(3)**

- Authorize or supervise every workforce member who works with ePHI. 164.308(a)(3)(ii)(A)
- Define clearance procedures that confirm a person's access is appropriate before it is granted. 164.308(a)(3)(ii)(B)
- Document termination procedures for voluntary and involuntary departures. 164.308(a)(3)(ii)(C) (see offboarding below)

**Information access management, 164.308(a)(4), and minimum necessary, 164.502(b) and 164.514(d)**

- Write access authorization policies for granting access to ePHI systems. 164.308(a)(4)(ii)(B)
- Establish, document, review, and modify each user's access based on those policies. 164.308(a)(4)(ii)(C)
- Identify which roles or classes of workforce need PHI, which categories they need, and under what conditions. 164.514(d)(2)
-   Map each role to specific entitlements so [least privilege](https://www.c1.ai/glossary/least-privilege) is enforced by default, not by request.

**Security awareness and training, 164.308(a)(5)**

- Train every workforce member, and send periodic security reminders. 164.308(a)(5)(ii)(A)
- Monitor log-in attempts and report discrepancies. 164.308(a)(5)(ii)(C)
- Set procedures for creating, changing, and safeguarding passwords. 164.308(a)(5)(ii)(D)

**Incident response, contingency, and evaluation**

- Identify, respond to, mitigate, and document security incidents. 164.308(a)(6)(ii) (Required)
- Notify affected individuals of a breach of unsecured PHI without unreasonable delay and no later than 60 calendar days after discovery. 164.404(b)
- Maintain data backup, disaster recovery, and emergency mode operation plans. 164.308(a)(7)(ii)(A) to (C) (Required)
- Run periodic technical and nontechnical evaluations, and re-run them when systems or operations change. 164.308(a)(8)

**Documentation, 164.316**

- Keep policies, procedures, and required records for six years from creation or last effective date, whichever is later. 164.316(b)(2)(i)
- Review and update documentation when the environment changes. 164.316(b)(2)(iii)

## Technical safeguards: access control, audit controls, authentication[#](#technical-safeguards-access-control-audit-controls-authentication)

Technical safeguards (45 CFR 164.312) are the controls inside your systems. For identity teams, three standards carry most of the weight: access control, audit controls, and person or entity authentication.

**Access control, 164.312(a)**

- Allow ePHI access only to people and software programs granted access rights under 164.308(a)(4). 164.312(a)(1)
- Assign a unique user ID to every user. No shared clinical workstation logins tied to ePHI. 164.312(a)(2)(i) (Required)
-   Document and test an emergency [break-glass access](https://www.c1.ai/glossary/what-is-break-glass-access) procedure, log every use, and review each use after the fact. 164.312(a)(2)(ii) (Required)
- Configure automatic logoff after a set period of inactivity. 164.312(a)(2)(iii)
- Encrypt ePHI at rest, or document the equivalent alternative. 164.312(a)(2)(iv)
- Separate privileged admin accounts from day-to-day user accounts on ePHI systems. Supports 164.308(a)(4) and least privilege.
-   Enforce [separation of duties](https://www.c1.ai/glossary/what-is-separation-of-duties) on sensitive combinations, such as creating and approving billing adjustments.

**Audit controls, 164.312(b)**

- Record activity in every system that contains or uses ePHI: EHR, data warehouse, billing, file shares, and cloud storage. 164.312(b) (Required)
- Log identity events too: account creation, permission grants, role changes, and deprovisioning.
- Assign an owner and a cadence for reviewing those logs. 164.308(a)(1)(ii)(D)
- Retain logs long enough to support investigations and your documentation policy.

**Integrity and transmission security, 164.312(c) and (e)**

- Protect ePHI from improper alteration or destruction. 164.312(c)(1)
- Encrypt ePHI in transit where appropriate. 164.312(e)(2)(ii)

**Person or entity authentication, 164.312(d)**

- Verify that each person or entity seeking ePHI access is who or what it claims to be. 164.312(d) (Required)
-   Require multi-factor authentication for remote access, privileged access, and every ePHI system that supports it. The 2025 proposed rule would make MFA required, with limited exceptions ([HHS](https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html) ).

### AI agents and non-human identities with ePHI access[#](#ai-agents-and-non-human-identities-with-ephi-access)

HIPAA's access control standard already covers software. 164.312(a)(1) limits ePHI access to "persons or software programs" with granted access rights, and 164.312(d) requires authenticating any "person or entity." Service accounts, integration bots, and AI agents that read clinical notes or summarize claims all fall under the same rule as clinicians.

- Inventory every non-human identity with ePHI access: service accounts, API keys, integration users, and AI agents.
- Give each one a named human owner and a documented purpose.
- Scope access to the task. An agent that drafts prior authorization letters does not need the full patient chart.
- Use credentials that expire instead of long-lived shared secrets.
- Log agent actions in ePHI systems under the agent's own identity, not a shared admin account.
- Include agents and service accounts in access reviews, reviewed by their owners.
- Deprovision an agent when its owner leaves or its project ends.

C1.ai governs AI agents in the same identity governance model as people, with dedicated Agents and MCP Gateway modules ([pricing](https://www.c1.ai/pricing)). Whatever platform you use, ask it to show one agent with an owner going through a review and being deprovisioned.

## Access reviews and offboarding[#](#access-reviews-and-offboarding)

Access reviews and offboarding are where a HIPAA compliance checklist meets the calendar. Healthcare workforces change constantly: travel nurses, rotating residents, per diem staff, students, and contractors. Every one of those changes is a chance for access to outlive its purpose.

### User access reviews[#](#user-access-reviews)

The Security Rule does not use the phrase "access review," but it requires you to review and modify access rights (164.308(a)(4)(ii)(C)), regularly review access reports (164.308(a)(1)(ii)(D)), and periodically evaluate your controls (164.308(a)(8)). A documented [user access review](https://www.c1.ai/glossary/user-access-reviews) program is the most direct way to show all three.

- Prioritize ePHI systems: EHR, PACS, lab, pharmacy, billing, data warehouse, and file shares.
- Set a written cadence by risk, for example quarterly for privileged and EHR access and annually for the rest. Auditors test against your policy, so write it down.
- Route each review to someone who can judge it: the department manager for staff access, the application owner for admin roles, the owner for each service account or agent.
- Show reviewers context such as role, department, last login, and how access was granted, so they are not approving blind.
- Flag access that conflicts with role or separation of duties rules.
- Remove revoked access in the target system, and record proof that it happened.
- Keep campaign records, decisions, reviewer identity, timestamps, and remediation for six years. 164.316(b)(2)(i)

Rubber-stamping is the failure mode. A 4,000-line spreadsheet sent to a charge nurse during a shift does not produce a real decision. Shrink the list by removing access automatically when HR data says a role ended, so reviewers see only judgment calls. For a full program, see [User Access Review Best Practices](https://www.c1.ai/guides/user-access-reviews-best-practices-guide).

### Offboarding and role changes[#](#offboarding-and-role-changes)

- Trigger deprovisioning from the HR system of record, not from a manager's email. 164.308(a)(3)(ii)(C)
-   Handle voluntary and involuntary terminations separately. OCR's audit protocol asks about both ([HHS](https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/audit/protocol-edited/index.html) ).
- Remove access across every ePHI system, including apps outside single sign-on and local accounts.
- Revoke tokens, API keys, and agent credentials the person owned, and reassign ownership of agents and service accounts.
- On a transfer, remove the old role's access before or when the new role's access is granted. Movers accumulate access faster than leavers.
- Record the timestamp of each removal so you can show how long access lasted after the end date.

Plan for tighter timelines. The proposed rule would require ending a departing workforce member's access within one hour and notifying other regulated entities within 24 hours when that person's access to their ePHI changes or ends ([Davis Wright Tremaine](https://www.dwt.com/blogs/privacy--security-law-blog/2025/01/hipaa-security-rule-proposed-changes-in-2025); [HHS](https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html)). One hour is not achievable with ticket-based offboarding. Event-driven [identity lifecycle management](https://www.c1.ai/guides/identity-lifecycle-management) is.

## Vendor and business associate access[#](#vendor-and-business-associate-access)

Business associates, such as billing companies, clearinghouses, IT managed service providers, and cloud vendors, are directly liable under the Security Rule. Covered entities still own the decision to give them access.

- Sign a business associate agreement (BAA) before any business associate creates, receives, maintains, or transmits ePHI on your behalf. 164.308(b)(1), 164.502(e)
- Confirm each BAA includes the required terms: safeguards, reporting of security incidents and breaches, and subcontractor flow-down. 164.314(a)(2)(i)
- Require business associates to get the same assurances from their subcontractors. 164.308(b)(2)
- Keep an inventory of every vendor account in your environment, with a named internal sponsor and an end date.
- Give vendor accounts unique IDs and MFA. No shared vendor logins. 164.312(a)(2)(i), 164.312(d)
- Grant vendor access just in time for support work, then remove it.
- Include vendor and contractor accounts in every access review.
- Remove access the day a contract ends, and confirm it in writing.

The proposed rule would also require business associates to verify their technical safeguards to covered entities at least once every 12 months, backed by a written analysis and certification ([HHS](https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html)). Building a vendor access inventory now makes that verification easy to request and check.

## Downloadable HIPAA IT compliance checklist[#](#downloadable-hipaa-it-compliance-checklist)

Copy this HIPAA IT compliance checklist into your ticketing system, GRC tool, or audit workbook. Each line names its HIPAA section.

```
HIPAA IT COMPLIANCE CHECKLIST (45 CFR Part 164)

RISK AND GOVERNANCE
[ ] Risk analysis covers every ePHI system, including SaaS and AI tools ... 164.308(a)(1)(ii)(A)
[ ] Risk management plan addresses identified risks .......................... 164.308(a)(1)(ii)(B)
[ ] Sanction policy documented ................................................ 164.308(a)(1)(ii)(C)
[ ] Security official named in writing ........................................ 164.308(a)(2)
[ ] Periodic technical and nontechnical evaluation completed .................. 164.308(a)(8)

ACCESS AUTHORIZATION
[ ] Access authorization policy written ........................................ 164.308(a)(4)(ii)(B)
[ ] Role-to-PHI matrix defined (minimum necessary) ............................ 164.514(d)(2)
[ ] Access established, documented, reviewed, and modified by policy ......... 164.308(a)(4)(ii)(C)
[ ] Clearance procedure before access is granted .............................. 164.308(a)(3)(ii)(B)

ACCESS CONTROL AND AUTHENTICATION
[ ] Unique user ID for every user, no shared logins ........................... 164.312(a)(2)(i)
[ ] Break-glass procedure documented, logged, and reviewed .................... 164.312(a)(2)(ii)
[ ] Automatic logoff configured ................................................ 164.312(a)(2)(iii)
[ ] ePHI encrypted at rest and in transit, or alternative documented .......... 164.312(a)(2)(iv), 164.312(e)(2)(ii)
[ ] MFA on remote, privileged, and ePHI system access ......................... 164.312(d)
[ ] Log-in attempts monitored ................................................. 164.308(a)(5)(ii)(C)
[ ] Password procedures documented ............................................ 164.308(a)(5)(ii)(D)

AUDIT AND MONITORING
[ ] Activity logged in every ePHI system ...................................... 164.312(b)
[ ] Identity events logged (grants, changes, removals) ........................ 164.312(b)
[ ] Logs and access reports reviewed on a set cadence ......................... 164.308(a)(1)(ii)(D)

ACCESS REVIEWS AND OFFBOARDING
[ ] Access review cadence written into policy ................................. 164.308(a)(4)(ii)(C)
[ ] Reviews completed for all ePHI systems, with decisions recorded ........... 164.308(a)(4)(ii)(C)
[ ] Revoked access removed and removal verified ............................... 164.308(a)(4)(ii)(C)
[ ] Deprovisioning triggered by HR system of record ........................... 164.308(a)(3)(ii)(C)
[ ] Voluntary and involuntary termination procedures documented .............. 164.308(a)(3)(ii)(C)
[ ] Mover access removed when role changes .................................... 164.308(a)(4)(ii)(C)

AI AGENTS AND NON-HUMAN IDENTITIES
[ ] Inventory of service accounts, API keys, and AI agents with ePHI access ... 164.312(a)(1)
[ ] Named owner and purpose for each ......................................... 164.308(a)(4)
[ ] Agents authenticated under their own identity ............................. 164.312(d)
[ ] Agents included in access reviews and deprovisioned at end of use ........ 164.308(a)(4)(ii)(C)

BUSINESS ASSOCIATES
[ ] BAA signed before any ePHI access ........................................ 164.308(b)(1)
[ ] BAA includes required terms .............................................. 164.314(a)(2)(i)
[ ] Subcontractor assurances obtained ......................................... 164.308(b)(2)
[ ] Vendor accounts inventoried, sponsored, time-bound, and reviewed .......... 164.308(a)(4)

INCIDENTS AND DOCUMENTATION
[ ] Incident response procedure documented and tested ......................... 164.308(a)(6)(ii)
[ ] Breach notification within 60 days of discovery ........................... 164.404(b)
[ ] Backup, disaster recovery, and emergency mode plans in place .............. 164.308(a)(7)
[ ] Policies and records retained six years ................................... 164.316(b)(2)(i)
```

## FAQ[#](#faq)

### What is a HIPAA compliance checklist?[#](#what-is-a-hipaa-compliance-checklist)

A HIPAA compliance checklist is a list of the safeguards the HIPAA Security Rule and Privacy Rule require, each tied to its section of 45 CFR Part 164. For IT and security teams, it covers risk analysis, access authorization, unique user IDs, MFA, audit logging, access reviews, offboarding, and business associate access.

### Does HHS publish an official HIPAA compliance checklist?[#](#does-hhs-publish-an-official-hipaa-compliance-checklist)

No. HHS publishes the rule, guidance, and an audit protocol, but no official checklist. OCR's [audit protocol](https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/audit/protocol/index.html) is the closest reference for how auditors test each requirement, and NIST SP 800-66 Revision 2 offers implementation guidance ([NIST](https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-66r2.pdf)).

### What is on a HIPAA IT compliance checklist?[#](#what-is-on-a-hipaa-it-compliance-checklist)

A HIPAA IT compliance checklist covers the technical and administrative controls IT owns: risk analysis, role-based access, unique user IDs, emergency access, automatic logoff, encryption, MFA, audit logs and log review, access reviews, deprovisioning, vendor access, and documentation retention.

### Does HIPAA require access reviews?[#](#does-hipaa-require-access-reviews)

HIPAA does not name access reviews, but it requires you to review and modify user access rights (164.308(a)(4)(ii)(C)) and regularly review access reports (164.308(a)(1)(ii)(D)). Periodic access reviews are the most common way to meet both and produce evidence for an audit.

### How quickly must access be removed when an employee leaves?[#](#how-quickly-must-access-be-removed-when-an-employee-leaves)

The current rule requires termination procedures but sets no deadline (164.308(a)(3)(ii)(C)). The 2025 proposed rule would require removal within one hour of employment ending. It is not final; OMB projects final action in July 2027.

### Is multi-factor authentication required by HIPAA?[#](#is-multi-factor-authentication-required-by-hipaa)

The current rule requires authenticating every person or entity that accesses ePHI (164.312(d)) without naming MFA. The proposed rule would require MFA with limited exceptions. Deploying it now on remote, privileged, and ePHI system access covers both.

### Do HIPAA rules apply to AI agents?[#](#do-hipaa-rules-apply-to-ai-agents)

Yes. The access control standard covers "persons or software programs" with access to ePHI (164.312(a)(1)). AI agents and service accounts that touch ePHI need unique identities, scoped access, logging, owners, and review, the same as people.

### How long do HIPAA records need to be kept?[#](#how-long-do-hipaa-records-need-to-be-kept)

Six years from the date of creation or the date the document was last in effect, whichever is later (164.316(b)(2)(i)). That includes policies, risk analyses, and access review records.

### What is C1.ai?[#](#what-is-c1ai)

C1.ai, formerly ConductorOne, is an identity governance platform for lifecycle automation, access requests, access reviews, and AI agent governance ([see the IGA platform](https://www.c1.ai/products/iga)).

**Turn this checklist into evidence that collects itself.** C1.ai runs access reviews on schedule, enforces policy in real time, and generates audit-ready reports on demand . [Book a demo](https://www.c1.ai/lp/request-demo) or [see C1.ai compliance and risk management](https://www.c1.ai/solutions/compliance-risk-management).

**Sources**

All sources accessed November 19, 2026.

- HIPAA Security Rule text: [45 CFR 164.308 (Cornell LII)](https://www.law.cornell.edu/cfr/text/45/164.308) ,[45 CFR 164.312 (Cornell LII)](https://www.law.cornell.edu/cfr/text/45/164.312)
- HHS guidance: [Summary of the HIPAA Security Rule](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html) ,[Addressable vs required FAQ](https://www.hhs.gov/hipaa/for-professionals/faq/what-is-the-difference-between-addressable-and-required-implementation-specifications/index.html) ,[Guidance on Risk Analysis](https://www.hhs.gov/hipaa/for-professionals/security/guidance/guidance-risk-analysis/index.html) ,[Security Series #2: Administrative Safeguards](https://www.hhs.gov/sites/default/files/ocr/privacy/hipaa/administrative/securityrule/adminsafeguards.pdf) ,[Security Series #4: Technical Safeguards](https://www.hhs.gov/sites/default/files/ocr/privacy/hipaa/administrative/securityrule/techsafeguards.pdf)
- OCR audit protocol: [Audit Protocol](https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/audit/protocol/index.html) ,[Audit Protocol (Security)](https://www.hhs.gov/hipaa/for-professionals/compliance-enforcement/audit/protocol-edited/index.html)
- Proposed rule: [Federal Register NPRM, Jan 6, 2025](https://www.federalregister.gov/documents/2025/01/06/2024-30983/hipaa-security-rule-to-strengthen-the-cybersecurity-of-electronic-protected-health-information) ,[HHS NPRM fact sheet](https://www.hhs.gov/hipaa/for-professionals/security/hipaa-security-rule-nprm/factsheet/index.html) ,[Davis Wright Tremaine summary](https://www.dwt.com/blogs/privacy--security-law-blog/2025/01/hipaa-security-rule-proposed-changes-in-2025) ,[McDermott Will & Schulte on July 2027 timeline](https://www.mcdermottlaw.com/insights/final-action-on-hipaa-security-rule-modifications-now-projected-for-july-2027/)
- Enforcement: [HHS MMG Fusion settlement, Mar 5, 2026](https://www.hhs.gov/press-room/ocr-mmg-fusion-hipaa-agreement.html) ,[Nixon Peabody on 14th Risk Analysis Initiative action](https://www.nixonpeabody.com/insights/articles/2026/07/21/health-plan-settlement-marks-ocrs-20th-ransomware-and-14th-risk-analysis-initiative)
- NIST: [SP 800-66 Rev. 2](https://nvlpubs.nist.gov/nistpubs/specialpublications/nist.sp.800-66r2.pdf)
- C1.ai: [Compliance and risk management](https://www.c1.ai/solutions/compliance-risk-management) ,[IGA](https://www.c1.ai/products/iga) ,[Pricing](https://www.c1.ai/pricing)
