Case studyBanking & Financial Services

Datacenter firewalls and routing for a leading private bank: design, supply, and implementation

A redundant next-generation datacenter firewall pair with routing, designed and implemented as an integrated security core — awarded through open competition and delivered on schedule.

Delivered2023project completed
ClientA leading private bank with a strong digital-banking focus
Solution areasCybersecurity · Networking & Connectivity
TimelineThree months, delivered on schedule
01 — Challenge

The challenge

This bank had built its reputation on digital banking — a technology-forward institution whose services live in its datacenter and whose customers reach them through online and mobile channels. That strength was also its exposure: the datacenter was the bank, and the controls protecting it had to match.

The bank’s datacenter security needed a step change:

01Enforcement at the core, not just the edge Traffic between the bank’s internal environments — channel-facing systems, application tiers, database and core-banking tiers — needed application-aware inspection and policy, so that a foothold in one tier could not become a breach of all of them.
02No single point of failure Security enforcement in a datacenter must be at least as available as the services it protects. A firewall that fails closed takes the bank offline; one that fails open removes the protection. Neither is acceptable.
03Routing designed with security The datacenter’s traffic paths and the firewall’s placement had to be engineered together, so inspection happened where it mattered without introducing bottlenecks or asymmetric paths that break stateful security.
04Throughput for growth Digital banking traffic grows; the security core had to be sized for the bank’s trajectory, not its current load.

The bank tendered for the design, supply, and implementation of a datacenter firewall and router solution.

02 — Approach

Our approach

  1. 01

    Design first

    eSafe’s proposal — evaluated and accepted on both technical and financial merit — was built around a design, not a bill of materials: where enforcement points sit relative to the bank’s zones, how routing steers traffic through them symmetrically, how high availability is achieved, and how policy is structured to reflect the bank’s application landscape.

  2. 02

    Discovery and zone modeling

    We mapped the datacenter’s traffic flows and application dependencies to define security zones and the policies between them — inspection rules grounded in what actually talks to what.

  3. 03

    Staged implementation

    The firewall pair was staged and configured, integrated with the datacenter routing, and brought into the traffic path in phases — with policy first in visibility mode to validate against real flows, then enforced. Cutover windows were agreed with the bank; rollback was retained until each phase was verified.

  4. 04

    Test, document, accept

    Failover, throughput, and policy enforcement were tested and documented; the bank’s team was trained on the platform; the engagement closed with formal acceptance.

03 — Solution

The solution

Redundant next-generation datacenter firewalls

  • A high-availability firewall pair — active/passive with stateful synchronization — so a device failure or maintenance event causes no interruption to inspection or to service.
  • Application- and identity-aware policy: enforcement based on the application and the user or system behind a connection, not IP addresses alone — the foundation of meaningful datacenter segmentation.
  • Threat prevention on east-west traffic: intrusion prevention, malware protection, and command-and-control detection applied to traffic crossing zone boundaries inside the datacenter.
  • Sized for growth, with throughput headroom for the bank’s expanding digital-channel traffic.

Integrated routing

  • Datacenter routing engineered with the security design — symmetric traffic paths through the enforcement points, no asymmetric flows that would blind a stateful firewall, and resilient paths that survive a link or device failure.

Zone-based segmentation

  • Security zones defined from the bank’s application dependencies, with explicit policy between them — so the datacenter is a set of controlled trust boundaries rather than one flat, mutually trusting network.
04 — Result

The result

The datacenter security core was delivered on schedule and formally accepted, giving the bank application-aware, highly available protection at the heart of its digital-banking platform.

Delivered on schedule
Enterprise data loss prevention

The bank’s confidence showed in what came next: within a year it returned to eSafe — again through open tender — for its enterprise data loss prevention program, extending the relationship from network security into data security. When a technology-forward bank chooses the same integrator for two consecutive security programs, it is grading the first one.

05 — Why it worked

Why it worked

Routing and security as one design

Symmetric paths and correct placement made the firewall effective; treating routing separately would have undermined it.

Visibility before enforcement

Policy validated against real traffic first, so enforcement was accurate from day one.

HA is non-negotiable

In a datacenter, the security core must be as available as the bank itself — and it was designed that way.

Client identity withheld under our confidentiality commitments. Details, quotations, and outcomes are drawn from the client’s formal project acceptance and recommendation letters, held on file.

More case studies

Other engagements, same discipline

Next step

Have a project like this one?

Tell us your infrastructure reality and your constraints — we’ll show you how we’d approach it.

Talk to a pro