Regulation · Healthcare · US law

HIPAA compliance: Security Rule safeguards, Privacy Rule and breach notification

HIPAA is the US Health Insurance Portability and Accountability Act of 1996. Its rules, in 45 CFR Parts 160 and 164, require covered entities and business associates to protect health information: the Privacy Rule limits use and disclosure, the Security Rule sets safeguards for electronic PHI, and the Breach Notification Rule sets reporting deadlines.

Key takeaways

What you need to know about HIPAA

Two rolesCovered entities and their business associates both carry obligations.
Risk analysisThe Security Rule starts with an accurate, thorough risk analysis.
Required and addressableSome specifications are required; addressable ones need a documented decision.
60 daysBreaches of unsecured PHI go to individuals within 60 days.
No certificateOCR enforces HIPAA; no body can certify you as compliant.

Who must comply with HIPAA?

HIPAA is law; whether it applies depends on your role with health information.

Healthcare providersDoctors, clinics and hospitals that bill electronically.
Health plansInsurers, HMOs and employer group health plans.
Healthcare clearinghousesOrganisations that process health information formats.
Business associatesSaaS, billing, cloud and IT vendors handling PHI for covered entities.
SubcontractorsVendors of business associates that touch PHI.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

HIPAA rules

What does HIPAA require?

HIPAA requires you to limit how PHI is used and disclosed, protect electronic PHI with administrative, physical and technical safeguards, sign business associate agreements, and report breaches on time.

164.500s Privacy

Privacy Rule

Uses and disclosures, minimum necessary, patient rights, notices.

In QULDEX: Disclosure and request logs
164.308 Security

Administrative safeguards

Risk analysis, workforce, training, incidents, contingency, BAAs.

In QULDEX: Risk analysis in the risk register
164.310 Security

Physical safeguards

Facilities, workstations, devices and media.

In QULDEX: Disposal and access evidence
164.312 Security

Technical safeguards

Access, audit controls, integrity, authentication, transmission.

In QULDEX: Log and access reviews scheduled
164.314–316 Security

Organisational and documentation

BAA terms, policies, six-year retention.

In QULDEX: Retention enforced in the vault
164.400s Breach

Breach Notification Rule

Individuals, media, HHS and business associate notices.

In QULDEX: 60-day clock per breach
Part 160 Enforcement

Enforcement Rule

OCR investigations and tiered civil penalties.

In QULDEX: Audit trail ready for OCR
Standards explorer

What are the HIPAA Security Rule safeguards?

The Security Rule has standards in four groups of safeguards plus documentation, and the Breach Notification Rule adds four notice requirements. Select any standard to see what it asks for, typical evidence and the matching NIST CSF and ISO 27001 controls.

3safeguard types: administrative, physical, technical
21Security Rule standards in the explorer
60 daysbreach notice to individuals
6 yearsdocumentation retention

Showing up to 6 per group. Search, filter, or open a group to see all 25.

Administrative safeguards 9

  1. 164.308(a)(1)Security management process

    Run a risk analysis and risk management, apply a sanction policy and review system activity.

    In QULDEXThe risk analysis lives in the risk register and is refreshed on schedule.

    Typical evidence
    Risk analysis, risk management plan
    Maps to
    NIST ID.RAISO 27001 6.1.2

  2. 164.308(a)(2)Assigned security responsibility

    Name a security official responsible for the Security Rule.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Security official appointment
    Maps to
    ISO 27001 A.5.2

  3. 164.308(a)(3)Workforce security

    Make sure workforce members have appropriate access to ePHI and remove it when they leave.

    In QULDEXJoiner and leaver tickets attach as evidence.

    Typical evidence
    Access provisioning records
    Maps to
    ISO 27001 A.5.18SOC 2 CC6.2

  4. 164.308(a)(4)Information access management

    Authorise access to ePHI based on role and need.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Access authorisation records
    Maps to
    ISO 27001 A.5.15

  5. 164.308(a)(5)Security awareness and training

    Train the workforce, including on malware, log-in monitoring and passwords.

    In QULDEXTraining completion is imported and checked against headcount.

    Typical evidence
    Training records
    Maps to
    ISO 27001 A.6.3NIST PR.AT

  6. 164.308(a)(6)Security incident procedures

    Identify, respond to, mitigate and document security incidents.

    In QULDEXIncidents are logged with response steps and evidence.

    Typical evidence
    Incident log
    Maps to
    ISO 27001 A.5.24–A.5.26NIST RS.MA

  7. 164.308(a)(7)Contingency plan

    Keep data backup, disaster recovery and emergency mode plans, and test them.

    In QULDEXBackup and recovery tests are scheduled with results attached.

    Typical evidence
    Contingency plan, test results
    Maps to
    ISO 27001 A.5.29A.8.13NIST RC.RP

  8. 164.308(a)(8)Evaluation

    Evaluate security periodically and after operational or environmental changes.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Evaluation reports

  9. 164.308(b)(1)Business associate contracts

    Get satisfactory assurances from business associates through a written contract.

    In QULDEXEach business associate record links its BAA.

    Typical evidence
    BAAs
    Maps to
    ISO 27001 A.5.20NIST GV.SC

Physical safeguards 4

  1. 164.310(a)(1)Facility access controls

    Limit physical access to systems and facilities holding ePHI.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Badge logs, facility security plan
    Maps to
    ISO 27001 A.7.2

  2. 164.310(b)Workstation use

    Specify how workstations that access ePHI should be used.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Workstation policy

  3. 164.310(c)Workstation security

    Physically safeguard workstations that access ePHI.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

  4. 164.310(d)(1)Device and media controls

    Control receipt, movement, disposal and re-use of devices and media with ePHI.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Disposal certificates, media log
    Maps to
    ISO 27001 A.7.10A.7.14

Technical safeguards 5

  1. 164.312(a)(1)Access control

    Allow access to ePHI only to authorised people and software, with unique IDs and emergency access.

    In QULDEXAccess reviews run as recurring tasks; revocations become tracked actions.

    Typical evidence
    Access reviews, unique ID policy
    Maps to
    ISO 27001 A.5.15A.8.5NIST PR.AA

  2. 164.312(b)Audit controls

    Record and examine activity in systems that contain ePHI.

    In QULDEXLog review evidence is collected on schedule.

    Typical evidence
    Audit log reviews
    Maps to
    ISO 27001 A.8.15SOC 2 CC7.2

  3. 164.312(c)(1)Integrity

    Protect ePHI from improper alteration or destruction.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Integrity controls

  4. 164.312(d)Person or entity authentication

    Verify that anyone seeking access to ePHI is who they claim to be.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    MFA settings
    Maps to
    ISO 27001 A.8.5

  5. 164.312(e)(1)Transmission security

    Guard ePHI sent over networks against unauthorised access.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    Encryption in transit
    Maps to
    ISO 27001 A.8.24SOC 2 CC6.7

Organisational and documentation 3

  1. 164.314(a)Business associate contract requirements

    Business associate contracts must include required terms, such as safeguarding ePHI and reporting incidents.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    BAA template review

  2. 164.316(a)Policies and procedures

    Implement reasonable policies and procedures to comply with the Security Rule.

    In QULDEXPolicies are versioned with approvals and linked to standards.

    Typical evidence
    Policy set

  3. 164.316(b)(1)Documentation and retention

    Document actions and assessments and keep them for six years.

    In QULDEXRetention is enforced on documents in the vault.

    Typical evidence
    Document register

Breach notification 4

  1. 164.404Notice to individuals

    Notify affected individuals without unreasonable delay, and no later than 60 days after discovering a breach of unsecured PHI.

    In QULDEXBreaches are logged with a running 60-day clock.

    Typical evidence
    Notification letters

  2. 164.406Notice to the media

    Notify prominent media when a breach affects more than 500 residents of a state or jurisdiction.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

  3. 164.408Notice to the Secretary (HHS)

    Notify HHS within 60 days for breaches of 500 or more; log smaller breaches and report them annually.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

    Typical evidence
    HHS breach portal submissions

  4. 164.410Notification by a business associate

    Business associates notify the covered entity of breaches without unreasonable delay, within 60 days.

    In QULDEXQULDEX gives this standard an owner, a review cycle and an evidence request, and maps it to NIST CSF and ISO 27001.

Citations follow 45 CFR Part 164. Summaries are QULDEX paraphrases, not legal advice; the eCFR text is the authority. HHS has proposed Security Rule changes; check their status before go-live.

Compliance path

How do you become HIPAA compliant?

There is no HIPAA certification. You confirm your role, run a risk analysis, put safeguards and policies in place, sign BAAs and keep six years of evidence. A first programme usually takes 3 to 9 months.

  1. Confirm your role and map PHI

    Decide whether you are a covered entity, business associate or both, and map where PHI and ePHI live.

  2. Run the security risk analysis

    Assess risks to the confidentiality, integrity and availability of all ePHI, as 164.308(a)(1) requires.

  3. Put safeguards in place

    Implement administrative, physical and technical safeguards, and document decisions on addressable specifications.

  4. Policies, training and BAAs

    Write policies, train the workforce and sign business associate agreements.

  5. Test contingency and incident response

    Test backups, disaster recovery and incident procedures, and fix what fails.

  6. Independent assessment (optional)

    A third party assesses your programme, or you pursue a framework certification such as HITRUST.

  7. Keep it current

    On changeUpdate the risk analysis
    YearlyTraining and evaluation
    6 yearsKeep documentation

Durations are typical planning ranges from QULDEX delivery, not legal requirements.

Documentation

Which documents does HIPAA require?

OCR asks for these first in an investigation. The risk analysis is the most common gap in enforcement actions.

Document or recordCitationWhere it lives in QULDEX
Security risk analysis164.308(a)(1)Risk register
Risk management plan164.308(a)(1)Risk register
Security official designation164.308(a)(2)Program setup
Training records164.308(a)(5)Evidence vault
Incident log and responses164.308(a)(6)CAPA automation
Contingency plan and test results164.308(a)(7)Evidence vault
Business associate agreements164.308(b), 164.314Vendor register
Policies and procedures164.316Evidence vault · policy library
Breach notifications and HHS submissions164.404–164.410CAPA automation
Notice of privacy practices164.520Evidence vault

Keep documentation for six years from creation or last effective date (164.316(b)(2)).

Time and cost

How long does HIPAA compliance take and what drives the effort?

A first programme usually takes 3 to 9 months, then runs continuously. Effort depends on how many systems hold ePHI, how many business associates you have and your incident history.

Where the time goes

Role and PHI mapping2–4 wk
Risk analysis4–8 wk
Safeguards2–5 mo
Policies, training, BAAs1–2 mo
Testing1–2 mo

Bars show the upper end of each range on one scale (5 months = full width).

What changes the effort

  • Systems with ePHI: each needs safeguards and evidence
  • Business associates: every one needs a BAA and oversight
  • Workforce size: training and access management scale with headcount
  • Existing SOC 2 or ISO 27001: reused controls cover much of the Security Rule
  • Incident history: past breaches bring OCR scrutiny
Readiness check · 2 minutes

How ready are you for a HIPAA review?

OCR and healthcare customers check these eight things first. Nothing you enter leaves this page.

RoleHave you confirmed whether you are a covered entity or business associate?
164.308(a)(1)Is your security risk analysis current and complete?
164.308(a)(2)Have you named a security official?
164.308(a)(5)Has the workforce completed security training this year?
164.308(b)Do all business associates have signed BAAs?
164.312(b)Do you log and review activity on systems with ePHI?
164.308(a)(7)Have you tested backups and disaster recovery?
164.404Can you notify individuals within 60 days of a breach?
Crosswalk

How HIPAA maps to NIST CSF 2.0, ISO 27001 and SOC 2

HHS has published a crosswalk between the HIPAA Security Rule and the NIST Cybersecurity Framework, and most safeguards have ISO 27001 and SOC 2 counterparts. One tested control can support all of them.

HIPAA Privacy Rule vs Security Rule

Privacy RuleSecurity Rule
CoversAll PHI, in any formElectronic PHI (ePHI) only
FocusWho can use and disclose PHI, and patients' rightsSafeguards that protect ePHI
Key dutiesMinimum necessary, notices, access requests, authorisationsRisk analysis, administrative, physical and technical safeguards
Applies toCovered entities; business associates by contractCovered entities and business associates directly
Citation45 CFR 164 Subpart E45 CFR 164 Subpart C
In QULDEXQULDEX tracks Privacy Rule requests and Security Rule safeguards in one programme with shared evidence.

Safeguard crosswalk

HIPAA Security RuleNIST CSF 2.0ISO 27001:2022SOC 2Shared evidence
164.308(a)(1) Risk analysisID.RA6.1.2CC3.2Risk analysis
164.308(a)(3) Workforce securityPR.AAA.5.18CC6.2Access provisioning
164.308(a)(5) TrainingPR.ATA.6.3CC1.4Training records
164.308(a)(6) IncidentsRS.MAA.5.24–A.5.26CC7.3–CC7.5Incident log
164.308(a)(7) ContingencyRC.RPA.5.29 · A.8.13A1.2–A1.3Recovery tests
164.308(b) BAAsGV.SCA.5.20CC9.2BAAs
164.310(d) Device and mediaPR.DSA.7.10 · A.7.14CC6.5Disposal records
164.312(a) Access controlPR.AAA.5.15 · A.8.5CC6.1Access reviews
164.312(b) Audit controlsDE.CMA.8.15CC7.2Log reviews
164.312(e) TransmissionPR.DSA.8.24CC6.7Encryption settings

Indicative mapping aligned to HHS's HIPAA-to-NIST crosswalk approach. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

How QULDEX runs HIPAA compliance from risk analysis to audit

QULDEX is HIPAA compliance and audit management software built from EGV Group's audit delivery, used by covered entities, business associates and the assessors who test them. Pick your role to see who does what.

For healthcare organisations and their vendors.

  1. Role and PHIMap PHIPHI inventory linked to systems and vendors
  2. Risk analysisAssess risksRisk analysis refreshed on schedule
  3. SafeguardsRun the safeguardsStandards with owners and evidence requests
  4. BAAsSign agreementsVendor register with BAAs
  5. BreachesNotify on timeBreach log with a 60-day clock
  6. AuditProve complianceControlled, logged evidence for OCR and customers
Without one systemWith QULDEX
Risk analysis done once and forgottenRisk analysis refreshed on schedule and on change
BAAs scattered across inboxesBAAs linked to each business associate
Separate work for HIPAA and SOC 2One control set mapped to both
Breach decisions undocumentedDecision records with a 60-day clock
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

HIPAA questions people ask

Who needs to comply with HIPAA?

Covered entities (healthcare providers that bill electronically, health plans and clearinghouses) and their business associates and subcontractors that handle PHI.

Is there an official HIPAA certification?

No. HHS does not certify organisations or recognise any HIPAA certification. You can get an independent assessment or a framework certification such as HITRUST.

What are the three HIPAA safeguards?

Administrative, physical and technical safeguards under the Security Rule, plus organisational and documentation requirements.

What is the HIPAA breach notification deadline?

Notify affected individuals without unreasonable delay and no later than 60 days after discovery. Breaches of 500 or more also go to HHS and, by state, to the media.

What is a business associate agreement?

A contract a covered entity signs with a vendor that handles PHI on its behalf, setting how the vendor must protect PHI and report incidents.

What is the difference between required and addressable specifications?

Required specifications must be implemented. Addressable ones must be implemented if reasonable and appropriate, or you document why not and what you do instead. HHS has proposed changes to this; check the current rule.

Can QULDEX run HIPAA alongside SOC 2 and ISO 27001?

Yes. Safeguards are mapped once to NIST CSF, ISO 27001 and SOC 2, so one evidence set supports each.

Sources

References

  1. 45 CFR Part 160 and Part 164 (Privacy, Security and Breach Notification Rules). ecfr.gov
  2. HHS OCR, Guidance on Risk Analysis Requirements under the HIPAA Security Rule. hhs.gov
  3. HHS, HIPAA Security Rule Crosswalk to the NIST Cybersecurity Framework. hhs.gov
  4. NIST SP 800-66 Rev. 2, Implementing the HIPAA Security Rule. nist.gov
  5. HHS, Breach Notification Rule guidance. hhs.gov

Reviewed by

Swati Chaturvedi

Framework reviewer · QULDEX

Reviewed this page against 45 CFR Parts 160 and 164 and HHS guidance: safeguards, breach notification and the NIST crosswalk.

Page history
  • : Rebuilt with standards explorer, breach notification rules, compliance path and readiness check
  • : Page first published

Find your HIPAA gaps in 15 minutes

Answer a short readiness check and get a gap summary by standard. No sales call needed to see the result.

Schedule
Book a Demo