Firewall change management, from ticket to verified rule

FwChange runs the change process for your firewalls. It reads the request from your ticket system, checks it against the real rulebase, sends the approval to the people who must sign off, and reads the firewall afterwards to check the result. It gets read-only accounts, so it cannot change a firewall: your engineers make the change and FwChange keeps the record.

fwchange.internal/changes
A firewall change request in FwChange: open HTTPS from the teller app to the payments gateway, with a three-level approval chain (security engineer and change manager approved, CISO step escalated) and a break-glass override button. A firewall change request in FwChange: open HTTPS from the teller app to the payments gateway, with a three-level approval chain (security engineer and change manager approved, CISO step escalated) and a break-glass override button.

How a change moves through FwChange

A change takes the same four steps each time, and each step lands in an audit trail you can export for an auditor.

1

Request

A ticket comes in. FwChange checks every field and sends an incomplete or wrong request back to the requester.

2

Check

FwChange tests the request against the firewall's current rules and reports whether it is already allowed, blocked by an earlier rule, conflicting or too broad.

3

Approve

The priority of the change sets who must approve it and in which order. Nobody approves their own change.

4

Verify

Your engineer makes the change in the change window. FwChange then reads the firewall and records what it finds.

When a change does not follow the plan

Break-glass override

In an emergency an authorised person can override the open approvals, with a written reason. A second person approves afterwards.

Escalation

An approval that passes its deadline is escalated and shows as overdue in the queue.

Drift check

FwChange flags a rule that someone changed on the firewall without a ticket.

The detail is in the demo.

Book a 30-minute demo

Runs inside your network

FwChange is self-hosted. Your rulebase stays where it is.

  • One virtual machine in your own network, like any other internal tool.
  • Read-only firewall accounts. FwChange asks for no write access to any firewall.
  • No internet access needed for the core workflow. Your rule data stays on the machine.
  • Microsoft sign-in with your own MFA rules, and separate roles from requester to auditor.

For teams that have to prove their changes

Banks and regulated companies

An examiner asks who approved a firewall change and what was checked first. FwChange holds that evidence for each change, from the ticket to the reading taken on the firewall.

Managed service providers

One tenant per client, each with its own firewalls, users and audit trail. You can give a client read-only access to its own changes.

What people ask first

Does FwChange change anything on the firewall?

No. It uses read-only accounts. Your engineer implements the approved change, and FwChange reads the firewall to check the result.

Which firewalls does it read?

Palo Alto, Fortinet, Check Point, Cisco ASA and FTD, Juniper SRX and more than twenty other platforms. We check your models and software versions with you before setup.

Is it hosted or self-hosted?

Self-hosted, on one virtual machine in your network.

What does it cost?

You get a written quote after the demo.

Book a 30-minute demo

You see one change go through the whole system on a sample estate, and you can ask anything.

  • By video call, at a time that suits you.
  • We need no data from your network.
  • Shown by the engineer who built it.

Sent through Formspree. We use your details only to reply. Privacy notice