Tiza Group

Home / Tools / Firewall rule reviewer

Zone firewall rule reviewer

Write the firewall rules between the zones of the example substation. The tool shows which rule decides each flow, which needed flows are cut, which pass without need and which rules are risky, and proposes the minimal rules.

Example cases
Zone firewall rule reviewer
ALearn

E1Firewall rules
Rules in order

One row per rule, in the order the firewall reads them: the first match decides.

RowSourceDestinationProtocolActionRemove

E2Conditions

Temporary connections: CNO Agreement 1960, annex 1, 6.6.

E3View

Rule number; 0 = the last one you edited.

Use a decimal point. The calculation runs in your browser and updates as you type.

Needed flows passing

—

Excess allowed

—

Risky rules

—

Score (Tiza criterion)

—

What passes and what is blocked at each conduit
  • Passes and is needed
  • Cut or not needed
  • Correctly blocked
Red with a cross: a needed flow that is cut. Moving red: passes although the operation does not need it. The flows that changed with the last edit and the conduit of the selected rule are highlighted.

Each flow, the rule that decides it and its state

FlowZonesProtocol and portNeededDecidesState

Ports from the IANA registry. «Policy»: no rule matches and the default policy decides. ● marks the flows that changed with the last edit.

Rules and their risk

#RulePortDecidesRisk and source

Suggested minimal rules

One «allow» rule per source zone, destination zone and protocol of the needed flows, in the order of the flows, and «deny all» at the end. They let exactly what is needed through with any default policy.

#RulePortFlows it lets through

What it is for

To review the firewall rules of a substation before loading them, or to understand why a flow is cut. You write the rules by source zone, destination zone and protocol; the tool applies the first match to each flow and shows on the network what passes and what is blocked.

The network is the same in every Tiza cybersecurity tool: seven zones, from the remote vendor to the bay network, and sixteen flows: eleven needed flows that cross a conduit, GOOSE inside the bay and four that nobody needs.

What is checked

  • The needed flows pass and nothing else. Every flow the operation needs must pass and every flow it does not need must stay closed, with the default policy set to «deny». Source: CNO Agreement 1960 of 2025, annex 1, 6.5.
  • No «any» rules or wildcards. A rule that allows any protocol between any zones opens ports nobody asked for. A wildcard in an «allow» rule is flagged for review, and it is a failure if the rule comes from the control centre, the vendor or the corporate network. Source: CNO 1960, 6.5.
  • Remote access through the intermediate system. No rule lets traffic from the corporate network or the vendor straight into the station or the bay, nor from the control centre straight into the bay: remote access reaches the jump server in the DMZ. Source: CNO 1960, 6.7.
  • Access logging. Rules are not enough: every access point must log permitted and denied accesses, 24 hours a day. The tool reminds you of it; it does not check it. Source: CNO 1960, 6.3.
  • Temporary connection only with a permit. The maintenance laptop rule is accepted while a permit is in force; without a permit it is a failure. Source: CNO 1960, 6.6.
  • No clear-text credentials between zones. Telnet, FTP, HTTP and SNMP v1/v2c send the password unencrypted: no rule lets them cross a conduit. Tiza criterion (estimate).
  • No shadowed or unused rules. A rule that never acts because a rule above takes all its traffic is a design error; an «allow» rule that lets no needed flow through is surplus. Tiza criterion (estimate), with CNO 1960, 6.5.

Limits

  • It filters by zone and protocol, like the rules between conduits; it does not handle IP addresses, custom ports, session direction or content inspection.
  • It works with the reference network of seven zones and sixteen flows; it does not accept your own devices or flows.
  • It does not review the real configuration of a vendor's firewall and does not replace the on-site test. The example cases are illustrative.

Frequently asked questions

Why does the order of the rules matter?

The firewall applies the first rule that matches and ignores the rest. A broad «deny» at the top can cancel an «allow» below it, and an «allow» with a wildcard at the top can open what a rule below meant to close.

What is the default policy?

What the firewall does with traffic that matches no rule. In a substation it must be «deny»: only what a rule explicitly opens gets through.

How is the score calculated?

It is a Tiza criterion (estimate): 60 points for the needed flows that pass and 40 for the unneeded flows that stay closed, in proportion. With an «any» rule or the «allow» policy it does not go above 30. It is not a rating from a standard.

Can I use my own rules and devices?

You can write or paste any set of rules by zone and protocol. The network is the reference substation of the Tiza cybersecurity tools: sixteen devices in seven zones.

Related guides

Other tools

All tools
WhatsApp