In short
- The HIPAA Security Rule requires covered entities and business associates, including a startup that creates, receives, maintains or transmits PHI on a covered entity's behalf, to conduct an accurate and thorough assessment of the risks and vulnerabilities to the confidentiality, integrity and availability of its ePHI.
- HHS does not prescribe a method, but NIST SP 800-66 Rev. 2 describes one in seven steps: prepare by mapping where ePHI lives and flows, identify threats and vulnerabilities, rate likelihood and impact, determine the level of risk and document the results.
- The analysis feeds a required risk management plan, must be kept in writing for six years, and must be reviewed and updated when your environment or operations change.
A HIPAA risk analysis is a written, accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the electronic PHI your company holds. The Security Rule makes it a required implementation specification for every covered entity and business associate. For a startup, the first one is mostly a mapping exercise: find every place ePHI is created, received, stored, processed and sent, list what could go wrong at each, rate each risk, and write down what you will do about it.
Does a startup need a HIPAA risk analysis?
Yes, if it is a covered entity or a business associate. Under 45 CFR 160.103, a business associate is a person who, on behalf of a covered entity, creates, receives, maintains or transmits protected health information for a regulated function, such as claims processing, data analysis, quality assurance, billing or practice management. The definition also covers subcontractors that handle PHI on behalf of a business associate. A software company that stores patient data for a clinic or a health plan usually fits it.
The obligation sits in 45 CFR 164.308(a)(1), the security management process standard, which requires policies and procedures to prevent, detect, contain and correct security violations. It has four required implementation specifications: risk analysis, risk management, a sanction policy for workforce members who break security policies, and regular review of information system activity records such as audit logs and access reports.
HHS's Office for Civil Rights enforces this requirement through its Risk Analysis Initiative. In April 2025 it announced its sixth action under the initiative: Northeast Radiology paid $350,000 after OCR found it had failed to conduct an accurate and thorough security risk analysis. The two-year corrective action plan required a risk analysis, a written risk management plan, revised policies and procedures, and workforce training.
What does accurate and thorough mean for a small company?
The Security Rule is flexible by design. Under 45 CFR 164.306(b), you choose security measures considering your size, complexity and capabilities, your technical infrastructure and software security capabilities, the costs of the measures, and the probability and criticality of potential risks to ePHI. NIST SP 800-66 Rev. 2 adds that HHS does not prescribe any particular risk assessment or risk management method. A five-person startup and a hospital system will produce very different documents, and both can be compliant.
The flexibility comes with a duty to document. For addressable implementation specifications, such as encryption at rest, the rule requires you to assess whether each one is reasonable and appropriate in your environment. If it is, you implement it. If it is not, you document why and implement an equivalent alternative where reasonable. Your risk analysis is where those decisions get their justification.
How do you run your first risk analysis?
NIST SP 800-66 Rev. 2 describes a seven-step process based on NIST's general risk assessment guidance. The steps do not have to run in strict order, and some can run at the same time.
1. Prepare: map where ePHI lives and moves
NIST says to identify where ePHI is generated, where and how it enters the organization, for example through web portals, where it moves and is stored, and where it leaves, including to cloud and other service providers. Note how access is controlled and whether ePHI is encrypted at rest and in transit. The scope should cover remote staff and external providers with remote access, laptops and mobile devices, and online tracking technologies on your websites and apps.
For a software startup, the places that get missed are rarely the production database. Check these too:
- Backups and snapshots, and where they are stored.
- Application and server logs, error tracking and APM tools that may capture request bodies.
- Analytics, session replay and marketing pixels on pages where patients log in.
- Email, SMS and push providers that send messages with patient details.
- Customer support tools where users paste screenshots or records.
- Staging and test environments loaded with copies of production data.
- Data warehouses, exports and the laptops of people who run ad hoc queries.
- Every vendor in that path, and whether you have a BAA with each one.
2. Identify reasonably anticipated threats
List the threat events and sources that apply to you: natural, such as floods and storms; human, intentional or not, such as network attacks, malware uploads, unauthorized access and data entry errors; and environmental, such as long power failures. NIST specifically calls out phishing, ransomware and insider threats against the confidentiality, integrity and availability of ePHI.
3. Identify vulnerabilities
List the technical and non-technical weaknesses those threats could exploit. NIST suggests internal sources, such as earlier risk assessments, vulnerability scans, security test results including penetration tests and audit reports, and external sources, such as vendor information and the National Vulnerability Database.
4 to 6. Rate likelihood and impact, then set the level of risk
For each threat and vulnerability pair, rate how likely the threat is to occur and how likely it is to cause harm if it does, on a scale such as very low to very high. Then rate the impact of a loss of confidentiality, integrity or availability. NIST's example: a phishing attack rated very high for occurrence and moderate for exploiting a human weakness gives an overall likelihood of high, and with a moderate impact, the overall risk is moderate. Use NIST's matrices or your own, as long as you apply them consistently.
7. Document the results
Record every threat and vulnerability pair, its likelihood and impact ratings and the resulting risk level, for example in a risk register. NIST points to a sample report outline in SP 800-30 and suggests sharing the results with leadership, whose review matters for the risk management that follows.
What comes after the analysis?
Risk management, the second required specification: implement security measures sufficient to reduce risks and vulnerabilities to a reasonable and appropriate level. In practice that is a plan with an owner, a target date and a planned control for each risk above your tolerance, ordered by risk level.
Documentation rules apply to both. Under 45 CFR 164.316(b), policies, procedures and required assessments must be kept in written form, which may be electronic, retained for 6 years from creation or from the date they were last in effect, whichever is later, made available to the people who implement them, and reviewed periodically and updated in response to environmental or operational changes that affect the security of ePHI. A new product line, a new cloud provider or a new data flow is such a change.
What could change under the proposed Security Rule update?
HHS proposed an update to the Security Rule on January 6, 2025. According to a summary by the law firm Bradley, the proposal would require written inventories of technology assets that handle ePHI and a map of how ePHI moves through the organization, both updated at least every 12 months, and a more detailed risk analysis. It would also require compliance audits at least every 12 months, vulnerability scans every six months, penetration tests every 12 months, and it would remove the addressable flexibility for measures such as encryption and multi-factor authentication, with limited exceptions. These are proposals. The current rule applies until a final rule replaces it, but an inventory and a data flow map are worth building now because step 1 needs them anyway.
Can you use the HHS Security Risk Assessment Tool?
You can. ONC built the SRA Tool with OCR to help providers conduct the risk assessment the Security Rule requires. Version 3.7 comes as a Windows application and an Excel workbook, and data entered stays on your computer. HealthIT.gov says its target audience is medium and small providers and that it may not suit larger organizations. It also says the survey alone may not identify all risks, and that using the tool is neither required by nor guarantees compliance with federal, state or local laws. A software startup can use it as a checklist, but the system map from step 1 is still yours to build.
What do startups get wrong?
- Treating a cloud provider's BAA as their own risk analysis. The provider's agreement covers its part of the system, not your configuration, code and staff.
- Mapping only the production database and missing logs, analytics, support tools and staging copies.
- Doing it once to answer a customer security questionnaire and never updating it after the product changes.
- Stopping at the analysis without a risk management plan that assigns owners and dates.
- Skipping the written justification for addressable specifications they decided not to implement.
Want a second pair of eyes on yours?
Onix Systems has built software since 2000 and has 370+ engineers. We sign a BAA before anyone on our team sees PHI and run a penetration test before launch, which gives a risk analysis real vulnerability data to work with. If you are preparing your first risk analysis or updating one after a product change, talk to one of our engineers. Our free five-day technical audit ends with a written report on where ePHI lives in your system and which risks to address first.
Sources
- 45 CFR 164.308: administrative safeguards (Cornell LII)
- 45 CFR 164.306: security standards, general rules (Cornell LII)
- 45 CFR 164.316: policies, procedures and documentation requirements (Cornell LII)
- 45 CFR 160.103: definitions, business associate (Cornell LII)
- NIST SP 800-66 Rev. 2: Implementing the HIPAA Security Rule, A Cybersecurity Resource Guide (February 2024)
- HealthIT.gov: Security Risk Assessment Tool
- Nixon Peabody: OCR's sixth HIPAA Risk Analysis Initiative settlement announced (April 2025)
- Bradley: Top 10 takeaways from the new HIPAA Security Rule NPRM (March 2025)