How to List Firewall Settings Across All Macs (2024)

Using Kolide, you can easily view and query Mac Firewall Settings across your fleet.

Introduction

The Application Firewall (often abbreviated ALF) is a security featurebuilt-into macOS that prevents unauthorized and untrusted apps from acceptingnetwork connections from the internet. Unless the Mac is using a third-partysoftware firewall, the macOS ALF should be enabled.

You can read more about the macOS Application Firewall onApple's support site

What Mac Firewall Setting Data Can Kolide Collect?

Kolide's endpoint agent bundles in osquery to efficiently collect Mac Firewall Settings from Macs in your fleet. Once collected, Kolide will parse, clean up, and centrally store this data in Inventory for your team to view, query, or export via API.

Kolide meticulously documents every piece of data returned so you can understand the results.

Mac Firewall Settings Schema

Column	Type	Description
id	Primary Key	Unique identifier for the object
device_id	Foreign Key	Device associated with the entry
device_name	Text	Display name of the device associated with the entry
allow_signed_enabled	Boolean	`true` if allow signed mode is enabled else `false`
enabled	Boolean	`true` if the firewall is enabled, else `false`
firewall_unload	Boolean	`true` if firewall unloading enabled else `false`
global_state	Enum::Integer	Describes the current state of the firewall Can be one of the following: `0` - The firewall is disabled `1` - The firewall is enabled, but is configured to allow some traffic through `2` - The firewall is configured to block all incoming connections
logging_enabled	Boolean	`true` If logging mode is enabled else `false`
logging_option	Enum::Integer	Logging verbosity options for `/var/log/appfirewall.log` Can be one of the following: `0` - Throttled `1` - Brief `2` - Detailed
stealth_enabled	Boolean	`true` If stealth mode is enabled else `false`
firewall_version	Text	The text representation of the version
firewall_version_major	Bigint	`firewall_version`'s semver major version(ex: `4.2.1` would yield `4`)
firewall_version_minor	Bigint	`firewall_version`'s semver minor version(ex: `4.2.1` would yield `2`)
firewall_version_patch	Bigint	`firewall_version`'s semver patch version(ex: `4.2.1` would yield `1`)
firewall_version_subpatch	Bigint	`firewall_version`'s numeric status fourth position number(ex: `4.2.1.6` would yield `6`)
firewall_version_pre	Text	`firewall_version`'s semver pre-release version(ex: `1.2.3-prerelease+build` would yield `pre-release`)
firewall_version_build	Text	`firewall_version`'s semver build version(ex: `1.2.3-prerelease+build` would yield `build`)
collected_at	Timestamp	Time the row of data was first collected in the database
updated_at	Timestamp	Time the row of data was last changed in the database

What Can You Do With This Information?

Kolide enables you to write your own queries against the data the agent collects. This allows you to build your own reports and API endpoints. For example, you can:

Find devices which do not have the built-in macOS firewall enabled

Show Query

Determine which devices have the Firewall Stealth Mode enabled

Show Query

enabled	device_name	stealth_enabled
false	Johns-MacBook-Pro	false
false	Daves-MacBook-Pro	false
false	ashleys-mac-mini	false
false	donut	false
false	Conference-Room-MacBook-Air	false

enabled	device_name	global_state	stealth_enabled
true	Daves-MacBook-Pro-2	1	true
true	Franks-MacBook-Pro-2	1	true
true	holden	1	true
true	imaging-parent	1	true
true	Laptop-2	1	true

Why Should I Collect Mac Firewall Settings?

Knowing the state of the built-in Firewall can help paint a broaderpicture of the computer's overall security and adherence to compliancestandards.

End-User Privacy Consideration

Kolide practices Honest Security. We believe that data should be collected from end-user devices transparently and with privacy in mind.

When you use Kolide to list Mac Firewall Setting data from end-user devices, Kolide gives the people using those devices insight into exactly what data is collected, the privacy implications, and who on the IT team can see the data. This all happens in our end-user privacy center which can be accessed directly by employees.