Case studyGovernment & Public Sector

Datacenter switching and next-generation firewalls for a federal ministry: a four-milestone delivery, formally accepted

Next-generation perimeter and datacenter firewalls, centralized firewall management, and layer-3 DMZ switching for a national revenue authority — delivered milestone by milestone, integrated end to end, and formally accepted “in accordance with the contractual requirements, approved technical specifications, and implementation standards.”

Delivered2025project completed
ClientA federal government ministry — a national revenue authority
Solution areasCybersecurity · Networking & Connectivity · Data Center
TimelineDelivered milestone by milestone; each firewall phase completed within a two-week window
01 — Challenge

The challenge

A national revenue authority runs some of the most consequential systems in any government: the platforms through which a country collects the taxes and duties that fund it. Those systems face relentless attention from attackers — and they answer to a public that expects them to work, and to a government that expects them to be secure and sovereign.

The ministry’s datacenter security needed a generational upgrade, and it needed it under the discipline of public procurement — a formal, milestone-based contract with defined technical specifications, acceptance criteria, and implementation standards.

The gaps were structural:

01The perimeter needed next-generation inspection — application awareness, intrusion prevention, threat intelligence — with centralized management, so the ministry’s team could govern policy from one place rather than device by device.
02The datacenter needed its own firewalling: enforcement between internal zones so that a compromise anywhere could not reach the revenue systems at the core.
03The DMZ — the zone hosting the ministry’s public-facing services — needed proper layer-3 switching to be segmented and routed correctly rather than flat-bridged into the rest of the network.
04Integration Perimeter, datacenter, and DMZ had to work as one architecture, tested end to end, not as three deliveries that merely coexisted.

And it all had to be delivered to a public body’s standard: documented, tested against specification, accepted formally, with the ministry’s own staff trained to operate it.

02 — Approach

Our approach

  1. 01

    Compete and win on compliance with the specification

    eSafe’s bid was evaluated against the ministry’s approved technical specifications and won through the national competitive procurement process. The contract — with defined milestones, acceptance criteria, and standards — became the project plan.

  2. 02

    Milestone discipline

    The work was structured as four contractual milestones, each with delivery, implementation, configuration, migration where applicable, and operational testing — and each closed formally before the next began. This gave the ministry visibility and control at every stage.

  3. 03

    Migrate without disrupting revenue services

    Both firewall phases involved migration from existing infrastructure. Each was executed within a tightly planned two-week window, with policy migrated and validated before enforcement and rollback retained until the ministry confirmed operational status.

  4. 04

    Test everything, end to end

    The final milestone was dedicated entirely to integrating the deployed components and completing end-to-end operational testing — proving that the perimeter, datacenter, and DMZ worked as one system under real conditions.

  5. 05

    Transfer the knowledge

    Training and knowledge transfer to the ministry’s ICT team were part of the contractual scope and were completed and confirmed — a public body must be able to operate what it has bought.

03 — Solution

The solution

Milestone one — next-generation perimeter firewall and central management

  • Next-generation firewalls at the ministry’s internet edge: application- and identity-aware policy, intrusion prevention, and threat prevention, replacing legacy perimeter equipment.
  • A centralized firewall-management platform, so policy across the perimeter estate is defined once, pushed consistently, versioned, and audited from one console.
  • Delivered, configured, migrated from the previous perimeter, and operationally tested within a two-week window.

Milestone two — next-generation datacenter firewall

  • Datacenter firewalling between the ministry’s internal security zones — enforcement at the boundaries around the revenue systems, so lateral movement is stopped rather than assumed impossible.
  • Delivered, configured, migrated, and operationally tested within a two-week window.

Milestone three — layer-3 DMZ switching

  • Layer-3 switches for the DMZ, giving the public-facing zone proper routed segmentation from the internal network — the DMZ becomes a controlled, inspected boundary rather than a bridged extension of the core.
  • Delivered, configured, and operationally tested.

Milestone four — integration and end-to-end testing

  • Integration of all deployed components — perimeter, datacenter, DMZ, and management — into one coherent security architecture.
  • End-to-end operational testing across the integrated system, confirming traffic paths, policy enforcement, failover, and management under real conditions.
  • Knowledge transfer and user training for the ministry’s ICT team.
04 — Result

The result

The project was successfully completed and formally accepted. Following what the ministry described as “a comprehensive review, inspection, and acceptance process,” it confirmed in a formal testimony letter that the project “has been completed in accordance with the contractual requirements, approved technical specifications, and implementation standards” — that “all equipment has been properly installed, configured, integrated, tested, and commissioned,” that “knowledge transfer and user training have also been successfully conducted,” and that “the implemented solution is fully operational and performing in accordance with the required specifications and technical standards.”

The implemented solution is fully operational and performing in accordance with the required specifications and technical standards
From the client’s letter

The ministry closed its letter by appreciating “the professionalism and commitment demonstrated throughout the project” and stating that it looks forward to “future opportunities for collaboration.”

For a national revenue authority, that is the outcome that matters: a modern, segmented, centrally governed security architecture around the systems a country’s finances depend on — delivered to specification, proven end to end, and operated by the ministry’s own people.

05 — Why it worked

Why it worked

The contract was the plan

Milestones, specifications, and acceptance criteria defined the work — and the work was delivered against them, phase by phase.

Migrate in windows, prove before you enforce

Two-week migration windows with validated policy and retained rollback kept revenue systems live throughout.

Integration is a milestone, not an assumption

A dedicated end-to-end testing phase is why the pieces worked as one system.

Public bodies must own their platforms

Knowledge transfer was contractual, completed, and confirmed.

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.

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