pfSense
Uses the same SSH mechanism, credentials, and host key verification as
the SSH-based OS identification
family, but reads pfSense’s own /etc/version and /etc/platform in
one round trip.
targets: - id: pfsense-fw product: pfsense address: fw.example.com credentials: linux-host-sshAuthentication — required
Section titled “Authentication — required”An SSH credential, ssh-key or password — see
Configuration → Credentials.
Community Edition only
Section titled “Community Edition only”Confirmed live against three real pfSense CE hosts (2.7.2-RELEASE,
2.8.1-RELEASE): /etc/version holds exactly the version pfSense’s own
dashboard shows, and /etc/platform reads pfSense.
Netgate’s commercial pfSense Plus is a different product with its
own calendar-based version scheme (24.11, not 2.x.y-RELEASE). By its
documentation it reports pfSense-Plus in /etc/platform; this probe
rejects that rather than record a Plus host as a CE fact. No Plus host
was available to confirm this live — it’s based on documentation alone.
Recorded fields
Section titled “Recorded fields”version—/etc/versionas is, e.g.2.8.1-RELEASEextra.hostKeyVerified
CVE correlation
Section titled “CVE correlation”Matched against NVD and БДУ ФСТЭК when a cve: block is configured. Since 2.2. The probe reports
Community Edition only, so NVD’s pfSense Plus ranges (sw_edition: plus)
never apply — see
Edition-aware matching.
Lifecycle resolver
Section titled “Lifecycle resolver”None — endoflife.date has no page under pfsense, pfsense-ce or
pfsense-plus (confirmed 404). Inventory-only for now.