Skip to content

Compliance

HIPAA
Penetration Testing

HIPAA penetration testing covers the systems that store, process, or transmit ePHI and maps each finding to the Security Rule, as evidence for your risk analysis.

Component tests from $4,200, free retest. See all pricing →

Get a fixed quote

Reply the same day

Senior certified testers, manual-first185+ years combined experienceOnboarding within 24 hoursFree retest includedOur methodology

When you need it

When you need HIPAA penetration testing

The situations that bring teams to this engagement, and where it fits alongside the rest of your program.

  • Your annual risk analysis is due and the technical evaluation behind it needs more than a policy review.
  • A hospital, health system, or payer customer asked for third-party testing evidence in the business associate agreement.
  • You launched a patient portal, a telehealth product, or a mobile app that handles ePHI on devices you do not control.
  • An OCR inquiry, a breach at a peer, or a cyber-insurance renewal put “when were you last tested?” on the agenda.
  • You are preparing for the proposed Security Rule update, which would require annual penetration testing and scanning every six months if finalized.

The requirement

Does HIPAA require penetration testing? The current rule and the proposed update

The current Security Rule

Requires a risk analysis, risk management, and a periodic technical and nontechnical evaluation of safeguards, alongside the technical safeguards of §164.312. It does not name a testing method. A penetration test is the accepted way to evidence the evaluation and to feed real findings into the risk analysis, and OCR resolution agreements routinely cite the absence of an accurate and thorough risk analysis, which a test feeds directly.

The proposed update

On January 6, 2025, HHS published a proposed rule to strengthen the Security Rule. Among other changes it would require penetration testing at least every twelve months and vulnerability scanning at least every six months for all systems that create, receive, maintain, or transmit ePHI, a technology asset inventory and network map updated at least annually, and the end of the distinction between “required” and “addressable” safeguards, so encryption and multi-factor authentication would become required. As of November 2026 the rule is still proposed, not final, with final action projected for July 2027, and the details may change. Organizations that adopt the proposed cadence now are simply doing what is already common practice.

The proposal is not law yet, so plan around the current rule and budget for the proposed cadence: one penetration test a year and a vulnerability scan every six months. Our HIPAA compliance checklist covers the rest of the Security Rule.

The current rule

What the Security Rule requires today, provision by provision

Four provisions of 45 CFR Part 164 do the work. None of them says “penetration test,” and none is easy to evidence without one.

What it requires

Risk analysis, §164.308(a)(1)(ii)(A)
An accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI. This is the provision OCR cites most often.
Risk management, §164.308(a)(1)(ii)(B)
Security measures sufficient to reduce those risks to a reasonable and appropriate level.
Evaluation, §164.308(a)(8)
A periodic technical and nontechnical evaluation of how well your policies and procedures meet the Security Rule.
Technical safeguards, §164.312
Access control, audit controls, integrity, person or entity authentication, and transmission security.

What the penetration test provides

Risk analysis, §164.308(a)(1)(ii)(A)
Documented, exploitable vulnerabilities in the systems that hold ePHI, the most direct evidence that the analysis was thorough.
Risk management, §164.308(a)(1)(ii)(B)
Prioritized findings with remediation guidance, and a free retest showing which fixes closed them.
Evaluation, §164.308(a)(8)
The technical evaluation of ePHI systems, which in practice is a penetration test or a vulnerability assessment.
Technical safeguards, §164.312
Each finding mapped to the safeguard it affects, so it drops straight into the risk analysis.

Nothing in the current rule sets a testing frequency: “periodic” and “reasonable and appropriate” are the standards, judged against your risk analysis and the size of your organization. HHS guidance on the risk analysis makes identifying and documenting vulnerabilities a required element, and NIST SP 800-66, the implementation guide HHS points to, names penetration testing among the methods.

How they fit

Risk analysis vs penetration test

The risk analysis is the document OCR asks for first in every investigation. It inventories where ePHI lives, identifies threats and vulnerabilities, and rates the risk. A penetration test is the strongest input it can have: instead of estimating whether a patient portal could expose records, the test shows whether it did, with evidence. The findings become the vulnerabilities in the analysis, the exploited paths become the likelihood ratings, and the retest becomes the record of remediation. We write the report so it drops into that structure, and our security risk assessment guide shows where each piece lands.

What we assess

What your HIPAA test covers

We test the systems that actually touch ePHI and map every finding to the HIPAA Security Rule, giving your compliance officer evidence, not a generic scan.

Access & Authentication

Technical safeguards controlling who can reach electronic PHI and how.

We test for

  • Unique user identification
  • Authentication and MFA
  • Access authorization and least privilege
  • Automatic logoff

Transmission & Encryption

How ePHI is protected as it moves across and rests within your systems.

We test for

  • Encryption in transit and at rest
  • Secure transmission controls
  • Integrity verification
  • Key management

Audit & Integrity Controls

Whether activity on systems holding ePHI is logged and data is protected from tampering.

We test for

  • Audit logging and review
  • Integrity controls
  • Monitoring and alerting
  • Tamper detection

Systems Handling ePHI

The applications and infrastructure that store, process, or transmit ePHI.

We test for

  • ePHI system inventory
  • Application and infrastructure testing
  • Vulnerability and patch status
  • Business associate systems

Scope

Healthcare penetration testing scope: follow the ePHI

Penetration testing for healthcare starts with one question: where does electronic protected health information live, move, and rest? For most healthcare organizations that means six groups of systems.

Clinical systems

The EHR or EMR platform, PACS and imaging, laboratory systems, and the interfaces between them. HL7 v2 interfaces were designed for trusted internal networks and often carry no authentication or encryption; FHIR APIs bring standard API risks, such as broken object-level authorization, to clinical data.

Patient-facing systems

Portals, telehealth, scheduling, and payment flows. Internet-facing, handling ePHI, and usually the highest-value target in a healthcare estate. Tested as web, mobile, and API engagements.

Infrastructure

The internal network, segmentation between clinical and corporate VLANs, Active Directory, remote access, and the cloud environments hosting any of the above.

Identities and email

Single sign-on, clinician and vendor accounts, and the mailboxes that hold ePHI in attachments and threads. Email accounts were the breach location in about a quarter of large healthcare breaches in 2025, so a phishing test belongs in scope, and so does a Microsoft 365 security assessment if mail runs there.

Business associates

Anything a vendor operates on your behalf that touches ePHI. Their systems cannot be tested without written authorization, but their exposure is your regulatory problem, which is why BAAs and vendor assessments matter.

Medical devices

Infusion pumps, monitors, and imaging equipment. Tested as a separate hardware engagement with clinical safety rules, never during patient use.

A typical first engagement for a covered entity is an external network test, an internal network test, and a web application test of the patient portal, with the report mapped to §164.308 and §164.312.

Patient safety

Testing without disrupting care

A test that degrades a clinical system is not an inconvenience, it is a patient-safety incident. Healthcare engagements manage that risk explicitly, and a firm that will not discuss these rules in detail during scoping has not tested healthcare environments before. The same rules govern hospital penetration testing in Boston and every other city we work in.

  • Test in a staging or mirrored environment wherever a production system supports patient care directly. For EHRs this is standard practice.
  • Agree exclusion rules in writing: no denial-of-service testing, no automated fuzzing of clinical devices, no aggressive scanning of biomedical VLANs during operating hours.
  • Schedule around clinical operations, with a named clinical contact reachable throughout the engagement.
  • Define a stop condition and an escalation path before testing begins, so any sign of instability halts work immediately.
  • Report critical findings on discovery, not at the end. If a tester reaches ePHI on day one, you know on day one.

Typical findings

What a healthcare penetration test typically finds

Across healthcare engagements, from hospital penetration testing in Philadelphia to small practices, the recurring themes are consistent, and most of them are a HIPAA breach in a single request or a single phished workstation.

  • Flat networks: clinical devices, workstations, and corporate systems on the same segment, so one phished workstation reaches imaging equipment.
  • Broken access control in patient portals: a record identifier in a URL or API call that returns another patient’s data when changed.
  • Unauthenticated HL7 interfaces reachable from the general network.
  • Default and shared credentials on devices and clinical applications, often documented in vendor manuals that are public.
  • Legacy protocols and unsupported operating systems on biomedical equipment that the vendor certified years ago.
  • Excessive access rights: staff and service accounts able to reach far more patient data than their role requires.
  • Cloud storage exposure: backups, imaging archives, or exports sitting in misconfigured buckets.

Who is covered

Covered entities vs business associates

Covered entities

Providers, health plans, and clearinghouses. Scope typically centers on the EHR and its integrations, patient portals, clinical and billing applications, the internal network that connects them, and the perimeter around it all. Testing is mapped to the technical safeguards and to your risk analysis. New York general hospitals also answer to 10 NYCRR 405.46, which requires an annual penetration test.

Business associates

Health-tech vendors, billing companies, cloud hosts, and anyone else handling ePHI on a covered entity’s behalf. Directly liable under the Security Rule since HITECH, and increasingly required by BAA language to show independent testing. Scope is the product and infrastructure that touch the customer’s ePHI, and the report is written to satisfy the customer’s security review as well as your own program. When a health-system customer asks for HITRUST instead, see HITRUST penetration testing.

Medical device makers

Manufacturers are usually not covered entities, but hospitals ask for device testing evidence during procurement and FDA premarket cybersecurity guidance expects it. Devices are tested as a separate hardware engagement, from $5,200. Our guide to medical device penetration testing covers how to test safely.

Enforcement

How OCR enforces the current rule

The enforcement record is the clearest statement of what “required” means in practice. The pattern in OCR’s resolution agreements is consistent: a breach through a technical weakness, a request for the risk analysis, and a risk analysis that either did not exist or did not cover the system that was breached.

  • OCR closed 21 enforcement actions in 2025 and collected $8,330,066 in penalties. 76% of those actions cited a failure to conduct an accurate and thorough risk analysis.
  • 805 breaches of 500 or more records were reported for 2025, affecting more than 138.5 million people. Hacking and IT incidents caused more than 80% of them, up from 49% in 2019.
  • Network servers were the location of 61.5% of large breaches and compromised email accounts 24.9%. Business associates accounted for 35.8% of breaches, including most of the largest.
  • State attorneys general enforce alongside OCR. New York fined OrthopedicsNY $500,000 in 2025 over a breach affecting 656,086 people.

A penetration test report dated before a breach, covering the system that was breached, is the document that changes that conversation. Figures are from the HIPAA Journal’s 2025 Healthcare Data Breach Report and its healthcare data breach statistics. Our data breach statistics page has the full healthcare set.

Healthcare threats

Healthcare threats we test for

Healthcare has carried the highest breach costs of any industry in IBM’s annual study for over a decade. These are the attack paths behind those numbers, and the tests that cover them.

Ransomware and the internal network

Most healthcare ransomware starts with one compromised workstation or vendor connection and spreads through a flat clinical network. An internal penetration test shows how far it would get and whether segmentation around clinical systems holds, and a ransomware readiness assessment adds whether backups could be reached and recovery would work.

Patient portals and mobile apps

Authorization flaws that let one patient see another’s records are the most common finding in the applications we test. Web application and mobile testing covers the portal, the app, and the APIs behind them.

Medical and connected devices

Infusion pumps, imaging equipment, and monitoring devices carry firmware and network interfaces nobody patches. Hardware and IoT testing covers the device; the internal test covers the network it sits on.

EHR integrations and partners

HL7, FHIR, and vendor APIs move ePHI between systems constantly. API penetration testing checks the authentication and authorization on every interface, including the ones partners use.

The report

What a HIPAA penetration test report has to contain

OCR, an auditor, and a customer’s security review all read the same report. It should:

  • State the scope in terms of ePHI systems, so it can be matched to the risk analysis.
  • Describe the methodology. We follow PTES and the OWASP testing guides.
  • List every finding with its severity, the §164.308 administrative or §164.312 technical safeguard it affects, and the remediation.
  • Include the retest, showing which findings were closed.
  • Carry a one-page attestation letter summarizing all of the above, which you can share with customers without exposing the technical detail.

The full structure is on our sample report page. Keep the report and the retest: §164.316(b)(2)(i) requires Security Rule documentation to be kept for six years.

Methodology

How we test

Full methodology →

Every engagement follows the Penetration Testing Execution Standard and the relevant OWASP guides.

These are the phases your compliance test runs through.

  1. 01

    Scope the boundary

    The systems your framework actually covers, and nothing you would pay to test twice.

  2. 02

    Test

    The component penetration tests run to PTES and OWASP standards by senior testers.

  3. 03

    Map to controls

    Every finding tied to the requirement or control it evidences.

  4. 04

    Report for the auditor

    Evidence formatted the way your assessor, examiner, or QSA expects to read it.

  5. 05

    Fix & retest

    A free retest so the audit shows closed findings, not open ones.

How it works

How your engagement runs

From scope through the final retest, your team stays in the loop at every step, with findings tracked live in our platform.

  1. 01

    Scope ePHI

    We identify the systems that store, process, or transmit electronic PHI.

  2. 02

    Test safeguards

    We test access, transmission, and audit controls against the Security Rule.

  3. 03

    Mapped report

    Findings mapped to the Security Rule as evidence for your compliance team.

  4. 04

    Fix & retest

    Fix the findings, then a free retest that strengthens your risk analysis.

Cost

What a HIPAA penetration test costs

A HIPAA test is priced from the component tests your ePHI systems need, each with a published fixed starting price. A covered entity typically starts with the external network, the internal network, and the patient portal; a business associate scopes the product and infrastructure that touch its customers’ ePHI.

What it covers

External network
The internet-facing perimeter around systems that handle ePHI
Internal network
The clinical and corporate network, segmentation, and ransomware blast radius
Web application
Patient portals, clinical applications, and billing systems that display or process ePHI
API
FHIR, HL7, and vendor integrations that transmit ePHI between systems
Hardware and IoT
Medical and monitoring devices, tested as a separate hardware engagement
Validated vulnerability scan
The six-month scanning cadence the proposed rule would require

Starting price

External network
From $4,200
Internal network
From $6,000
Web application
From $5,200
API
From $4,000
Hardware and IoT
From $5,200
Validated vulnerability scan
From $1,500 per scan for up to 250 devices

Each price is fixed in writing before work begins. Penetration tests include the Security Rule mapping, an attestation letter, and a free retest. Add up your own scope with the pricing calculator.

Proof

Proof in the field

Every engagement is confidential, so the work below is anonymized to sector and engagement type.

All case studies →

Free

Retest on every penetration test

185+

Years combined experience

14

Senior in-house specialists

24h

Onboarding after signing

Healthcare · Imaging

Organization-Wide Phishing Simulation

High risk

Over half the workforce took the bait: roughly a third clicked the link and a quarter entered their credentials on the simulated capture page.

Outcome. Quantified credential-compromise risk across the whole organization and delivered a prioritized program of role-targeted awareness training, recurring simulations, and a faster, simpler reporting workflow.

11,800+

Employees targeted

53%

Phish-prone

24%

Entered credentials

Read the case study

Fintech · Payments

Web Application Penetration Test

High risk

Critical: a remote code execution flaw in the application’s web framework that could have given an attacker full control of the server. We escalated it to the development team while the test was still running.

Outcome. The critical RCE was reported and remediated during the engagement via an emergency framework upgrade, which also closed a high-severity server-side request forgery flaw, and the remaining findings were retested to confirmation.

1

Critical (RCE)

Mid-test

Critical remediated

2

High

Read the case study

In their words

What clients say

From the technical and business leaders who hired us, about the work and the report they got.

See who we test for 

We reached out to Invadel after our infrastructure provider was breached and we needed to ensure our new footprint was as secure as possible. Invadel was able to jump in and quickly get things moving. They found some open attack surfaces that we patched immediately. Our VAPT report was extremely helpful and the deliverables were perfect. I’ve worked with many security agencies in my time and Invadel tops the list.

Dylan Stamat, CTO at Booster SEO

Dylan Stamat

CTO, Booster SEO

SEO and marketing software

Booster SEO

FAQ

Frequently asked questions

What teams most often ask before HIPAA testing.

Still have questions? 
01Does HIPAA require a penetration test?

Under the current Security Rule, no method is prescribed: it requires a risk analysis (§164.308(a)(1)(ii)(A)) and a periodic technical evaluation of your safeguards (§164.308(a)(8)), and a penetration test is the most widely accepted way to evidence both. A proposed update to the Security Rule, published in January 2025 and not yet final, would make annual penetration testing and vulnerability scanning every six months explicit requirements for covered entities and business associates.

02What systems do you test?

The systems that store, process, or transmit electronic PHI, including in-scope applications, infrastructure, and business associate environments where applicable. We confirm scope with you before testing. The non-technical side of the rule is covered in our guide to HIPAA administrative and physical safeguards.

03We are a business associate, not a covered entity. Do we still need this?

Yes. Business associates are directly subject to the HIPAA Security Rule and must protect the ePHI they handle on behalf of covered entities, and your customers increasingly require evidence of testing in their business associate agreements. We scope the test to the systems where you store or process their ePHI.

04Will this support our risk analysis?

Yes. We map findings to the Security Rule's technical safeguards and provide documentation your compliance officer can use to support the required risk analysis.

05How much does a HIPAA penetration test cost?

A HIPAA test is scoped to the systems that handle ePHI, usually a web application and/or network test (from $5,200 and $4,200), quoted as a fixed price after scoping, with a free retest. An API test of FHIR or vendor integrations starts at $4,000 and an internal network test at $6,000. Starting prices for every service are on our pricing page, and our guide to HIPAA compliance cost covers the rest of the program.

06How often should we run HIPAA penetration testing?

Annually at a minimum, and after any significant change to the systems that handle ePHI: a new patient portal, an EHR migration, a new business associate integration, or a cloud move. That cadence is common practice today and is what the proposed Security Rule update would make explicit. Many covered entities pair the annual test with vulnerability scanning every six months, which is the other cadence the proposal names.

07Would vulnerability scans alone satisfy the proposed rule?

No. The proposal treats scanning and penetration testing as separate requirements on separate cadences: automated vulnerability scans at least every six months and a penetration test at least every twelve months. Scans find known weaknesses; the penetration test proves which ones expose ePHI. Our vulnerability scanning service covers the first, and it is included in a testing program alongside the annual test.

08What are the HIPAA penetration testing requirements in practice?

Four things, whatever the rule’s wording: scope that follows the ePHI (every system that creates, receives, maintains, or transmits it, including business associate connections), a test that does not endanger care delivery, findings that feed the risk analysis with evidence rather than assumptions, and a record that remediation was verified. Auditors, OCR investigators, cyber insurers, and hospital procurement teams all look for the same four, and the report is built around them. Our HIPAA security risk assessment guide shows how the findings feed the risk analysis.

09Will the tester sign a Business Associate Agreement?

Raise it during scoping. Any tester who may be exposed to ePHI while testing a live system should be covered by a BAA, and the engagement agreement sets out how test data and any incidental ePHI are handled, stored encrypted, and destroyed. Where a staging environment with synthetic data is available, we test there instead and the exposure question does not arise. Our list of healthcare penetration testing companies covers the other questions to ask any vendor.

10Do you test medical devices and clinical equipment?

Yes, as a separate scope. Infusion pumps, imaging equipment, and monitoring devices are tested as hardware and IoT engagements: firmware, hardware interfaces, wireless protocols, and the device’s backend communications, never fuzzed while attached to a patient. FDA premarket cybersecurity guidance expects manufacturers to show this kind of testing, and health systems increasingly ask for it during procurement. Our guide to medical device penetration testing covers how to do it safely.

11Does HITRUST or SOC 2 cover HIPAA penetration testing?

Both expect a penetration test in their evidence, and both map to the HIPAA safeguards, so one test reported against all three is the efficient route. Tell us every framework you hold or are pursuing during scoping and the report is written against all of them. See HITRUST penetration testing, SOC 2 penetration testing, and our comparison of HITRUST vs SOC 2.

12Does a small medical practice need a penetration test under HIPAA?

The Security Rule applies to every covered entity whatever its size, and it is flexible: what is reasonable and appropriate depends on your size, complexity, and risks. A small practice still owes a risk analysis and a periodic technical evaluation, and a small-scope test is a proportionate way to evidence both. That is typically an external test from $4,200, plus wireless penetration testing for clinics where the office Wi-Fi reaches systems that hold ePHI.

13Do state laws add testing duties on top of HIPAA?

Some do. New York general hospitals owe an annual penetration test under 10 NYCRR 405.46. State data security laws such as the NY SHIELD Act require reasonable safeguards for residents’ private information, and state attorneys general can enforce HIPAA alongside OCR. A test scoped to the systems that hold ePHI produces evidence you can use for each of them.

Ready to test your defenses?

Talk to our team about what your HIPAA compliance requires.

Prefer the full scoping questionnaire? 

Get a Fixed-Scope Quote

Tell us what you need tested. We reply the same day.

Get a quick proposal

We are online