What is a hybrid mesh firewall?

The perimeter has already disappeared. A hybrid mesh approach presents an opportunity for defence, but why should healthcare organisations care?

Ask a hospital network engineer where the perimeter is, and the honest answer is: nowhere in particular.

A modern NHS environment stretches across hospital campuses, community sites, a traditional data centre or two, and a growing footprint of public cloud and SaaS platforms.

Clinicians log in remotely. Shared national services sit alongside locally hosted systems. Infusion pumps, imaging equipment, building controls, and other connected devices sit on the same estate as clinical applications – and a good number of them are running software too old to patch.

None of this is new to anyone working in NHS infrastructure. What has changed is the assumption underneath most firewall strategies: that most traffic worth inspecting will, sooner or later, cross a small number of well-defined boundaries. In a distributed estate, a large share of traffic never does.

Defining the hybrid mesh firewall

‘Hybrid mesh firewall’ is the term Cisco and others in the industry have started using for an architecture that spreads enforcement across physical firewalls, virtual and cloud-native firewalls, firewall-as-a-service, switches, and workload-level controls. Then, ties them together under a single policy model.

The defining idea is straightforward, even if the name is new: push enforcement closer to the user, device, application or workload that actually needs protecting, while keeping the security intent consistent everywhere it’s applied. The enforcement point moves. The policy behind it doesn’t.

It’s worth being precise about what this isn’t. A hybrid mesh firewall isn’t a single box or a single product, and it isn’t a replacement for every firewall an organisation already owns.

It’s better understood as the next step for the firewall itself. An evolution of the next-generation firewall model to fit an estate that no longer sits neatly behind one boundary.

Why the old model is straining

Traditional perimeter firewalls remain useful. What they can no longer do on their own is provide sufficient control across a modern healthcare estate.

Traffic moving between systems on the same site (otherwise known as east-west in networking terms) often never touches a perimeter firewall at all.

Every cloud and SaaS service adopted adds another enforcement point that sits outside the traditional boundary. Routing traffic back through a central appliance for inspection adds latency that clinical systems can’t always absorb.

And when policy lives on separate platforms with separate rule sets, configuration drift creeps in quietly and often unnoticed until an audit or incident finds it.

The practical risk is familiar: an unsegmented or compromised device becomes a route into systems it was never meant to reach.

What actually changes

A hybrid mesh approach changes how enforcement and policy work together.

Controls are distributed to sit nearer to what they’re protecting. Policy is defined once, centrally, and orchestrated across environments and sometimes across vendors if the underlying platform supports it.

Segmentation can be identity-aware rather than purely address-based. So access reflects who or what is actually connecting, not just which subnet it happens to sit on.

That segmentation can run from broad zones, such as clinical versus administrative traffic, down to individual workloads. Plus, detection and response draw on a wider set of signals than any one appliance could see alone because enforcement points share telemetry.

The net effect is fewer unrestricted paths for any attacker who gets an initial foothold into the estate.

The stakes in healthcare

Consider one scenario: an imaging device on a hospital network is compromised. It’s not an unusual starting point for an attacker, given how many such devices run outdated software.

In a flat network, that device is a stepping stone to whatever else sits on the same segment, including clinical applications.

Under a hybrid mesh approach, the device sits inside a much narrower policy boundary, and the systems around it are protected whether or not the device itself can be patched or run an agent.

That’s the healthcare case for hybrid mesh in a sentence: fewer unrestricted paths between a vulnerable device and the systems patient care depends on.

Not a rip-and-replace project

Few NHS organisations will implement every part of hybrid mesh at once, and nothing about the model demands they should.

Cisco is explicit that adoption is meant to be progressive, building on infrastructure already in place rather than replacing it.

The realistic starting point is more modest:

  • Map the enforcement points that already exist.
  • Identify where visibility or segmentation is thin.
  • Work out where unified policy would remove the most risk first.

The term is new. The problem it’s addressing isn’t. It’s still all about tackling infrastructure that has outgrown the boundaries built to protect it.

Want to learn more about hybrid mesh?

Join our upcoming webinar where Cisco experts will walk you through.

 

How to adopt network security when trust changes