Exploit-Forge
Health Insurance Portability and Accountability Act

HIPAA penetration testing

Security assessments that validate the administrative, physical, and technical safeguards protecting electronic protected health information (ePHI).

Key facts

Pentest recommended
Pentest required?
Not by name. Supports the Security Rule’s risk analysis and evaluation standards.
Applies to
US covered entities and their business associates handling ePHI
Enforced by
US Department of Health and Human Services (OCR)
Typical cadence
Annually, and after significant changes

What is HIPAA?

The HIPAA Security Rule requires covered entities and their business associates to protect the confidentiality, integrity, and availability of electronic protected health information through administrative, physical, and technical safeguards.

Where pentesting fits

How our testing supports HIPAA

HIPAA doesn’t name penetration testing, but testing is one of the most direct ways to meet these Security Rule standards:

§164.308(a)(1)

Risk analysis

Gives your risk analysis real evidence of vulnerabilities that threaten ePHI.

§164.308(a)(8)

Evaluation

A periodic technical evaluation of whether your safeguards work.

§164.312(a)

Access control

Tests authentication, authorization, and least-privilege access to ePHI.

§164.312(b)

Audit controls

Checks that access to ePHI is logged and detectable.

§164.312(e)

Transmission security

Verifies ePHI is encrypted and protected in transit.

Scope

What we test

Patient-facing apps

Portals and mobile apps, with a focus on authentication and authorization.

APIs and integrations

The interfaces that move health data between systems and partners.

Cloud and infrastructure

Logging, encryption, and access controls around systems holding ePHI.

Retesting

Confirmation that risks to ePHI are mitigated after you fix them.

What you get

  • Findings mapped to the controls and requirements above
  • Evidence for every finding: requests, payloads, and screenshots
  • Executive summary for leadership and auditors
  • Developer-ready fixes, then retesting to confirm they hold

How often to test

  • At least annually as part of your risk analysis, and after significant changes to systems that store or transmit ePHI.

Common questions

Does HIPAA require penetration testing?

Not by name. But the Security Rule requires an accurate risk analysis and periodic technical evaluations, and a penetration test provides evidence for both.

Need HIPAA-aligned security testing?

Tell us about your audit timeline and scope, and get a fast, pragmatic proposal.