A security risk analysis (SRA) is a required implementation specification under 45 CFR §164.308(a)(1)(ii)(A): an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of all ePHI the organization holds. Because the requirement covers all ePHI, the effort — and therefore the cost — is driven by how much ePHI you have and where it lives.
This page is about scoping a single risk analysis. It walks through the factors that expand or shrink the work, the optional technical add-ons that are often bundled in, and how to decide between doing it yourself with the free HHS SRA Tool and engaging an outside assessor. It does not quote prices. For the cost of a whole program, see HIPAA compliance cost; for how consultants structure fees, see HIPAA consulting cost.
Key points
- Scope is set by ePHI, not headcount: every system, location and vendor holding ePHI must be considered.
- A risk analysis is not an audit and not a penetration test; those are different activities.
- The HHS SRA Tool is free, but using it does not by itself ensure compliance.
- Good existing documentation is the single biggest effort reducer.
Scoping factor 1: where ePHI lives
The first scoping question is not "how many employees?" but "how many places does ePHI exist?" HHS guidance expects the analysis to include ePHI in all forms of electronic media — servers, workstations, laptops, mobile devices, removable media, cloud services and backups. Each repository adds inventory, data-flow and control-review work.
| Repository type | Why it adds effort |
|---|---|
| EHR / practice management system | Core system; usually well documented, but access and audit controls need review |
| Email and file sharing | ePHI spreads informally; often under-controlled |
| SaaS applications (billing, scheduling, CRM, messaging) | Each needs BAA confirmation and configuration review |
| Cloud infrastructure (IaaS/PaaS) | Shared responsibility; IAM, logging and encryption settings need review |
| Endpoints and mobile devices | Encryption, loss risk and device management |
| Medical and IoT devices | Limited patching and vendor-controlled configurations |
| Backups and archives | Often forgotten; must be included |
Scoping factor 2: locations and entities
Each physical location brings its own physical safeguards under §164.310 — facility access, workstation use and security, device and media controls — and often its own network and local practices. Multiple legal entities or affiliated covered entities add documentation and interview work. Remote-first organizations shift effort from facility review to home-office and endpoint controls rather than eliminating it.
Scoping factor 3: documentation maturity
An assessor needs an asset inventory, network and data-flow diagrams, existing policies, prior risk analyses, vendor lists and BAAs. If these exist and are current, much of the effort is validation. If they don't, the assessor must build them through interviews and discovery, which is usually the largest single driver of effort.
| Documentation maturity | Effect on effort |
|---|---|
| Current inventory, diagrams, prior SRA and policies | Lower — focus on validating and updating |
| Partial or outdated documentation | Moderate — reconcile and fill gaps |
| Little or none; first-ever risk analysis | Higher — discovery and inventory from scratch |
Scoping factor 4: technical testing add-ons
A risk analysis can be performed through interviews, documentation review and configuration walkthroughs. Many organizations add technical testing to validate what interviews say. These add-ons are recommended practices that strengthen the analysis; they are not explicit requirements of the current Security Rule. (HHS's proposed Security Rule update published January 6, 2025 would add specific testing requirements; it is a proposal — verify its current status.)
- Vulnerability scanning of internal and external networks.
- Cloud configuration review against provider security benchmarks.
- Penetration testing of applications or networks.
- Phishing simulation to test workforce awareness.
- Review of identity and access settings, including MFA coverage.
Scoping factor 5: depth of analysis and deliverables
- Risk methodology: likelihood and impact ratings for each threat-vulnerability pair, consistent with HHS guidance and NIST SP 800-30.
- Whether the deliverable includes a prioritized risk management plan to support §164.308(a)(1)(ii)(B), or only a findings report.
- Executive briefing or board presentation.
- Re-assessment or annual update included or priced separately.
DIY with the HHS SRA Tool vs. an external assessment
The Security Risk Assessment Tool from ONC and OCR is free and walks smaller organizations through questions mapped to the Security Rule. It is a legitimate option. Its limits are the user's knowledge and objectivity: the tool records your answers; it cannot verify them or find the systems you forgot.
| Consideration | HHS SRA Tool (in-house) | External assessment |
|---|---|---|
| Direct cost | No license fee; internal time only | Consulting fees plus internal time |
| Best fit | Small, simple environments with a knowledgeable internal lead | Multiple systems or locations, cloud-heavy, first-ever SRA, or customer/OCR scrutiny |
| Objectivity | Self-assessment; blind spots likely | Independent view; challenges assumptions |
| Technical validation | None built in | Can include scanning and configuration review |
| Output | Tool reports based on your answers | Tailored report and remediation roadmap |
Worked scoping examples
The examples below are illustrative profiles, not quotes. They show how the same requirement produces very different levels of effort depending on the environment.
| Profile | Scope characteristics | Relative effort |
|---|---|---|
| Single-location therapy practice | One cloud EHR, email, a few laptops; prior SRA from the HHS tool | Lower — validate and update, focus on endpoints and email |
| Multi-specialty clinic with three sites | On-premises servers, imaging devices, several SaaS tools, no current inventory | Moderate to higher — discovery, physical review per site, device risks |
| Healthcare SaaS company (business associate) | Multiple cloud accounts, CI/CD pipeline, subprocessors, customer-driven deadline | Moderate — cloud configuration and vendor chain dominate |
| Regional hospital | Hundreds of applications, medical devices, many vendors and departments | Higher — often phased by department or system tier |
Updates cost less than first-time analyses
Because the risk analysis must stay accurate, it is not a one-time purchase. The good news is that a well-documented first analysis makes later updates far less effortful: the inventory, data flows and risk register already exist, so the work becomes reviewing changes, re-rating affected risks and confirming remediation. When budgeting, think of the first analysis as building the baseline and later cycles as maintaining it. Ask any outside assessor to deliver working files — not just a PDF — so your team or a future assessor can build on them.
Preparing to reduce effort
Our HIPAA risk assessment checklist lists the materials in more detail.
- 1
List systems
Draft a list of every application, device type and service that stores or transmits ePHI.
- 2
List vendors
Pull your vendor list and match it against signed BAAs.
- 3
Gather prior work
Collect earlier risk analyses, policies, network diagrams and audit findings.
- 4
Name contacts
Identify who can answer questions for IT, clinical or product operations, HR and facilities.
- 5
Decide on add-ons
Choose whether you want technical testing included now or later.
Frequently asked questions
Is the HHS SRA Tool enough for a HIPAA risk analysis?
It can be appropriate for small, simple organizations with someone knowledgeable completing it. HHS notes that using the tool does not guarantee compliance. The analysis still has to be accurate and thorough across all ePHI, and you must follow through with risk management.
Is a risk assessment the same as a penetration test?
No. A risk analysis evaluates threats, vulnerabilities, likelihood and impact across all ePHI. A penetration test actively tests specific systems for exploitable weaknesses. Testing can inform a risk analysis but does not replace it.
How often does the risk analysis need to be repeated?
The Security Rule does not set a fixed interval, but the analysis must stay accurate. Organizations commonly review it at least annually and whenever there are significant changes, such as new systems, locations, vendors or a security incident.
Does headcount drive the cost of a risk assessment?
Less than you might expect. The number of systems, locations and ePHI repositories, and the state of existing documentation, usually matter more than how many employees you have.
Will an outside assessor need access to PHI?
Often an assessment can be done without viewing patient records, focusing on systems and configurations. If the assessor will access PHI, a business associate agreement is required.
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.