Who we serve / Healthtech

    Pen testing for healthtech and ePHI-adjacent platforms.

    HIPAA-aligned scoping, patient-portal auth boundaries, FHIR and HL7 endpoint abuse, and third-party EHR integration risk. Evidence that satisfies both your Security Rule Risk Analysis and the diligence questionnaires health systems send before they sign.
    ePHI boundaryPatient portalAPI layerRecord storeExport routeUnscoped bulkEvidence · redactedHIPAA §164.308(a)(8)FHIR · HL7 · Portal

    Recurring finding

    In healthtech, the finding we surface most often is a misconfigured endpoint returning identifiable records without auth. It's also the finding that immediately reaches a regulator once it becomes an incident.

    Anonymous data exfiltration

    critical

    Misconfigured access controls let unauthenticated visitors read entire customer and lead databases — names, emails, PII — straight from the API.

    Why it mattersOne forgotten endpoint becomes a regulator-reportable breach.

    What we test for Healthtech

    Patient data surfaces, portals, and the integration seams attackers pivot through.

    • HIPAA-aligned scoping under §164.308 Risk Analysis and Evaluation

    • Patient-portal authentication and session boundary testing

    • FHIR and HL7 endpoint abuse and authorization bypass

    • Third-party EHR and clearinghouse integration risk

    • Business Associate boundary crossings and BAA-scope surfaces

    • PHI-adjacent API surfaces (scheduling, billing, messaging)

    • Telehealth session isolation and recording protections

    • Cloud storage exposure of PHI (S3, GCS, blob)

    RelatedHIPAA pen testing →

    How it shows up

    The archetype, anonymized.

    In healthtech, the finding we surface most often is a misconfigured endpoint returning identifiable records without auth. It's also the finding that immediately reaches a regulator once it becomes an incident.

    Healthtech attack path04 hops
    1. 01 · Entry

      Patient portal session handling

    2. 02 · Identity

      Weak object scoping on chart lookups

    3. 03 · Breadth

      Cross-tenant record enumeration

    4. 04 · Impact

      Bulk PHI retrieval over the API

    OutcomeA reportable PHI breach without a single malware artifact on disk.

    See all recurring findings →

    From the register

    What a healthtech report actually lists.

    Healthtech — findings excerpt05 rows
    Filter
    • PT-01

      Unauthenticated PHI retrieval via record ID enumeration

      Patient API

      critical
    • PT-02

      Audit log omits read access to clinical records

      Logging

      high
    • PT-03

      HL7 / FHIR interface trusts unvalidated org identifiers

      Integration

      high
    • PT-04

      Legacy VPN allows access to clinical subnet

      Internal network

      medium
    • PT-05

      Session persists after password change

      Authentication

      low

    Healthtech FAQ

    Frequently asked.

    No. We can test against de-identified data, synthetic PHI, or a scrubbed staging environment. When live PHI is unavoidable, we sign a BAA, minimize access, and destroy any incidental PHI captured during proof-of-concept — with a written evidence-of-destruction attestation for your Risk Analysis file.

    Yes. A signed Business Associate Agreement is a standard part of any engagement where PHI could be accessed, incidentally or otherwise. We use HHS-conforming BAA terms and can review your template first.

    Yes. We map findings to the HITRUST CSF control categories your assessor uses, in addition to the HIPAA Security Rule. If you're preparing for a HITRUST validated assessment, tell us during scoping and we produce evidence in the format your external assessor already accepts.

    Next step

    Scope a healthtech pen test.

    Thirty-minute scoping call. Fixed-scope quote within one business day. BAA signed before any access, and a report ready for your Risk Analysis file.

    Request a pen test scope call →