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

# WCF Agent – Event Formats (CEF)

> Network events and CTI metrics sent by the WCF Agent to your SIEM in CEF format

**Vendor:** OneFirewall\
**Product:** WCF Agent\
**Output format:** CEF (Common Event Format) over Syslog

***

## 1. Overview

The WCF Agent sends two types of data to the customer's SIEM or log collector:

| Type | Description | Frequency |
| - | - | - |
| **a) Network Events** | One event per connection evaluated by the agent (allowed or blocked) | Real time |
| **b) CTI Metrics** | Threat intelligence statistics, aggregated over a time window | Periodic (configurable interval) |

> [!NOTE]
>
> **Both formats are fully customizable from the OneFirewall central console.**
> The examples below show the default layout. Fields, labels, severity, interval and destination can all be changed to match your SIEM and use cases. See [Section 5 – Customization](#5-customization).

***

## 2. CEF Structure

```
CEF:Version|Device Vendor|Device Product|Device Version|Signature ID|Name|Severity|Extension
```

| Header field | Default value |
| - | - |
| Version | `0` |
| Device Vendor | `OneFirewall` |
| Device Product | `WCF Agent` |
| Device Version | Agent version (e.g. `2.4`) |
| Signature ID | Event type ID (e.g. `NET-1001`, `CTI-2001`) |
| Name | Human-readable event name |
| Severity | `0`–`10` |
| Extension | `key=value` pairs (see below) |

***

## 3. a) Network Events

### Example – Blocked connection (outbound to malicious IP)

```
CEF:0|OneFirewall|WCF Agent|2.4|NET-1001|Outbound connection blocked - malicious destination|8|rt=Nov 16 2026 09:42:17 UTC dvchost=wcf-agent-01 src=10.20.1.15 spt=51544 dst=203.0.113.47 dpt=443 proto=TCP act=blocked deviceDirection=1 out=517 in=0 cs1Label=CrimeScore cs1=92 cs2Label=ThreatCategory cs2=C2 cs3Label=PolicyName cs3=Block-High-Risk-Outbound cn1Label=RuleID cn1=1042
```

### Example – Allowed connection (inbound, low risk)

```
CEF:0|OneFirewall|WCF Agent|2.4|NET-1000|Inbound connection allowed|2|rt=Nov 16 2026 09:43:02 UTC dvchost=wcf-agent-01 src=198.51.100.23 spt=60211 dst=10.20.1.40 dpt=22 proto=TCP act=allowed deviceDirection=0 in=3120 out=4410 cs1Label=CrimeScore cs1=12 cs2Label=ThreatCategory cs2=None cs3Label=PolicyName cs3=Default-Allow cn1Label=RuleID cn1=1
```

### Field reference

| CEF key | Label | Description |
| - | - | - |
| `rt` | – | Event timestamp |
| `dvchost` | – | Agent hostname |
| `src` / `spt` | – | Source IP / port |
| `dst` / `dpt` | – | Destination IP / port |
| `proto` | – | Protocol (TCP, UDP, ICMP) |
| `act` | – | Action taken (`blocked` / `allowed`) |
| `deviceDirection` | – | `0` = inbound, `1` = outbound |
| `in` / `out` | – | Bytes received / sent |
| `cs1` | CrimeScore | OneFirewall risk score of the remote IP (0–100) |
| `cs2` | ThreatCategory | e.g. C2, Scanning, Botnet, BruteForce, None |
| `cs3` | PolicyName | Policy that matched the connection |
| `cn1` | RuleID | ID of the rule that matched |

### Signature IDs

| Signature ID | Name | Default severity |
| - | - | - |
| `NET-1000` | Connection allowed | 2 |
| `NET-1001` | Connection blocked – malicious IP | 8 |

***

## 4. b) CTI Metrics

### Example – Periodic summary (5-minute window)

```
CEF:0|OneFirewall|WCF Agent|2.4|CTI-2001|CTI metrics summary|3|rt=Nov 16 2026 09:45:00 UTC start=Nov 16 2026 09:40:00 UTC end=Nov 16 2026 09:45:00 UTC dvchost=wcf-agent-01 cn1Label=TotalConnections cn1=184233 cn2Label=BlockedConnections cn2=1271 cn3Label=UniqueMaliciousIPs cn3=311 cs1Label=TopThreatCategory cs1=Scanning cs2Label=FeedVersion cs2=2026.11.16-0900 cs3Label=TopSourceCountry cs3=CN cfp1Label=BlockRatePct cfp1=0.69
```

### Example – Per-indicator metric (single malicious IP)

```
CEF:0|OneFirewall|WCF Agent|2.4|CTI-2002|Malicious IP activity|7|rt=Nov 16 2026 09:45:00 UTC start=Nov 16 2026 09:40:00 UTC end=Nov 16 2026 09:45:00 UTC dvchost=wcf-agent-01 src=203.0.113.47 cs1Label=CrimeScore cs1=92 cs2Label=ThreatCategory cs2=C2 cs3Label=FirstSeen cs3=2026-11-14T22:10:05Z cn1Label=HitCount cn1=148 cn2Label=BlockedCount cn2=148 cn3Label=DistinctInternalHosts cn3=3
```

### Field reference – Summary (`CTI-2001`)

| CEF key | Label | Description |
| - | - | - |
| `start` / `end` | – | Aggregation window |
| `cn1` | TotalConnections | Connections evaluated in the window |
| `cn2` | BlockedConnections | Connections blocked in the window |
| `cn3` | UniqueMaliciousIPs | Distinct malicious IPs seen |
| `cs1` | TopThreatCategory | Most frequent threat category |
| `cs2` | FeedVersion | CTI feed version in use |
| `cs3` | TopSourceCountry | Most frequent country of malicious sources |
| `cfp1` | BlockRatePct | Percentage of connections blocked |

### Field reference – Per indicator (`CTI-2002`)

| CEF key | Label | Description |
| - | - | - |
| `src` | – | Malicious IP |
| `cs1` | CrimeScore | OneFirewall risk score (0–100) |
| `cs2` | ThreatCategory | Threat category |
| `cs3` | FirstSeen | First time the IP was seen by the agent |
| `cn1` | HitCount | Connection attempts in the window |
| `cn2` | BlockedCount | Attempts blocked |
| `cn3` | DistinctInternalHosts | Internal hosts involved |

***

## 5. Customization

The formats above are **default templates**. From the OneFirewall central console you can adapt them to your SIEM, use cases and data volumes:

| What can be customized | Examples |
| - | - |
| **Fields included** | Add or remove fields (e.g. drop byte counters, add geo-location or ASN) |
| **Field mapping and labels** | Rename `csXLabel` / `cnXLabel`, or move a value to a different CEF key |
| **Event types sent** | Send only blocked events, only CTI metrics, or both |
| **Filters** | Send only events above a given CrimeScore or for specific threat categories |
| **Severity mapping** | Change the severity assigned to each Signature ID |
| **CTI aggregation interval** | e.g. 1, 5, 15 or 60 minutes |
| **Header values** | Device Vendor / Product / Signature IDs to match existing SIEM parsers |
| **Destination and transport** | Collector IP/port, Syslog over UDP, TCP or TLS |

Changes are applied centrally and pushed to the agents, with no reinstall needed.

We can work with your team to agree the final mapping for your SIEM.

***

## 6. Technical Notes

* **Custom slots:** CEF provides `cs1–cs6` (strings), `cn1–cn3` (numbers) and `cfp1–cfp4` (floats). If more fields are needed, they can be split into separate events or sent as vendor-specific keys, which are supported by the main SIEMs (ArcSight, Microsoft Sentinel, QRadar, Splunk).
* **Escaping:**
  * Header: `|` → `\|`, `\` → `\\`
  * Extension: `=` → `\=`, `\` → `\\`
* **Severity scale:** 0–3 Low, 4–6 Medium, 7–8 High, 9–10 Very High
* **Transport:** Syslog (RFC 5424 / RFC 3164), default ports 514 (UDP/TCP) or 6514 (TLS)

***

*IP addresses in the examples use documentation (RFC 5737) and private ranges.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.