Key takeaways
- The HIPAA Security Rule does not use the words “penetration test” today.
- It does require a risk analysis and a periodic technical evaluation, and a penetration test is the common way to meet the technical part.
- In January 2025, HHS proposed requiring a penetration test every 12 months and vulnerability scans every six months. The proposal is not final.
- Health systems, payers, and enterprise customers often ask digital health companies for a current report regardless of the rule.
What the Security Rule requires today
Two parts of the current rule matter here.
The first is the risk analysis. A covered entity or business associate must assess the risks to the confidentiality, integrity, and availability of the electronic protected health information it holds (45 CFR 164.308(a)(1)).
The second is the evaluation. The organization must perform a periodic technical and nontechnical evaluation of how well its safeguards meet the rule, and repeat it when its environment or operations change (45 CFR 164.308(a)(8)).
Neither part names a method. A penetration test is how most organizations produce the technical evidence, because it shows whether a control stops an attacker and not only whether the control exists.
What HHS has proposed
On January 6, 2025, HHS published a proposal to rewrite the Security Rule. Among other changes, it would require:
- A penetration test at least once every 12 months.
- Vulnerability scanning at least every six months.
- Multifactor authentication and encryption of patient data, with limited exceptions.
- A written inventory of technology assets and a map of how patient data moves through them.
HHS had targeted 2026 for a final rule. It has since moved final action to July 2027 at the earliest, and the current rule stays in force until a final rule replaces it. The proposal still shows where regulators expect the standard to go.
Why most digital health companies test anyway
For a digital health company, the regulator is rarely the first to ask. The request usually comes from a customer.
A health system or payer that is about to send you patient data will run a security review. It will ask for a penetration test report from an independent firm, usually one completed in the last year. SOC 2 auditors and HITRUST assessors ask for the same evidence. The practical standard is already an annual test, whatever the final rule says.
What a HIPAA penetration test should cover
Scope follows the patient data. A useful test covers every route to it.
- Web and mobile applications. Patient portals, telehealth apps, and clinician tools, tested against OWASP ASVS and MASVS. The flaws that expose patient records are usually in authorization, where one user can reach another user’s data.
- APIs and integrations. FHIR and HL7 interfaces, partner connections, and the internal services behind the app.
- Cloud environment. Identity policies, storage settings, and logging in AWS, Azure, or Google Cloud.
- External and internal networks. What an attacker can reach from the internet, and how far a compromised account can move.
- Connected devices. Where clinical or medical devices are in scope, tested in a way that puts nothing in a clinical environment at risk.
What the report should give you
A scanner export does not satisfy a reviewer and does not help your engineers. The report should state which findings an attacker could exploit in your environment, what each one exposes, and what to fix first. Each finding should come with evidence of how it was exploited, such as screenshots, so your engineers can confirm it. The report should also include a summary that a partner’s security team can read without the technical detail.
If a reviewer wants proof that findings were fixed, a retest adds an addendum to the report that shows what was tested again and what was observed.
How ForgePath helps
We test healthcare and digital health applications, cloud environments, networks, and connected devices, and we write reports that partners and auditors accept. Each finding includes evidence of how we exploited it, with screenshots. Retesting is available as an add on.
When the test is part of a larger review, we also map your controls to the partner’s questionnaire and prepare the evidence it asks for.
See how we work with healthcare and digital health companies, or read about HIPAA readiness, web application penetration testing, and our penetration test for FOLX Health.
Frequently asked questions
Is a vulnerability scan enough for HIPAA?
A scan finds known weaknesses. It does not show whether an attacker can use them to reach patient data, and it rarely finds access control flaws in an application. Reviewers generally ask for both.
Do business associates need a penetration test?
The Security Rule applies to business associates directly, so the same risk analysis and evaluation duties apply. Most business associates are also asked for a report by the covered entities they serve.
How often should we test?
Once a year is the common expectation from partners and auditors, and it matches the proposed rule. Test again after a major release or a change in architecture.
Sources
- HIPAA Security Rule, 45 CFR Part 164 Subpart C
- HHS proposal, “HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information”, Federal Register, January 6, 2025
- Delay of final action to July 2027

