Home / Case Studies / Corporate firewall uplift
Case Study · Secure Edge · 200+ User Environment

Corporate firewall uplift for a multi-site organisation with more than 200 users

A firewall and secure edge project focused on policy structure, access supportability, cloud traffic handling and post-cutover manageability.

Inlight IT supported a production firewall uplift for an operating environment supporting more than 200 users with distributed access requirements, cloud productivity use and business-critical connectivity needs.

SITESMANAGED EDGECORE SECURE EDGE BASELINE INSPECTIONPOLICYACCESS MULTI-SITE OPERATING MODEL / CORPORATE FIREWALL UPLIFT ONE SECURE EDGE ACROSS SITES
Engagement at a glance

Corporate firewall and secure edge uplift

A representative engagement showing scale, delivery discipline and operating outcome.

Engagement type
Corporate firewall and secure edge uplift
Client profile
Australian multi-site organisationClient name withheld. The project details and outcomes reflect a completed engagement.
Scale
200+ user operating environment
Environment
Distributed corporate operating environment with cloud productivity, business systems, access requirements and site-connectivity considerations
Delivery scope
5 delivery workstreams across firewall uplift, policy structure, traffic control, access supportability and operational handover
Implementation approach
5-stage delivery sequence: review, design, prepare, cut over, operate
Outcome areas
6 operating outcomes: edge control, policy structure, cloud supportability, access supportability, operational handover and future network readiness
Key project stats

Project scale and delivery structure

200+
users

Firewall uplift delivered for an operating environment supporting more than 200 users with distributed access and cloud productivity requirements.

5
delivery workstreams

Delivery covered firewall uplift, policy structure, traffic control, access supportability and operational handover.

5
stage cutover approach

The project moved through review, design, preparation, production cutover and post-cutover operation.

6
operating outcome areas

The engagement improved edge control, policy structure, cloud supportability, access supportability, operational handover and future network readiness.

Operating context

The firewall sat at the point where security, access, cloud traffic and supportability all met

The organisation's environment needed to support users across multiple working patterns, locations and business systems.

In that context, the firewall could not be treated as a simple perimeter appliance. It needed to operate as a controlled network edge, supporting secure access, traffic flow, cloud platform use and ongoing manageability.

The project focused on creating a more supportable security and network control point, not simply completing a hardware or configuration change.

Why this work mattered

The network edge needed an operating model, not just a technical cutover

For the client, the key question was not only whether traffic could pass through the firewall. It was whether the environment would remain secure, visible and supportable after implementation.

01

Business workflows depended on reliable access

The environment needed to support communication, collaboration, corporate systems and operational workflows without unnecessary access friction or performance risk.

02

Cloud traffic needed practical handling

Cloud productivity platforms behave differently from traditional on-premises applications. Firewall and routing decisions needed to account for user experience, access reliability and supportability.

03

Access pathways needed clearer structure

The organisation required controlled access pathways for users and business operations without creating unmanaged exposure or unnecessary exceptions.

04

Firewall policy needed discipline

Firewall rules and access exceptions can accumulate over time. The project needed to establish a clearer policy baseline so future changes could be reviewed and supported properly.

05

Lifecycle ownership needed to be planned

A firewall uplift is not complete at cutover. The environment needs documentation, ownership, review and lifecycle planning so it remains manageable as the business changes.

What Inlight IT delivered

A firewall and secure edge uplift aligned to the client's operating environment

Inlight IT delivered the project around five practical workstreams: current-state review, firewall uplift, policy and traffic control, secure access supportability and operational handover.

01

Firewall uplift and edge-control design

Inlight IT reviewed the operating requirements and supported the firewall uplift around the client's traffic patterns, access needs and manageability requirements.

Included
Network edge reviewTraffic flow considerationsPolicy baseline planningRouting and access considerationsCutover planningOperational support considerations
02

Policy structure and traffic control

Firewall policy was structured around business access requirements and future supportability. The aim was to create a cleaner foundation for allowed traffic, blocked traffic, cloud access and business system dependencies.

Included
Firewall policy reviewRule-structure improvementAccess pathway clarificationException reduction where practicalLogging and visibility considerationsDocumentation for supportFuture change-management pathway
03

Security service and lifecycle considerations

The project considered how the firewall environment would be maintained after implementation. The objective was to avoid creating a once-off configuration that would become difficult to support or review.

Included
Security service alignmentInspection and performance considerationsLifecycle planningUpdate and maintenance considerationsSupport documentationOperational review pathwayEscalation planning
04

Secure access supportability

Access was treated as an operating-control issue, not only a connectivity feature. The firewall environment needed to support users and business access requirements while keeping access pathways more manageable.

Included
Access supportability reviewIdentity and access alignment considerationsUser access policy considerationsThird-party access considerationsLeast-privilege access planningFuture access-model readinessSupport handover
05

Operational handover and managed support

The firewall environment was brought into a managed support rhythm so it could be reviewed, changed and supported after cutover.

Included
Operational handoverDocumentationSupport process alignmentChange-management considerationsLifecycle review planningIssue escalation pathwayOngoing improvement considerations
Delivery approach

The project was structured to protect continuity while improving the control position

Select a stage to trace how the project moved from review to managed operation.

External threat signals

The numbers behind edge-device risk

Firewall, VPN and perimeter technologies are no longer background infrastructure. They are active targets — sitting between the organisation, cloud services, remote users and the public internet. That is the commercial context for treating a firewall uplift as an operating-control project, not just a hardware change.

22%

Edge devices and VPNs represented 22% of vulnerability-exploitation actions in the 2025 Verizon DBIR.

1,700+

ASD's ACSC made more than 1,700 notifications to entities of potentially malicious cyber activity in FY2024–25.

83%

ASD reported those notifications increased 83% from the previous year.

120+

ASD observed more than 120 incidents associated with attacks on edge devices in FY2024–25.

Verizon 2025 DBIRASD Annual Cyber Threat Report 2024–25
What changed for the client

A more supportable network-edge environment for a 200+ user operating model

The project helped create a stronger firewall operating baseline for an environment supporting more than 200 users. The network edge became easier to support, easier to review and better aligned to the organisation's access, cloud and operating requirements.

O·01

Clearer edge control

The firewall environment became a clearer control point for business traffic, access requirements and network-edge policy.

O·02

Stronger policy structure

Firewall policy could be managed with clearer structure, reducing the risk of unmanaged rules, unclear exceptions and unnecessary access paths.

O·03

Better cloud supportability

Cloud platform traffic was considered as part of the firewall and network operating model, not treated only as generic internet traffic.

O·04

More manageable access pathways

Access pathways could be reviewed against business need, user context, supportability and future security requirements.

O·05

Improved operational handover

Documentation, support process alignment, review pathways and change-management considerations were incorporated into the operating model.

O·06

Foundation for future network work

The project created a more documented and reviewable baseline for future network, secure access and edge-security improvements.

Net position

A documented, reviewable network-edge baseline the business can operate, audit and build on — not a cutover the business has to work around.

Project outcomes

A corporate firewall uplift delivered with measurable operating scope

Outcome 01

Environment supporting 200+ users

The project supported an operating environment supporting more than 200 users with distributed access, cloud productivity and business application requirements.

Outcome 02

5 delivery workstreams completed

The engagement covered firewall uplift, policy structure, traffic control, access supportability and operational handover.

Outcome 03

Production cutover managed

The project was structured around production continuity, dependency review, rollback planning and operational validation.

Outcome 04

Cloud traffic considered

Cloud productivity and business application access were considered as part of the firewall and network operating model.

Outcome 05

Access supportability improved

Access requirements were reviewed through the lens of supportability, business need and future operating requirements.

Outcome 06

Operating baseline strengthened

Documentation, support process alignment, change-management considerations and lifecycle planning were included as part of the project.

Technology and service scope

The work connected firewall engineering, secure access and managed network operations

Firewall and edge

7
  • Enterprise firewall uplift
  • Network edge control
  • Firewall policy structure
  • Traffic flow review
  • Routing considerations
  • Application and service access requirements
  • Production cutover support

Security and lifecycle

7
  • Security service considerations
  • Inspection and performance considerations
  • Update and maintenance planning
  • Lifecycle review
  • Visibility and logging considerations
  • Operational documentation
  • Support escalation pathway

Network and access

7
  • Secure access requirements
  • Identity and access alignment considerations
  • Third-party access considerations
  • Least-privilege planning
  • Cloud traffic considerations
  • Future network readiness
  • Support handover

Managed operations

8
  • Operational handover
  • Support process alignment
  • Change-management considerations
  • Lifecycle planning
  • Issue escalation
  • Service review alignment
  • Ongoing improvement planning
  • Managed firewall operation
Practical next step

Need a firewall environment that stays manageable after cutover?

Inlight IT can help design, uplift and manage firewall environments that support secure access, clear policy structure, cloud traffic handling, access supportability and ongoing lifecycle ownership.

Discuss firewall and secure edge