Stealth Technology Group

A four-physician practice receives a letter from the Office for Civil Rights. A laptop was stolen from a billing employee’s car six months earlier, the practice reported it as required, and now investigators want documentation. Among the first requests is the practice’s most recent security risk analysis. The office manager produces a two-page checklist, dated eight years ago, with every box ticked. It lists no systems, names no threats, assigns no risk ratings, and leads to no action plan.

That document will not satisfy a regulator, and the practice is not unusual. The risk analysis is the cornerstone of the HIPAA Security Rule, and it is also the requirement that small organizations most often handle badly. The reason is rarely neglect. It is that the requirement is stated in a single sentence, and turning that sentence into a defensible document is a project that nobody has trained the practice to do.

This guide explains what the rule requires, how to perform an analysis in a structured way that a small team can manage, what auditors look for, and how to keep the analysis alive. It is general information rather than legal advice, so involve your compliance counsel or privacy officer where the stakes call for it.

What the Security Rule Actually Requires

The Security Rule requires covered entities and business associates to conduct an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of electronic protected health information they hold. It then requires them to implement security measures sufficient to reduce those risks and vulnerabilities to a reasonable and appropriate level. The first obligation is the risk analysis. The second is risk management. They are separate, and a regulator will ask for both.

Several features of the requirement matter in practice. It is mandatory, not addressable, meaning organizations cannot decide it is unnecessary for their size. It covers electronic protected health information wherever it lives, not just the main records system. It must be accurate and thorough, which implies a documented method, not a hurried walk-through. It is ongoing, so a single analysis completed years ago does not satisfy the obligation today. And the Rule requires that documentation be retained, generally for six years.

The Office for Civil Rights, which enforces the Rule, publishes guidance on the risk analysis requirement that identifies the elements it expects: defining the scope, collecting data, identifying threats and vulnerabilities, assessing current controls, determining likelihood and impact, assigning risk levels, and documenting the results. It has also repeatedly cited the absence of an adequate risk analysis in its enforcement actions, which tells you where regulators look first. HHS has also proposed updates to the Security Rule that would add more prescriptive requirements, so check the current regulatory status when you plan your next review.

businessman working in the office, select the icon security on the virtual display

Why Small Practices Struggle With It

Understanding the usual failures makes them easier to avoid. Checklists are mistaken for analyses. A checklist asks whether controls exist. An analysis asks what could go wrong, how likely it is, how bad it would be, and what you are doing about it. A document that answers only the first question leaves out the part the Rule is about.

Scope is too narrow. Practices often assess the electronic health record and forget the billing system, the email, the shared scanner, the text messages, the laptops, the backup drives, the patient portal, the telehealth platform, and the vendors that hold data on their behalf. Anything that creates, receives, maintains, or transmits electronic protected health information belongs in scope.

The analysis is performed once and filed. Environments change, and an analysis that describes an office that no longer exists is not accurate. A new system, a new vendor, or a new location changes the risk picture.

Findings go nowhere. An analysis that identifies risks but leads to no plan, owner, or deadline demonstrates knowledge without action, which regulators view unfavorably. And documentation is thin or missing, so even good work cannot be proven.

Step 1: Define the Scope and Inventory Your ePHI

Start by establishing where electronic protected health information exists. Walk through the life of patient information: how it arrives, where it is stored, who uses it, how it moves, and how it leaves.

List the systems and locations: the electronic health record, practice management and billing platforms, patient portals, email, secure messaging, fax and scanning systems, voicemail and call recordings, imaging equipment, laboratory interfaces, mobile devices, laptops and desktops, servers, cloud storage, backups and archives, and telehealth tools. Include medical devices that store or transmit data. Include paper that is scanned or transcribed into systems, because the electronic copy is in scope.

For each, note who has access, how they authenticate, where the data sits physically or in the cloud, and which vendors are involved. A simple data-flow diagram helps. It often reveals surprises, such as a staff member forwarding records to personal email, an old server still holding archives, or an application adopted by one department without review. These findings are exactly what the exercise is meant to uncover, and our articles on SaaS sprawl and shadow AI explain how unsanctioned tools accumulate. If staff are using AI tools with patient information, the guidance in our AI usage policy article is directly relevant.

Step 2: Identify Threats and Vulnerabilities

With the inventory in hand, ask what could harm the confidentiality, integrity, or availability of the data. Threats are things that could cause harm: ransomware, phishing and fraudulent emails, theft or loss of devices, snooping by employees, errors such as misdirected records, vendor breaches, power or hardware failure, fire or flood, and improper disposal of equipment. Vulnerabilities are weaknesses that a threat could exploit: unpatched software, missing multi-factor authentication, unencrypted laptops, shared logins, untested backups, weak physical controls, inadequate training, and unmanaged vendors.

Pair them. A lost laptop is a threat, and an unencrypted drive is the vulnerability that turns it into a reportable breach. Phishing is a threat, and the absence of multi-factor authentication is the vulnerability that lets one clicked link become a compromised mailbox. Our article on business email compromise and the guide to MFA fatigue attacks describe how those pairings play out, and the CISA guidance on multi-factor authentication explains why that control matters.

Do not rely on interviews alone. Technical evidence, such as a scan of systems for missing patches or a review of which accounts lack multi-factor authentication, turns opinion into fact. Our guide to vulnerability management as a service explains how that evidence is gathered.

Step 3: Assess the Controls You Already Have

Next, document what is currently in place. The Security Rule organizes safeguards into administrative, physical, and technical categories, and it is helpful to evaluate each.

Administrative safeguards include policies and procedures, workforce training, access authorization, sanctions for violations, contingency planning, and vendor agreements. Physical safeguards cover facility access, workstation placement and security, and handling of devices and media. Technical safeguards include unique user identification, access controls, audit logs, integrity protections, authentication, and transmission security such as encryption.

For each control, record how it is implemented, who owns it, and how well it works. “We have backups” is not an assessment. “Nightly backups run to a cloud service, one copy is immutable, the last successful restore test was in March, and the restore took four hours” is. Our guides on immutable backups and backup and data recovery explain what to look for, because availability of patient data during an outage is part of the Rule.

Step 4: Determine Likelihood, Impact, and Risk

This step converts findings into priorities. For each threat and vulnerability pair, estimate how likely it is to occur given your current controls, and how severe the consequences would be if it did. Impact in a medical practice includes exposure of patient information, interruption of care, regulatory penalties, and loss of trust.

A simple scale works for a small organization. Rate likelihood as low, medium, or high, rate impact the same way, and combine them into an overall risk rating. NIST SP 800-30, the federal guide to conducting risk assessments, describes this approach and can serve as a reference for method. The goal is consistency and explainability, not mathematical precision. You should be able to tell an auditor why something was rated high.

Step 5: Document Findings and Build a Risk Management Plan

The analysis is incomplete until it produces a plan. For each significant risk, define the response: reduce it with a control, transfer it, avoid it, or accept it knowingly. Assign an owner, set a target date, and describe what done looks like. Prioritize by risk level, but also consider quick wins that close several gaps at once, such as enforcing multi-factor authentication and device encryption together.

Document accepted risks explicitly, with the reasoning and who approved. A risk that is accepted deliberately and recorded is defensible. A risk that is ignored is not. Review progress on a schedule, and keep evidence that actions were completed, such as configuration screenshots, training records, and updated policies.

The risk analysis and the risk management plan together form the record that an investigator will want to see. NIST SP 800-66 Revision 2 offers detailed guidance on implementing the Security Rule, including how to link risk analysis to the selection of safeguards, and is a useful companion for the practice’s privacy or security officer.

Step 6: Keep It Current

The Rule contemplates ongoing risk analysis, and regulators expect to see evidence that it is maintained. A reasonable approach is a full review at least annually, plus an update whenever something significant changes. Triggers include adopting a new EHR or major application, opening or closing a location, merging or acquiring a practice, adding a new vendor that handles patient data, deploying new technology such as AI tools or telehealth, experiencing a security incident, and changes in the threat environment or regulations.

Treat the analysis as a living document. Keep a version history, record what was reviewed and when, and update the risk register as controls are implemented or new risks appear. A practice that can show an initial analysis, a plan, evidence of completed actions, and a dated annual update presents a very different picture from one that can show only a single report.

software developer work with AR new design dashboard computer icons of scrum agile development and code fork and versioning with responsive cybersecurity

Using Tools, and Their Limits

Small practices need a practical way to do this work. The Office of the National Coordinator and HHS offer a free Security Risk Assessment Tool designed for small and medium-sized providers. It walks users through questions about their policies and safeguards and generates a report. For many practices it is a sensible starting point, and it helps structure the work.

Its limits are worth understanding. It is a questionnaire that depends on the accuracy of the answers, and it does not test your systems. Someone who answers that encryption is enabled on every laptop has not verified it. The tool does not know about vendors you forgot, and it does not decide what is reasonable and appropriate for your circumstances. Use it as a framework, and supplement it with technical evidence and a review by someone who understands both the Rule and your environment.

For higher-risk or more complex practices, an independent assessor brings an outside view, technical testing, and credibility. Even for small practices, an outside review of the completed analysis can catch gaps before a regulator does.

Business Associates and Vendors

Practices rely on vendors for the EHR, billing, transcription, IT support, cloud storage, shredding, and more. Each vendor that creates, receives, maintains, or transmits electronic protected health information on your behalf is a business associate and must have a signed business associate agreement. Your risk analysis should include them.

Inventory the vendors, confirm that agreements are in place, and evaluate each one’s security. Ask what safeguards they use, how they would notify you of an incident, and what happens to your data when the relationship ends. Record the results and revisit them periodically. A vendor that is a blind spot in the analysis is a blind spot in your defenses, and our guide on how third-party vendors affect compliance explains how to approach vendor risk. Network design also affects exposure, so the principles in our article on network segmentation for mid-market businesses apply to separating clinical systems from guest and administrative networks.

What Auditors Want to See

Investigators and auditors look for evidence that the process is real. The table summarizes what a strong file contains. Keep documentation organized and retrievable. If an investigator asks for your risk analysis, you should be able to produce the current version, prior versions, and the evidence behind them within a day, not after weeks of searching. Our compliance programs are built around producing this kind of evidence continuously rather than assembling it under pressure.

Getting Help Without Losing Control

Small practices often have no dedicated security staff, which makes this work hard to fit around patient care. A managed approach spreads the load. Stealth Technology Group’s healthcare services combine managed IT services with cybersecurity and compliance support, delivered under the model described in our article on virtual managed services. A co-managed IT arrangement keeps your office manager or IT lead involved while an outside team supplies technical evidence and specialist depth. A vCIO helps practice leadership prioritize the risk management plan and budget for it. Practices in Boston, Tampa, and Sarasota can read the client results from regulated organizations that built compliance into operations.

diverse team engages in collaborative data analysis for cybersecurity strategies, utilizing digital tools and visual data in a modern office setting

Conclusion

A HIPAA security risk analysis that survives an audit is not a longer checklist. It is a documented process: scope the data, identify threats and vulnerabilities, assess the controls you have, rate the risks, turn the findings into a plan with owners and dates, and keep the whole thing current. It is within reach of a small practice when the work is broken into steps, supported by technical evidence, and maintained rather than filed.

The practice in the opening scene was not careless. It simply had a checklist where an analysis should have been. The difference between the two is the difference between a letter that ends in a corrective action plan and one that closes with a finding of good-faith compliance. Doing the work before the letter arrives is far easier than explaining its absence afterward.

If your organization is planning its CMMC compliance journey, contact Stealth Technology Group today at (617) 903-5559 to learn how modern cybersecurity infrastructure can accelerate your path toward certification readiness.

Scroll to Top