HIPAA and penetration testing: what the rule says

What the HIPAA Security Rule says about testing, and how a penetration test supports your risk analysis.

A laptop on a desk

What the Security Rule requires

The HIPAA Security Rule asks covered entities and business associates to analyse the risks to electronic protected health information and to evaluate their safeguards periodically. The text of the current rule does not name penetration testing, but a test is a common way to show that technical safeguards work in practice.

HHS has proposed changes to the Security Rule that would be more specific about testing. Check the current status of that proposal before you rely on it.

Where testing fits

Penetration testing gives evidence for two things auditors and customers ask about:

  • Risk analysis: which systems that handle patient data can actually be reached, and how.
  • Technical evaluation: whether access controls, authentication and transmission safeguards hold up against a real attempt.

What health-data products should cover

Scope what handles patient data, not only the public website:

  • Patient portals and mobile apps, including sign-in, password reset and record access.
  • APIs and integrations with labs, payers, EHR systems and billing.
  • Role models: whether one user can reach another patient’s or another clinic’s records.
  • Cloud storage, backups and logging for files that contain PHI.

Business associates and customer reviews

Healthcare customers often send security questionnaires to vendors that handle PHI, and many ask for a recent independent test. Keep the report summary ready and share the full report only under a confidentiality agreement.

Sources

General guidance, not legal, audit or compliance advice. Confirm requirements with your auditor or assessor.

Ready to test?

Tell us what needs testing and by when.

You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.