Skip to main content
Axottle helps control the network surface of nodes: block dangerous outbound ports, monitor suspicious traffic and keep the firewall in good condition.
For whom: Administrator and SRE. Required rights: Administrator of the panel.

Catalog of Dangerous Ports

There’s a fixed catalog of dangerous ports in the dashboard, broken down into categories, and each category has a default action and an indication of whether it’s enforceable, and each category is accompanied by an explanation of why it’s safe or why it shouldn’t be.
Service ports that are critical to operation (particularly DNS and NTP) are not consciously blocked by by — instead, anomalies are monitored by a detector, which eliminates accidental breakage of time and name resolving.

Controlling Outbound Traffic (Egress Guard)

Egress Guard applies a node-hazard port policy. The most important principle is that is “saved” ⁇ “applyed”: retaining the desired policy does not mean that it is already valid on the node. Protection is only applied when the node agent has confirmed the corresponding state. The order of operation, statuses and rollbacks are described in detail in the section Egress Guard.
Don’t confuse Egress Guard with “external transit egress blocks” in Flow - these are different features. Egress Guard blocks dangerous ports on the node; Flow transit blocks direct outbound traffic through an external node. Routing Flow.

Firewall and security profiles

The state of the firewall is additionally covered by security profile modules: basic firewall, permission of necessary ports, blocking of dangerous ports, backup of rules and rollback of rules in case of loss of connection. Read more - Audit and compliance .

Verification

Rollback

  • Unlock egress: Change the policy and re-enforce (reconcile) – see Egress Guard.
  • Firewall changes through security profiles are rolled back by reassigning the previous node profile.