WORKING RESOURCE / SCOPE & PROCUREMENT

Build a hospital pentest scoping brief

Start with the hospital services that must remain available and the boundaries you need to assess. Make exclusions, vendor dependencies and clinical stop authority visible before technical scope expands.

Define the objective.
Set the boundaries.
Leave with a working brief.

No signup required
Copy, download or print
Your draft stays in this page

Keep it high level. Do not enter patient details or live device identifiers. Avoid active clinical operations until the specific test method and permissions have been agreed.

Your choices are processed in your browser. They are not sent, saved in browser storage or shared with AI. Copy or download your brief before leaving.

01 The decision you need

Assessment objective

Operational setting

Direct testing of medical devices is a separate scope decision requiring the relevant clinical and vendor approvals. It is never implied by a network test.

02 The assessment boundary

Choose the areas you want to discuss. Final coverage is agreed during scoping.

Clinical application and identity boundariesWard, administration and clinical network zonesRemote vendor supportMedical-device management boundariesRecovery systems and downtime dependencies

Proposed environment

Operating constraints (optional)

For example: clinical blackout windows, no active device scanning, vendor-supervised sessions or agreed downtime escalation.

03 Timing and permissions

Indicative timing

Supplier permissions

NDA preference

YOUR WORKING BRIEF

Ready for a better
scoping conversation.

0 of 7 planning points captured

Review and copy your draft

Hospital penetration testing — initial scoping brief
DRAFT FOR DISCUSSION · not authorisation to test

Assessment objective: To be agreed
Primary context: To be agreed
Environment: To be agreed
Indicative timing: To be agreed
Supplier permissions: To be agreed
NDA preference: To be agreed
Assessment areas: To be agreed
Operating constraints: To be discussed

Questions to resolve:
- Assessment areas
- Assessment objective
- Primary context
- Environment
- Indicative timing
- Supplier permissions
- NDA preference

Next step: agree scope, named owners, safeguards, deliverables and commercial terms.
Do not include credentials, patient/customer records or confidential technical evidence.

Copy the brief into your enquiry message, or email it to sales@hospitalpentest.com. Nothing is sent automatically.

WHAT TO INCLUDE / Hospital penetration testing

Scope choices that change the test.

Assessment area	What to describe	What useful evidence answers
Clinical networks	Map the permitted zones and pathways between hospital services.	Allowed and denied paths tied to the identity and source context used.
Vendor and device boundaries	Identify owners, maintenance arrangements and explicit device exclusions.	Evidence about authorised management access without assuming active device testing.
Continuity and recovery	Identify downtime processes, recovery roles and independent stop authority.	The tested management boundary, untested dependencies and clear handover actions.

BEFORE THE SCOPING CALL

Bring the right context.

Clinical and technical owners for every included zone
Device exclusions and supplier authorisations
A practical stop procedure with clinical decision makers
Test-data, rollback and continuity arrangements

Open the full readiness checklist ↗

THE NEXT DECISION

Agree the safety boundary before the test boundary

Bring clinical operations, infrastructure owners and suppliers into the scoping decision. Record who can stop activity and what evidence is safe to collect.

Coverage, environments, role combinations, supplier coordination and retesting affect effort. A brief helps expose those assumptions; it is not a price or delivery commitment.

See how the evidence is reported ↗

Method and source references

Read the scope guide · Evaluate a provider · How we publish our guidance