How to compare proposals fairly
Ask each provider to price the same patient portals, healthcare APIs and supplier access and explain assumptions about roles, access, environments and test windows. Request relevant delivery-team evidence and a report sample. Compare the proposed testing and retesting work before comparing day rates; the lowest number may describe a different engagement.
Evaluate the proposed work and team
Request named delivery roles, relevant experience, availability and evidence supporting any professional claims. Confirm whether subcontractors are involved and how independence or conflicts are managed. This website makes no unverified certification or accreditation claim.
A healthcare estate extends beyond one hospital. We connect identity, referrals, remote care and third-party integrations into a scope that follows the patient-data journey.
Make the proposal specific
- Objectives, systems, roles, scenarios and explicit exclusions.
- Operating windows, safety controls, test data and supplier permissions.
- Named responsibilities for incident escalation and stop decisions.
- Secure evidence transfer, retention, confidentiality and data processing.
- Reporting, remediation discussions, included retests and change control.
Review a sample for substance
Look for actual observations and verifiable acceptance criteria. A scan finding without validation or an attack narrative without scope limits is hard to use. Compare the sample’s technical detail with what the proposal commits to deliver.
Our Healthcare AG sample is clearly fictional and available for this evaluation.
Understand the basis for duration and fees
Systems, roles, business logic, third parties and operational windows determine the work. There is no public fixed-price package or guaranteed completion time. The agreed statement of work should show assumptions, inclusions, retest allowance and how changes affect the schedule.
Confirm the operational plan
Use synthetic patient identities and agreed data cohorts. Name a clinical escalation contact, set request limits and exclude treatment-affecting actions unless separately authorised. Stop immediately if testing encounters unexpected live clinical data or threatens a care workflow.
Prepare a brief before the scoping call
Describe the care service and information boundary you want to assess. Separate patient-facing access, clinical roles and supplier integrations so the test can answer a clear question.
Use the free healthcare penetration testing brief builder to record objectives, assessment areas, constraints and NDA preferences. Review the proposed scope, then send it directly to Atlant Security through the contact form.
