Compliance program

HIPAA COMPLIANCE PROTECT PATIENT DATA AND PROVE I.T

The Health Insurance Portability and Accountability Act (HIPAA) Security Rule requires regulated organizations to protect the confidentiality, integrity and availability of electronic protected health information (ePHI). Hacking and ransomware lead large breach reports, the federal regulator says. We run the risk analysis, document safeguards, write policies and keep evidence current.

Who it is for
Clinics, health centers and their business associates
How it runs
A setup project, then a risk analysis every year and ongoing upkeep
What you get
Risk analysis, gap report, safeguard documentation, policy set

What the HIPAA Security Rule asks you to do

Citations are to Title 45 of the Code of Federal Regulations (CFR).

The Security Rule under the Health Insurance Portability and Accountability Act (HIPAA) asks the health care organizations it covers, and the businesses that handle their patient data, to protect the confidentiality, integrity and availability of electronic protected health information (ePHI). That means any patient data they create, receive, keep or send electronically (45 CFR 164.306). The safeguards come in three kinds: administrative, physical and technical.

Parts of the rule are labeled "required." Others, such as encrypting stored ePHI, are "addressable." That does not make them optional: you assess each one, put it in place if it is reasonable and appropriate, and if it is not, record why and use an equivalent measure where reasonable (164.306(d), 164.312(a)).

  • A risk analysis and risk management (164.308(a)(1))
  • A named security official, and regular review of audit logs and access reports (164.308(a)(1), (a)(2))
  • Security awareness training for the whole workforce, managers, volunteers and trainees included (164.308(a)(5), 160.103)
  • Incident procedures and a contingency plan, including data backup and disaster recovery plans (164.308(a)(6), (a)(7))
  • Controls on facility access, workstations, and the disposal and re-use of devices and media (164.310)
  • Unique user IDs, emergency access, audit controls and sign-in checks (164.312)
  • Written policies and procedures, kept for 6 years and reviewed periodically (164.316)

Who the HIPAA Security Rule applies to

The rule applies to covered entities and their business associates (164.302). Covered entities are health plans, health care clearinghouses, and health care providers that send health information electronically for standard transactions, such as insurance claims (160.103).

Business associates are outside companies that create, receive, keep or send patient data for a covered entity, or receive it to provide services such as legal, accounting or consulting work. Subcontractors that handle the data for them count too (160.103).

The proposed HIPAA Security Rule update is not final

We checked the Federal Register and the federal regulatory agenda in 2026.

The U.S. Department of Health and Human Services (HHS) proposed an update to the Security Rule on January 6, 2025, and comments closed on March 7, 2025 (proposed rule). No final rule has been published. HHS says that during the rulemaking "the current Security Rule remains in effect."

The spring 2025 regulatory agenda listed final action for May 2026. The latest agenda to list the rule, the 2026 edition, moved it to long-term actions with final action in July 2027. Agenda dates are plans, and this one has already moved. Our program is built on the rule in force today. Among the changes HHS proposed:

  • All specifications required, with limited exceptions, ending the "addressable" category
  • Encryption of ePHI at rest and in transit, and multi-factor authentication (MFA), with limited exceptions
  • Vulnerability scans at least every six months and a penetration test at least every 12 months
  • A compliance audit at least every 12 months, and yearly checks of business associates' safeguards

What a HIPAA security risk assessment covers

The assessment looks at all the ePHI your organization holds or sends, in any electronic form, and at the risks to keeping it private, accurate and available. HIPAA calls it a risk analysis; HealthIT.gov calls it a risk assessment.

The rule requires "an accurate and thorough assessment of the potential risks and vulnerabilities" (164.308(a)(1)(ii)(A)), then risk management to bring those risks down to a reasonable and appropriate level. For a broader security review beyond HIPAA, see our Cyber Risk Assessment.

HHS says no single method guarantees compliance. Its guidance lists these elements:

  • Set the scope and collect the data
  • Identify and document threats and vulnerabilities
  • Assess the security measures in place now
  • Judge the likelihood and impact of each threat, then the level of risk
  • Document the results and review them periodically

Why HIPAA settlements keep citing the risk analysis

The HHS Office for Civil Rights (OCR) has a Risk Analysis Initiative, and its June 18, 2026 settlement was the 14th enforcement action under it.

In February 2026, a substance use disorder treatment provider paid $103,000 after a phishing attack compromised patient ePHI. OCR found evidence it had not done an accurate and thorough risk analysis. In April, OCR settled four ransomware investigations, including one with a business associate, and made the same finding in each.

In June, an employer-sponsored group health plan paid $450,000 after a ransomware breach, and OCR listed the risk analysis failure among the potential violations.

How our HIPAA compliance program runs

It starts with a project, then continues on a schedule (how our compliance programs work).

  1. 01 AssessWe compare your setup with the Security Rule, list the gaps and run the risk analysis.
  2. 02 BuildWe document your safeguards, write your policies, list your business associates and guide the technical controls.
  3. 03 MaintainAs your systems and staff change, we keep your policies and evidence current.
  4. 04 Reassess yearlyEvery year we run the risk analysis again and update the program to match.

Documents the HIPAA program produces

  • 01HIPAA risk analysisThe threats to your ePHI, how likely and harmful each is, and the risk level.
  • 02Gap reportWhere your safeguards fall short of the Security Rule.
  • 03Safeguard documentationHow each safeguard is handled, including the reasons behind addressable choices.
  • 04Policy setWritten security policies and procedures, ready for your approval.
  • 05Business associate inventoryA list of the outside companies that handle ePHI for you.
  • 06Evidence kept currentRecords showing your safeguards in place, updated between risk analyses.

HIPAA IT services that carry out the safeguards

The program guides these controls. Separate services run them, where you contract them.

  • Managed Logging and SIEM MonitoringAlerts from your systems in one place, reviewed by our security team. Supports audit controls and log review.
  • Backup and Ransomware RecoveryImmutable backups with scheduled restore tests. Supports your backup and disaster recovery plans.
  • Security-First Endpoint ManagementProtection, threat detection and updates on every computer. Supports malware protection and, with drive encryption, encrypting stored ePHI.
  • Microsoft 365 Security ManagementSafer sign-ins, protected email and a locked-down Microsoft 365. Supports sign-in checks for your Microsoft 365 users.
  • Security Awareness and Phishing ReadinessShort training and practice phishing emails so your team can spot scams.
  • Incident Response ReadinessA response plan and practice drills, so everyone knows their role. Supports your incident procedures.

What we handle for HIPAA, What stays with you

CyberBlip

  • Run the gap assessment and the risk analysis
  • Document your safeguards and write your policies
  • Guide your technical controls and advise on physical safeguards
  • Keep the business associate inventory and evidence current

You

  • Tell us which systems and workflows hold patient data
  • Approve the risk analysis, policies and plan
  • Name your security official, as the rule requires
  • Make the risk decisions, including addressable choices
  • Bring in your attorney for breach response and notification

Questions about HIPAA compliance and IT services

We only have five employees. Do we really need HIPAA compliance?

Staff count does not decide it. A health care provider is covered when it sends health information electronically for standard transactions, such as insurance claims. If you are unsure that applies to you, ask your attorney. Size changes which safeguards are reasonable, since the rule lets you weigh your size, systems and the cost of each measure.

Is there such a thing as HIPAA certified IT?

Not in a form HHS recognizes. HHS says no Security Rule standard requires certification, and that it does not recognize private "certifications," which do not remove your legal obligations. What counts is your risk analysis, your safeguards and the records that show them, which is why we describe our work as aligned with the Security Rule.

How often should we do a HIPAA security risk assessment?

The current rule does not set a schedule. HHS calls risk analysis an ongoing process and notes that some organizations do it every year or as needed. Our program repeats the risk analysis every year and keeps your policies and evidence current in between.

Is the free HHS risk assessment tool enough?

Not on its own. HealthIT.gov's free Security Risk Assessment Tool is built for small and medium providers and keeps your answers on your own computer. HealthIT.gov also says the tool is not required, does not guarantee compliance, and its survey alone may not find every risk.

Our electronic health record (EHR) system is in the cloud. Isn't the vendor responsible for HIPAA?

The vendor has its own duties, but they do not replace yours. A company that keeps or sends patient data for you is a business associate under the rule, and you need a written contract or other arrangement with it. Your risk analysis still covers the ePHI in that system, and our program lists the vendor in your business associate inventory.

If we have a breach, will you handle the notifications?

No. Deciding who must be told is a legal call that your attorney leads. Planning for that day is part of our Data Breach Readiness Program. For a breach of unsecured patient data, meaning data not made unreadable by a method HHS specifies, the rule says the people affected must be told without unreasonable delay and no later than 60 calendar days after discovery. A business associate must tell the covered entity within the same limit.

Sources

Show all 19 sourcesHide sources
  1. Who the Security Rule applies to, 45 CFR 164.302 eCFR, 2026-11-13
  2. Covered entity, business associate and workforce definitions, 45 CFR 160.103 eCFR, 2026-11-13
  3. 45 CFR 164.306, Security standards: General rules (HIPAA Security Rule) eCFR, 2026-11-13
  4. 45 CFR 164.308, Administrative safeguards (HIPAA Security Rule) eCFR, 2026-11-13
  5. Physical safeguards, 45 CFR 164.310 eCFR, 2026-11-13
  6. Technical safeguards, 45 CFR 164.312 eCFR, 2026-11-13
  7. Policies, procedures and documentation, 45 CFR 164.316 eCFR, 2026-11-13
  8. 45 CFR Part 164 Subpart D, Notification in the case of breach of unsecured protected health information eCFR, 2026-11-13
  9. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information, proposed rule, 90 FR 898 Federal Register, 2025-01-06
  10. Documents published under the proposal's regulation number, 0945-AA22 Federal Register, 2026-11-17
  11. HIPAA Security Rule update in the Spring 2025 Unified Agenda reginfo.gov, 2025
  12. HIPAA Security Rule update, Unified Agenda entry RIN 0945-AA22 reginfo.gov, Office of Information and Regulatory Affairs, 2026
  13. HIPAA Security Rule Notice of Proposed Rulemaking Fact Sheet HHS, 2024-12-27
  14. Guidance on Risk Analysis HHS, 2026-08-12
  15. Security Risk Assessment Tool HealthIT.gov, 2026-09-18
  16. Settlement with a substance use disorder treatment provider HHS Office for Civil Rights, 2026-02-19
  17. HHS' Office for Civil Rights Settles Four HIPAA Security Rule Ransomware Investigations HHS Office for Civil Rights, 2026-04-23
  18. Ransomware settlement with a group health plan HHS Office for Civil Rights, 2026-06-18
  19. Are we required to "certify" our organization's compliance with the standards of the Security Rule? HHS, 2013-07-26

Next step

Find out where you stand

Tell us how we can best support you.

Icons: Tabler Icons, MIT License. License text: /licenses/tabler-icons.txt