Skip to content
HIPAA ComplianceConsulting

Core Assessment Service

HIPAA Security Risk Assessment (Security Risk Analysis)

The formal risk analysis the Security Rule requires: every system holding ePHI, real threats and vulnerabilities, rated by likelihood and impact, and documented to NIST-aligned methods.

Reviewed Request a HIPAA Consultation

The security risk analysis is the one assessment HIPAA explicitly requires of every covered entity and business associate. Under 45 CFR §164.308(a)(1)(ii)(A), you must conduct “an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability” of the ePHI you hold.

This engagement delivers that analysis. It is built around the elements HHS describes in its risk analysis guidance and the methods in NIST SP 800-30 and NIST SP 800-66 Rev. 2, and it produces a risk register your team can act on — not a generic questionnaire score.

Key points

  • Scope is all ePHI, wherever it lives — not just the EHR.
  • Each risk is rated on documented likelihood and impact, with reasoning.
  • Results feed directly into your risk management plan under §164.308(a)(1)(ii)(B).
  • Documentation is built to be retained for six years and produced on request.

Service overview

A security risk analysis answers a specific question: across every place your organization creates, receives, maintains or transmits ePHI, what could reasonably go wrong, how likely is it, and how bad would it be? The output is a ranked list of risks with enough context to decide what to fix first.

This is the deep, formal engagement within our broader HIPAA risk assessment services. If you need a requirement-by-requirement compliance check instead, that is a HIPAA gap analysis; many clients commission both.

Who needs a security risk analysis

  • Every covered entity and business associate with ePHI — the requirement applies regardless of size.
  • Organizations with no documented analysis, or one that predates current systems, vendors or locations.
  • Practices that completed the HHS SRA Tool themselves and want independent validation.
  • SaaS and health IT vendors whose covered entity customers request evidence of a current analysis.
  • Organizations after a security incident, acquisition, EHR change or move to cloud hosting.

Regulatory considerations

HHS guidance does not prescribe a single method, but it describes elements a risk analysis should include. We use these as the backbone of the engagement:

Risk analysis elements described in HHS guidance and how we address them
ElementWhat it means in practice
Scope of the analysisAll ePHI in all forms of electronic media — servers, cloud, endpoints, mobile devices, removable media, backups, vendor systems
Data collectionIdentify where ePHI is stored, received, maintained or transmitted, through inventory, interviews and document review
Identify threats and vulnerabilitiesReasonably anticipated threats (human, natural, environmental) and the weaknesses they could exploit
Assess current security measuresDocument the controls in place and whether they are configured and used properly
Determine likelihood of threat occurrenceRate how probable it is that a threat exploits a given vulnerability
Determine potential impactRate the effect on confidentiality, integrity and availability of ePHI
Determine the level of riskCombine likelihood and impact into a risk rating
Finalize documentationRecord the analysis, ratings and rationale
Periodic review and updatesRevisit as the environment changes; the rule does not fix a frequency

Common challenges in risk analysis

  • Shadow ePHI: exports in spreadsheets, scanned documents in shared folders, text messages and email attachments that nobody listed.
  • Vendor blind spots: billing, transcription, telehealth and messaging platforms excluded because “the vendor handles security.”
  • Asset lists that do not match reality, especially for laptops, tablets and medical devices.
  • Likelihood and impact assigned by instinct rather than recorded criteria, which makes ratings hard to defend.
  • Analysis performed once and never updated after significant operational changes.

Methodology

Our method follows NIST SP 800-30 Rev. 1 for risk assessment and uses NIST SP 800-66 Rev. 2 to map findings back to Security Rule standards. The rating scale is agreed with you at the start so results are consistent and repeatable in future updates.

Illustrative risk rating matrix (scale agreed during scoping)
Likelihood / ImpactLow impactModerate impactHigh impact
High likelihoodModerateHighHigh
Moderate likelihoodLowModerateHigh
Low likelihoodLowLowModerate

How we gather evidence

  • Interviews with the security official, IT, clinical or product leads and key vendors.
  • Review of configurations: identity and access management, logging, backups, encryption settings, endpoint management.
  • Walkthroughs of physical locations or, for remote-first companies, of the remote work model.
  • Review of BAAs and vendor security documentation for each business associate handling ePHI.

Threat categories we consider

Not every threat applies to every organization. A remote-first SaaS company and a rural hospital face different realistic scenarios, so the catalog is tailored during scoping rather than copied from a template.

  • Human, deliberate: phishing and credential theft, ransomware, insider snooping, theft of devices.
  • Human, accidental: misdirected email or fax, misconfigured cloud storage, improper disposal of media.
  • Technical: unpatched systems, unsupported operating systems, weak remote access, vendor compromise.
  • Environmental and natural: power loss, flooding, fire and regional disasters that threaten availability.

Optional technical depth

Where deeper testing is warranted, the analysis can be combined with a technical safeguards assessment. Vulnerability scanning and penetration testing are recommended practices rather than explicit Security Rule requirements, and are scoped separately when included.

Typical deliverables

  • ePHI inventory and data-flow diagram covering systems, devices, locations and vendors.
  • Threat and vulnerability catalog relevant to your environment.
  • Risk register with likelihood, impact, risk rating, existing controls and rationale for each entry.
  • Mapping of findings to Security Rule standards and implementation specifications.
  • Prioritized recommendations to feed your HIPAA risk management plan, labelled as required or recommended.
  • Executive summary and methodology statement suitable for retention under §164.316.

Engagement process

  1. 1

    Scope and rating criteria

    We confirm entities, locations, systems and vendors in scope and agree the likelihood and impact scales.

  2. 2

    Inventory and data flows

    We build or validate the ePHI inventory and map how information moves between people, systems and vendors.

  3. 3

    Control review

    Interviews, configuration review and walkthroughs establish which safeguards are in place and how well they work.

  4. 4

    Risk rating

    Each threat–vulnerability pair is rated, with reasoning recorded so future updates stay consistent.

  5. 5

    Validation

    Draft findings are reviewed with your team to correct factual errors before the report is final.

  6. 6

    Report and handoff

    We deliver the risk register and report and walk your owners through the highest-priority risks.

Cost factors

Cost is driven mainly by the number of systems, locations and vendors that handle ePHI; the number of legal entities in scope; whether technical testing is added; how accurate your existing asset inventory is; and whether this is a first analysis or an update to a well-documented prior one. Updates are generally lighter than first-time analyses. See HIPAA risk assessment cost for how these factors interact.

Frequently asked questions

What is the difference between this and the HHS SRA Tool?

The SRA Tool is a free, structured questionnaire from ONC and OCR, useful for smaller practices. Our engagement adds independent evidence gathering, configuration review and documented rating rationale. Using the tool does not by itself ensure compliance, and neither does any consultant engagement — what matters is an accurate, thorough analysis followed by risk management.

How often must the risk analysis be updated?

The Security Rule does not set a fixed interval. HHS describes risk analysis as an ongoing process, and the evaluation standard requires reassessment in response to environmental or operational changes. Many organizations update annually and after major changes.

Does the analysis have to include our vendors?

Your analysis must cover all ePHI you create, receive, maintain or transmit, which includes ePHI processed by vendors on your behalf. Business associates have their own Security Rule obligations, but you should understand and document the risks they introduce.

Will you fix the risks you find?

The analysis identifies and rates risks. Remediation is a separate step: some clients handle it internally, and others engage us for risk management planning or remediation support.

Is the proposed 2025 Security Rule change reflected?

The January 2025 NPRM proposed more detailed risk analysis requirements, among other changes. It is a proposal, not final law, so we assess against the current rule and can note where proposed changes might affect you. Verify the NPRM’s current status before planning around it.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.