On November 3 OCR posted its October 2026 quarterly cybersecurity newsletter, titled "Securing the Next 250." It is not a new rule and it does not add a new obligation. What it does is take the Cybersecurity and Infrastructure Security Agency's essential cyber hygiene steps for critical infrastructure (Healthcare and Public Health is one of 16 sectors) and put a specific Security Rule citation next to each one. Phishing training is pointed at 45 CFR § 164.308(a)(5). Strong passwords and MFA are pointed at 45 CFR § 164.312(d). Patching is pointed at 45 CFR § 164.308(a)(1)(ii)(A) and (B). Audit log review is pointed at 45 CFR § 164.312(b) and 45 CFR § 164.308(a)(1)(ii)(D). Backups are pointed at 45 CFR § 164.308(a)(7)(ii)(A). Encryption is pointed at 45 CFR § 164.312(a)(2)(iv) and 45 CFR § 164.312(e)(2)(ii). The newsletter is, in effect, OCR's own list of the Security Rule provisions behind the ransomware settlements it has issued over the last 18 months.
Three items in the newsletter are worth a small practice's direct attention. The first is the backup language: OCR says plainly that backups should include at least some offline copies, because current ransomware families target online backups as part of the attack. The second is the audit log language: review of system activity has to be regular, not just enabled, which is the finding behind the recent Lehigh Valley Health Network settlement. The third is a procedural clarification that is easy to miss: reporting a cyber incident to CISA does not satisfy HIPAA breach notification. Breach notices to OCR and to affected individuals still run on the 60-day clock in 45 CFR §§ 164.400 to 414.
For a 1 to 20 person practice this newsletter is useful because it hands you, in the agency's own voice, the exact short list of Security Rule provisions a current risk analysis should cover. It is not long. It is not full of industry jargon. It names each safeguard, pairs it with a citation, and in several places gives the small-practice version of the control (passphrases may suffice for some local access, MFA is most important for remote access and sensitive systems, encryption not feasible should be documented along with the alternate safeguard). If you were going to pick one page to walk through with your office manager or IT vendor once a year, this is a reasonable one to pick.
What to check in your practice
- Confirm that at least one copy of your practice's backup is offline, meaning it is not reachable from the same credentials that reach the live data. If every backup you have sits in the same cloud tenancy as the data it backs up, revise this. Current ransomware encrypts both.
- Pull the audit logs and access reports from your practice management system or EHR, from work email, and from the Microsoft 365 or Google Workspace admin console, for the last 30 to 90 days. Review them for unusual logins, after-hours access, failed login patterns, new or newly privileged accounts, and large exports. Record who did the review, the date, and anything flagged. If nothing has been reviewed in the last 12 months, this is the gap OCR has been citing.
- Check which accounts have MFA turned on, especially anything that can be reached from outside the office (remote access, email, the EHR portal, cloud file storage). OCR stops short of mandating MFA in the newsletter, but every ransomware settlement over the last year has cited environments without MFA on remote access.
- Note the CISA vs OCR distinction for your incident response plan. If you have a cyber incident and report it to CISA, that is fine, but it does not satisfy HIPAA breach notification. Breaches of unsecured PHI still go to OCR within 60 days of discovery, and breaches affecting 500 or more individuals go to OCR and to the media without delay.
- Walk the newsletter's list of Security Rule citations against your written risk analysis and security policies. If a citation in the newsletter has no corresponding entry in your own documentation, that is a gap to close. The newsletter itself is a short, agency-sourced version of that list.