> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Liongard pfSense Read

> Interrogate a client's pfSense firewall through the Liongard pfSense inspector — version, interfaces, firewall/NAT rules, VPN config, packages, admin access. Use for "what's their pfSense config?", rule/exposure review during triage, or version-currency checks.

<Info>
  **Category:** Liongard Inspectors · [View source ↗](https://github.com/bryan-getthread/skills/blob/main/skills/liongard-inspectors/liongard-pfsense/SKILL.md)
</Info>

**Connectors:** `Liongard`

**Role:** [Technician](/start-here/roles/technician)

**Outcome:** Risk & Compliance, Faster Resolution & Response

**When to use:** "What firewall rules / port-forwards are configured at \<client>?", a connectivity or exposure ticket, "what pfSense version are they on?", a VPN (IPsec/OpenVPN) troubleshooting read, or "did a rule or NAT entry change?".

**Run it:** on one client — name the client and the pfSense question.

## Prompt

```
Read pfSense firewall config for CLIENT_NAME from the Liongard pfSense inspector. Read-only — firewall changes go through the partner's change process.

1. Resolve the client's environment, then find the pfSense inspector and confirm it ran recently — carry "as of <timestamp>." A client may have multiple firewalls — enumerate them.
2. Read the values from its latest dataprint for the angle you need, verifying every field angle against the live dataprint (schemas vary by inspector version):
   - Rules: firewall rule list with action, interface, source/dest — flag any-any allows.
   - Port-forwards/NAT: inbound NAT with external port to internal host — flag exposure of RDP/3389, SMB/445.
   - Version: pfSense version — report verbatim, compare against current release.
   - VPN: IPsec/OpenVPN tunnel/server list with peers.
   - Admins: local admin accounts and access methods.
3. "What changed?" → check what changed on pfSense: rule adds/edits, NAT changes, version upgrades, package changes — ordered against the incident window (time-adjacency, not proven cause).
4. Sanity-check surprising zeros (zero rules) — usually a wrong field angle or partial inspection; re-probe broadly. Never paste PSKs, VPN pre-shared keys, or credentials into notes — reference "PSK on file in <doc platform>." Exposure findings are risk inputs, not confirmed breaches — "external RDP NAT present, verify need" phrasing.
5. Output: a compact table, source + data age line, flags (risky inbound NAT, any-any rules, outdated version, unexpected admins). Offer to leave a plain-text note. Degradation: no pfSense inspector → documentation → ticket history → "verify on appliance."
```


## Related topics

- [Liongard Duo Read](/skill-library/liongard-inspectors/liongard-duo.md)
- [Liongard Okta Read](/skill-library/liongard-inspectors/liongard-okta.md)
- [Liongard Azure Read](/skill-library/liongard-inspectors/liongard-azure.md)