A hospital campus has three doors an attacker actually needs

Reception, ward, server room. These three places explain how hospitals get attacked: through people on shift work, through networked medical devices and through a hospital information system that has grown over the years.

  • ICU, operating theatres and patient rooms stay off-limits
  • Medical devices are never actively attacked
  • Report with mapping to the B3S
1 January 2022 Section 75c SGB V in force
26 March 2024 Section 391 SGB V replaces 75c
30,000 cases per year: KRITIS from here

The floor plan: how an attack moves through your hospital

The route we take most often in our hospital assessments: from the most open point of the building all the way to the patient records and the billing system.

  • What an attacker finds
  • What we test
1

Reception

Open door, no time

Outside contractors walk through the building unannounced, and reception is unattended at times.

Access attempts posing as a technician or delivery driver, tailgating at side entrances, unfamiliar badges.

2

Ward

Devices at the bedside, staff under strain

Networked medical devices at the bedside, often maintained by the manufacturer. Staff on shift work with no time to check.

Phishing and pretexting tailored to shift work, logged-in ward workstations, remote maintenance of the devices.

3

Corridor and network

The segmentation question Attacker's route

Whether a compromised machine stays a local problem is decided by how the networks are separated.

Network segmentation, permissions, Active Directory. How far does an attacker get from a ward network?

4

Server room and HIS

Records, billing, interfaces

The HIS has grown over the years and has many interfaces to third-party systems. Each of them is a way in.

Interfaces, remote maintenance, access to the server room, permissions concept. Systems with direct patient impact passive only.

We never actively attack medical devices during live operation; we test their network connectivity and remote maintenance access. The ICU, operating theatres and anything with direct patient impact are off-limits, set down in writing before the first step.

How a hospital pentest runs

  1. Scope with patient safety in mind

    Together we define what gets actively tested and what is only analysed passively. For anything with direct patient impact: when in doubt, test more cautiously.

  2. Testing with an emergency contact

    Network scans and manual testing within the agreed scope. If anything unexpected affects production systems, we stop immediately.

  3. Report with B3S mapping

    Every finding rated by severity, exploitability and impact on hospital operations, with a management summary.

Test matrix: our modules by B3S topic area

Section 391 SGB V names a BSI-approved industry standard, in practice the DKG's B3S, as a route to the state of the art. Which module covers which topic area, and where does patient impact limit the test?

Topic area Our module Limit set by patient impact
Network and systems securityInfrastructure PentestProduction systems with patient impact passive only
Access and permissions managementActive Directory PentestNo changes to production accounts
Physical security of server rooms and wardsPhysical PentestICU, operating theatres and patient rooms off-limits
Staff awareness and behaviourSocial Engineering and Phishing SimulationNo pretext referring to specific patients
Medical and networked devicesCustom assessmentThe devices themselves are never actively attacked

Whether an area counts as met is decided by your B3S review, not our report. We deliver the technical findings and their classification.

What happened in four years

  1. 1 January 2022

    Section 75c SGB V comes into force

    State-of-the-art measures; since 26 March 2024 in Section 391 SGB V, without the two-year rule. The B3S is one named route.

  2. September 2024

    Wertachkliniken: a hospital without IT

    Ransomware attack on the Wertachklinik group, based on public reporting.

  3. March 2025

    SiKIS documents vulnerabilities in HIS

    Commissioned by the BSI, Fraunhofer SIT examined hospital information systems. The finding concerns the class of systems.

  4. 6 December 2025

    NIS2 implementation act in force

    The BSI Act was recast. For KRITIS hospitals the obligations remain and grow.

Among others, we work with Kreiskliniken Reutlingen on IT and medical technology security.

Questions from hospital boards and IT

Is a penetration test mandatory under section 391 SGB V?

Section 391 SGB V does not prescribe a test method; it requires appropriate measures reflecting the state of the art. A penetration test is the standard instrument to show that they work.

Can you test networked medical devices as well?

Within a tightly agreed scope. Medical devices must not be put at risk during operation, so we test network connectivity, segmentation and remote maintenance rather than the devices.

Which areas are off-limits during the physical test?

The ICU, operating theatres and anything with direct patient impact. The list is set down in writing beforehand.

What does a pentest for a hospital cost?

That depends on scope: sites, systems, medical device networks, physical and social engineering. After the initial consultation you receive a fixed-price quote.

The state of the art keeps moving.

One short call is enough to settle scope and timing. You then receive a fixed-price quote, with no obligation.

Access Granted delivers the penetration test and the technical evidence, not the B3S review and not the registration with the BSI.