Industry

Offensive Security for healthcare.

Hospitals, trusts, independent providers and health tech suppliers run services that can’t stop. The Swarm continuously tests your organisation the way a real attacker would, across digital, social and physical, so you know what holds and can prove it to your board, DSPT assessors and regulators.

What would an attacker take from you first?

You already invest in audits, assessments, and annual tests. They show what was checked on the day it was checked. They can’t show whether care would keep running if your organisation was targeted tomorrow.

Downtime simply isn’t an option. Every new system, supplier and device changes your risk, and your board and DSPT assessors want to know you’re ahead of it. That takes evidence, not assumptions, and that’s what the Swarm gives you.

Keep care running.

Clinical systems, scheduling and pathology are what patients feel first. We test whether they’d hold under a real attack, so disruption is something you’ve prepared for, not something you discover.

Protect patient trust.

A card can be reissued; a medical record can’t. We find the routes to patient data before anyone else does, and show your team exactly how to close them.

Know who has access.

Labs, billing, IT providers and device vendors all connect into your environment. We test those connections in every cycle, not just once at onboarding.

We attack the route to patient care.

Real incidents rarely start with one big flaw. They start with small gaps that line up: a rushed password reset, an unpatched device, a supplier’s remote access. The Swarm tests how those gaps connect, so you can break the chain, not just patch the links.

Identity and service desk

Clinicians, agency staff and shift workers across sites mean constant resets and access requests. We test whether your verification holds up under real pressure, and help your teams hold the line.

Clinical systems and patient portals

Electronic records, portals, scheduling and the integrations between them. We test access controls and APIs so a patient login only ever reaches that patient’s records.

Connected medical devices

Pumps, imaging, monitors and the networks they sit on, often running software that’s hard to patch. We test what’s reachable, within guardrails agreed with clinical engineering, and show you how to segment and protect it.

Suppliers and third parties

Labs, billing, IT providers and device vendors with access into your environment. We test those routes in, so a partner’s weakness doesn’t become yours.

Hospitals, surgeries and offices

Healthcare buildings are open by design, with public corridors and shared workstations. We test whether physical access could lead to digital access, and where simple changes close the gap.

Remote access and cloud

VPNs, remote desktops, telehealth and cloud platforms, often added quickly and rarely revisited. We test the configuration, so remote access works for your teams and no one else.

We know that real attack surfaces don’t come in neat categories. If yours doesn’t fit above, tell us what you’re working with.

What a Finding Looks Like

Finding

In a client login portal, a Swarm operator found three separate upload areas for IDs, documents and profile pictures, and used them as a way in.

Impact

Within three days: complete control over the web servers, the AWS domains and sensitive database information.

Remediation

Validate every upload server-side and store files where they can never execute. Limit the web server's cloud permissions to what it needs, and use parameterized queries in search.

Want the full picture?

The full range of offensive security the Swarm runs: every discipline, how they connect, and what each one tests.

Proof your board, insurers and auditors can see.

The CAF-aligned DSPT asks how well your controls work in practice, not just whether they exist. A real attack is the most direct evidence there is. Every Swarm cycle shows what was attacked, what held and what was fixed.

ObligationWhat it asks forHow the Swarm supports it
CAF-aligned DSPTOutcome-based assessment against the NCSC Cyber Assessment Framework. The 2026-27 version aligns to CAF 4.0, with submissions due 30 June 2027.Cycle-by-cycle evidence of controls under real attack, for your submission and independent assessment.
NIS Regulations 2018Health sector operators of essential services must manage cyber risk and report significant incidents.Evidence that essential services are tested against realistic attacks.
Cyber Security and Resilience BillWould update the NIS Regulations and bring more managed and digital service providers, the suppliers healthcare depends on, into scope. Passed the Commons June 2026; Lords report stage scheduled 26 October 2026.Supplier routes tested as part of every cycle.
UK GDPRReportable personal data breaches notified to the ICO within 72 hours.Evidence that the paths to patient data are tested against real attacks.

Stories from the Swarm

These stories are real, but the names are deeply redacted. We'll tell you how we uncovered the threats no one else could see, and why constant cyber attack is the best way to outpace cyber threats.

Frequently Asked Questions

What is penetration testing for healthcare?

Healthcare penetration testing is a controlled attack on an NHS trust, independent provider or health tech supplier by qualified ethical hackers, to find the weaknesses a real attacker would use to reach patient data or disrupt care. Continuous red teaming goes further, chaining weaknesses across clinical systems, devices, suppliers and staff the way real attackers do.

Does the DSPT require penetration testing?

The CAF-aligned DSPT is outcome-based, so it asks you to show how well your controls work rather than tick a box. Independent testing is one of the clearest ways to evidence that, and every Swarm cycle produces evidence you can use in your submission and assessment.

Will testing put patients or clinical systems at risk?

No. Every attack runs within guardrails agreed with your clinical and IT teams in your Attack Thesis, and patient care comes first. The goal is to find what breaks without breaking care.

Do you test connected medical devices?

Yes, within agreed boundaries. We test whether an attacker could reach connected devices and the networks around them, working with clinical engineering so nothing in use for patient care is disrupted.

Do you test people and physical sites, or only systems?

All three. The Swarm attacks digital, social and physical routes, because real attackers move between a phishing email, a service desk call and an unattended workstation on a public corridor.

How will the Cyber Security and Resilience Bill affect healthcare?

It would update the NIS Regulations and bring more of the managed and digital service providers healthcare depends on into scope. As of October 2026 it has passed the Commons and is in the House of Lords, so it is not yet law.