> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/firewalls/pfsense.md).

# pfSense

You can configure a **pfSense® firewall** to forward syslog logs to the **ThreatDefence (TD) Syslog Forwarder** for security monitoring.

***

## Requirements

* A deployed and activated **ThreatDefence Syslog Forwarder VM**
* Administrator access to the pfSense firewall

***

## Steps

### Step 1. Access pfSense Syslog Settings

1. Sign in to your pfSense WebGUI with administrator permissions.
2. Navigate to:\
   **Status → System Logs → Settings**

***

### Step 2. Configure Remote Syslog Server

1. In the **Remote Syslog Servers** section, add your TD Syslog Forwarder:
   * **IP Address** — Enter the IP address of your TD Syslog Forwarder
   * **Port** — Use the appropriate port (as per the [Syslog Onboarding Guide](/appliances/syslog-forwarder/onboarding-syslog-data.md))
   * **Transport** — Select **UDP**
2. Under **System Events to Send to Syslog**, enable:
   * **Firewall Events**
   * **System Events**
   * **VPN Events** (if applicable)
   * **DHCP/DNS Events** (if applicable)
3. Click **Save**

***

***

## Step 4. Provide Details to ThreatDefence

Once configuration is complete, provide the following details to **ThreatDefence Support** at 📧 [**support@threatdefence.com**](mailto:support@threatdefence.com):

* Firewall make/model and pfSense version
* Source IP address and used port number.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.threatdefence.com/siem-integrations/firewalls/pfsense.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.