Home / Case Studies / Corporate Firewall
Case Study · Industrial · Corporate Firewall

Corporate firewall support for an Australian industrial business — securing the network edge

The business is an industrial equipment and materials handling supplier. For an industrial business, the corporate firewall protects more than office internet access — it supports secure connectivity, user access, Microsoft 365 traffic, remote work, supplier communication, vendor support pathways, business systems, backup dependencies and the security boundary between the organisation and the outside world.

Inlight IT supports the business with corporate firewall control as part of a cyber-first managed IT operating model: perimeter security, policy management, access control, lifecycle visibility, escalation and continuous improvement brought into the managed support rhythm.

OUTSIDEINSPECTIONINSIDE MANAGED EDGE / INSPECTION INSPECTIONPOLICYACCESSSERVICES INDUSTRIAL / CORPORATE FIREWALL MANAGED EDGE / POLICY · ACCESS · SERVICES
Engagement at a glance

An Australian industrial business — managed corporate firewall for an industrial network edge

Perimeter security, policy and access control, lifecycle visibility and ongoing improvement in one operating model.

Client
Australian industrial business
Industry
Industrial
Region
Industrial operating environment
Environment
Users, business systems, cloud services and remote and third-party access requirements
Engagement
Managed corporate firewall — perimeter security, policy and access control, lifecycle visibility, security services and ongoing improvement
Operating model
Cyber-first managed IT, with the firewall inside the managed support rhythm
Outcome
A more controlled firewall posture, treated as part of the managed environment rather than a standalone appliance
Key project stats

One managed control point, five operating disciplines

5
operating disciplines

Visible policy, managed access pathways, live security services, lifecycle visibility and firewall control inside managed IT.

1
network edge

Users, business systems, cloud services and remote and third-party access requirements sit across the environment.

6
posture shifts

From understandable firewall policy to edge control aligned to backup dependencies, Microsoft 365 traffic and continuity.

10
service areas connected

From perimeter security and policy management to firmware lifecycle, logging and managed firewall operation.

Operating context

The business needed firewall control for an industrial operating environment, not a generic office network

Industrial organisations often carry complex network requirements: business systems, remote and third-party access, shared devices, cloud platforms, backup dependencies and supported applications.

The firewall needs to support that reality without leaving unmanaged access paths or unclear security responsibility.

Firewall policy, remote access, internet access, Microsoft 365 traffic, third-party access pathways, logging, firmware and security services all affect how safely and reliably the business operates.

Why this work mattered

A managed, visible, supportable firewall posture is a security requirement, not a configuration detail

Firewall, VPN and perimeter devices are no longer passive infrastructure — they are high-value control points, and the way they are operated determines how safely the business runs.

01

Edge devices offer attackers a path inside

Attackers target edge devices because they can provide initial access, credential exposure, traffic visibility and a path into internal systems.

02

Firewall policy had to stay tied to business need

Rule bases accumulate drift over time. The rule base needed to stay understandable and tied to actual business requirements.

03

Access pathways had to be deliberate

Remote and third-party access pathways needed to be managed deliberately rather than left as open paths.

04

Lifecycle risk had to surface early

Firmware and perimeter lifecycle risk needed to be visible ahead of time, rather than at a lifecycle decision point or once it had become urgent.

05

The firewall could not sit outside managed IT

A firewall run as a disconnected device leaves unclear security responsibility. It needed to sit inside the managed operating model rather than as a standalone appliance.

What Inlight IT delivered

Managed firewall support connected to access, policy, lifecycle and operational resilience

Inlight IT treats the corporate firewall as part of the managed IT operating model, focusing on visibility, policy control, access management, lifecycle awareness, security services and ongoing improvement.

01

Keeping firewall rules visible, supportable and aligned to business need

Rule base kept understandable and tied to actual business requirements, not accumulated drift.

Included
Visible policyRule base clarityBusiness-need alignmentDrift reductionPolicy managementSupportable rules
02

Managing access pathways through a security and operational lens

Remote access and connectivity managed deliberately rather than left as open paths.

Included
Remote access controlThird-party access pathwaysThird-party accessDeliberate connectivityAccess reviewControlled pathways
03

Treating security features as operational controls, not checkboxes

Security services run as live controls, not one-time configuration.

Included
Live security servicesOperational controlsLogging & visibilityOngoing configurationSecurity visibilityControl effectiveness
04

Keeping perimeter lifecycle risk visible before it becomes urgent

Firmware and lifecycle risk surfaced ahead of time, rather than at a lifecycle decision point.

Included
Firmware lifecycleLifecycle visibilityLifecycle awarenessRisk surfaced earlyPerimeter lifecycleLifecycle ownership
05

Including firewall control inside managed IT, not as a disconnected device

The firewall sits inside the managed operating model rather than as a standalone appliance.

Included
Managed IT integrationEscalation pathwayContinuous improvementManaged support rhythmConnected environmentNot a standalone appliance
Delivery approach

Firewall support managed through visibility, policy control, lifecycle ownership and practical improvement

Select a stage to trace how the firewall runs as an operating discipline.

Market context

Network edge devices are now active security targets

Firewall, VPN and perimeter devices are no longer passive infrastructure — they are high-value control points. Attackers target edge devices because they can provide initial access, credential exposure, traffic visibility and a path into internal systems. That makes a managed, visible, supportable firewall posture a security requirement, not a configuration detail.

5

Five operating disciplines keep the firewall visible, controlled and supportable inside managed IT.

1

The environment carries users, business systems, cloud services and remote and third-party access requirements.

6

Six posture shifts, from visible policy to edge control aligned to continuity.

10

Ten technology and service areas connected, from perimeter security to managed firewall operation.

Industrial business engagementInlight IT delivery record
What changed for the client

A clearer corporate firewall operating model for an industrial business

The service is structured to keep the firewall useful as a security and network control: what access is required, what should be reduced, how lifecycle risk is managed and how the firewall remains supportable over time.

O·01

Firewall policy kept understandable

Rules stay visible and aligned to business need, not accumulated drift.

O·02

Access pathways controlled

Remote access and connectivity managed through a security and operational lens.

O·03

Security features run as controls

Security services treated as live operational controls, not checkboxes.

O·04

Lifecycle risk made visible

Firmware and perimeter lifecycle risk surfaced before it becomes urgent.

O·05

Firewall inside managed IT

The firewall is part of the managed environment, not a standalone appliance.

O·06

Operational resilience supported

Edge control aligned to backup dependencies, Microsoft 365 traffic and continuity.

Net position

The value was not the appliance. It was a firewall posture treated as part of the managed environment rather than a standalone device.

Project outcomes

A firewall is an operating control, not a set-and-forget device

Outcome 01

Visible policy

Rules kept understandable and current.

Outcome 02

Controlled access

Remote and third-party pathways managed deliberately.

Outcome 03

Live security services

Controls run, not just configured.

Outcome 04

Lifecycle visibility

Firmware and EOL risk surfaced early.

Outcome 05

Inside managed IT

Firewall connected to the wider environment.

Outcome 06

Edge as a target

Perimeter treated as a high-value control point.

Technology and service scope

The work connected perimeter security, policy, access and managed firewall operation

Perimeter and policy

6
  • Corporate firewall
  • Perimeter security
  • Policy management
  • Rule base clarity
  • Business-need alignment
  • Logging & visibility

Access control

6
  • Access control
  • Remote access
  • Third-party access pathways
  • Third-party access
  • Microsoft 365 connectivity
  • Deliberate access paths

Security services and lifecycle

6
  • Security services
  • Live operational controls
  • Firmware lifecycle
  • Lifecycle visibility
  • Perimeter risk awareness
  • Lifecycle ownership

Managed operation

6
  • Managed firewall operation
  • Managed IT integration
  • Escalation pathway
  • Continuous improvement
  • Backup dependency alignment
  • Operational resilience
Practical next step

Is your firewall still secure, supportable and aligned to the way your business operates?

We review firewall policy, access and lifecycle, then manage the environment after cutover.

Book a Firewall Review