🇺🇸 United States · Framework guide

HIPAA: the Security Rule, the risk analysis and what OCR actually enforces

HIPAA has no certification and no checklist from the regulator, which is why so many organisations are unsure whether they comply. What the Office for Civil Rights enforces is specific: a documented risk analysis, safeguards that follow from it, policies that are followed, training that happened and breaches that were reported on time. This guide sets out those obligations and how to evidence them.

RegulatorUS Department of Health and Human Services, Office for Civil Rights (OCR)
Applies toCovered entities (health plans, healthcare clearinghouses, providers that transmit health information electronically) and their business associates
RulesPrivacy Rule (2003), Security Rule (2005), Breach Notification Rule (2009, HITECH Act), Omnibus Rule (2013)
Security Rule structureAdministrative, physical and technical safeguards; each standard has required and addressable implementation specifications
Breach notificationIndividuals without unreasonable delay and within 60 days; HHS within 60 days for breaches of 500+ (annually for smaller); media for 500+ in a state
Pending changeHHS proposed a substantial Security Rule update in January 2025; check its current status before planning

The Security Rule is technology-neutral and scales with the organisation, which is why it reads as principles rather than settings. The anchor is the risk analysis required by 45 CFR 164.308(a)(1): an accurate and thorough assessment of risks to the confidentiality, integrity and availability of electronic protected health information. In OCR settlements, a missing or inadequate risk analysis is the most common finding, ahead of any technical control.

“Addressable” does not mean optional. For each addressable specification the organisation must implement it, implement a reasonable alternative, or document why neither is reasonable. Auditors ask for that documentation.

The safeguards, by category

Administrative safeguards

Security management process (risk analysis, risk management, sanctions, activity review), assigned security responsibility, workforce security and clearance, information access management, security awareness and training, incident procedures, contingency planning, periodic evaluation, business associate contracts.

Physical safeguards

Facility access controls, workstation use and security, device and media controls including disposal, re-use and accountability.

Technical safeguards

Access control with unique user identification, emergency access, automatic logoff and encryption; audit controls; integrity controls; person or entity authentication; transmission security.

Organisational requirements and documentation

Business associate agreements with the required terms; policies and procedures maintained, retained for six years and updated when the environment changes.

Privacy Rule obligations

Notice of privacy practices, minimum necessary use and disclosure, individual rights of access and amendment, accounting of disclosures, designated privacy official.

Breach notification

Risk assessment of every impermissible use or disclosure (nature of the PHI, who received it, whether it was acquired, mitigation), notification within the deadlines, and a breach log.

Who it applies to

Hospitals, clinics, physician practices, pharmacies, laboratories, health plans and insurers, clearinghouses, and every vendor that creates, receives, maintains or transmits protected health information for them: cloud hosts, EHR and practice-management SaaS, billing companies, analytics firms, IT managed service providers, and their subcontractors. Business associates are directly liable under HIPAA since the 2013 Omnibus Rule.

How GRCorb covers HIPAA Security Rule

From scope to evidence, in one system

A risk analysis OCR would recognise

The Risk & Quantification module records ePHI assets, threats, vulnerabilities, likelihood, impact and the resulting risk register, with FAIR-style quantification where the board wants dollar figures, and keeps the history that proves the analysis is periodic.

Safeguards as controls with evidence

Each standard and implementation specification is a control with an owner, a required or addressable flag, the decision record for addressable items, and evidence collected from Microsoft 365, Entra ID, Intune, AWS, Azure and Google Cloud.

Policies, training and acknowledgement

The AI Policy Builder writes the HIPAA policy set; the Awareness module delivers training and simulated phishing; the Policy Register tracks acknowledgement per employee, which is the workforce evidence OCR asks for.

Business associate register

Vendors handling PHI are tiered, their agreements and assurance held against the engagement, and review dates tracked.

Incident and breach timers

Incidents carry the four-factor breach risk assessment and the 60-day clocks, with the breach log maintained as a report.

Frequently asked questions

Is there a HIPAA certification?

No. HHS does not certify compliance and does not endorse any third-party certification. What you can produce is a current risk analysis, documented safeguards, policies, training records and an audit trail. Many organisations also obtain a SOC 2 or HITRUST report to show customers.

What does “addressable” mean?

You must assess whether the specification is reasonable and appropriate for your environment. If it is, implement it. If not, document why and implement an equivalent alternative where reasonable. The decision must be written down.

Does HIPAA apply to a SaaS vendor that never looks at the data?

If the vendor creates, receives, maintains or transmits PHI on behalf of a covered entity it is a business associate, encrypted or not, and needs a business associate agreement and its own safeguards. Pure conduits such as internet carriers are the narrow exception.

How often must the risk analysis be updated?

The Rule says periodically and whenever the environment changes materially. OCR guidance and settlements point to at least annually and after any significant system, vendor or organisational change.

Related frameworks

Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.