Device Control

Firewall Management

Centrally manage and deploy firewall rules to control inbound and outbound network traffic across managed endpoints.

1 min
September 1, 2026

What You'll Learn

How to create a Firewall Policy, including its profile, action, and inbound/outbound defaults
How to add a granular Firewall Rule to a policy, specifying action, protocol, direction, program path, and optional IP/port scoping
How to deploy a firewall policy to specific endpoints using a Policy Deployment
How to choose a deployment policy (e.g. an instant, out-of-the-box deployment) and set notification recipients
Where to review deployment progress and drill into per-endpoint task status and execution output

Frequently Asked Questions

What's the difference between a Firewall Policy and a Firewall Rule?

A Firewall Policy is the top-level container — it sets the profile, overall inbound/outbound posture, and whether it applies on startup. Each policy can then contain one or more Firewall Rules, which define the specific match criteria (protocol, direction, program, IP, port) and the action to take.

What can a Firewall Rule match on?

A rule can be scoped by profile (Domain, Private, Public), protocol (Any, TCP, UDP, ICMPv4, and others), direction (Inbound or Outbound), a specific program path, and optional local/remote IP addresses and ports.

What does "Overwrite if exists" do when creating a rule?

It lets a new rule replace an existing rule of the same name on the endpoint instead of failing or creating a duplicate.

How do I actually push a firewall policy to endpoints?

Creating a policy alone doesn't deploy it. Under Policy Deployments, create a deployment, choose a scope (e.g. specific endpoints), select the endpoints, pick the firewall policy to apply, and choose a deployment policy that controls how and when it's rolled out.

Where can I check whether a deployment succeeded?

The Policy Deployments list shows each deployment's stage and progress. Opening a deployment shows per-endpoint task status (e.g. Ready to Deploy, Success), and opening a task's output shows a timestamped execution log, including how many rules applied successfully and the final status.