HIPAA penetration testing
HIPAA penetration testing for the systems that handle health data.
ShieldProbe Assess tests the web apps, APIs, networks and servers that handle ePHI, using agreed test accounts and fictional records where possible. The report gives your HIPAA risk analysis tested evidence.
For hospitals, clinics and payers, and for health-tech teams whose customers ask for pentest evidence of the apps and APIs that handle ePHI.
- A named consultant approves each finding before you see it. The gate is enforced in our database.
- Report in 48 hours, then retests of fixed findings for 12 months, under agreed scope, ready access and engagement terms.
- Patient portalTest account A
Roles and permitted actions agreed in advance.
- Application APIAuthorization boundary
Can this account retrieve a record outside its intended access?
- Record serviceFictional record B
Agreed test data only. We keep just the evidence the finding needs.
Use pentest evidence in your HIPAA risk analysis.
HHS guidance treats risk analysis as a foundation for choosing safeguards for electronic protected health information. A penetration test contributes technical evidence; it is not the whole risk-analysis process.
We start from the systems that create, receive, maintain or transmit ePHI, then agree with you which application, API and infrastructure boundaries to test.
Preparation for healthcare systems
- Authorized systems, owners and intended data flows.
- Representative test accounts and fictional records.
- Your teamIdentify systems and data flows.
- AssessTest the authorized scope.
- Risk ownerRecord correction and verification.
Read the framework. See the report.
HHS has proposed Security Rule updates, including testing schedules. They are proposals, not current obligations.
See what you receive.
The illustrative sample report uses fictional data. See what we test across web apps, APIs, networks and servers.
See how we handle scope and data.
Testing supports your assessment. We agree scope and evidence with you and your assessor.
Bring the systems and constraints to the discussion.
Tell us the systems, access and operating limits. We agree evidence handling, contracts and data processing with you before testing.