CEFOver syslog
6Event categories
MITREATT&CK mapped
STIX 2.1Over TAXII 2.1
The short answer

Splunk and OneFirewall do different jobs. Splunk is a SIEM: it collects your logs, runs correlation searches and helps analysts investigate. OneFirewall is an intelligence and enforcement layer: it blocks known attackers at your existing firewalls and WAFs. Together, Splunk sees fewer noisy perimeter events and gets Crime Score and ATT&CK context on the ones that matter.

How Splunk works

Index everything, search with SPL, alert on correlations

Splunk Enterprise and Splunk Cloud ingest machine data from any source, index it and make it searchable with SPL. Splunk Enterprise Security adds correlation searches, risk-based alerting, a threat intelligence framework and investigation workflows; Splunk SOAR adds playbook automation.

Splunk detects; it doesn't block. Turning an alert into a firewall rule needs an analyst or a SOAR playbook. And because licensing is typically based on ingest or compute, every perimeter scan and brute-force attempt you index has a cost.

  • Excellent search, correlation and investigation across all your data
  • Threat intelligence matching relies on the feeds you bring
  • Blocking needs a human or a SOAR playbook
  • Perimeter noise drives both ingest cost and alert fatigue
The integration

Events into Splunk, intelligence both ways

OneFirewall connects to Splunk through standard interfaces: CEF over syslog for events, STIX/TAXII for indicators, and syslog from Splunk to OneFirewall if you want your Splunk data scored.

STEP 1

Receive OneFirewall events

Configure a UDP syslog input (or a forwarder) for the WCF Agent with sourcetype=cef. Network events, enforcement decisions, agent lifecycle and CTI metrics arrive with Crime Score, threat category and MITRE ATT&CK technique as fields.

STEP 2

Bring in the indicators

Pull OneFirewall indicators from the TAXII 2.1 server into Splunk ES threat intelligence (or a TAXII-capable add-on) so correlation searches can match them against all your data.

STEP 3

Score your Splunk data (optional)

Forward selected logs from Splunk to the WCF Agent on UDP 514. OneFirewall scores every connection and shows which allowed traffic came from known attackers.

STEP 4

Let the firewall do the blocking

The WCF Agent pushes the same intelligence to your firewalls and WAFs, so known attackers are dropped automatically instead of waiting for a notable and a playbook.

What the configuration looks like

# inputs.conf on the forwarder / indexer that receives the WCF Agent
[udp://514]
connection_host = ip
sourcetype = cef

# SPL: what OneFirewall blocked at the edge, by threat category
index=* sourcetype=cef "CEF:0|OneFirewall" act=blocked
| stats count dc(src) AS attackers BY cs2
| sort - count

CEF fields, labels, severity and destination are all configurable from the OneFirewall console. See OFA Events for the full event reference.

Side by side

Splunk and OneFirewall, capability by capability

CapabilitySplunk (Enterprise Security)OneFirewall
Primary jobCollect, search, correlate and investigate your dataBlock attackers already confirmed by the Alliance, at your existing controls
Where intelligence comes fromYour logs plus feeds you subscribe toLive attack observations from 290+ organisations
From detection to blockingAlert, then analyst or SOAR actionNative block rules on firewall, IPS and WAF in under 30 seconds
Effect on SOC noiseEvery scan and brute-force attempt can be indexed and alerted onKnown-bad sources are dropped at the edge before they generate events
Pricing driverIngest volume or computePer device; doesn't grow with log volume
Event contextWhatever your sources includeCrime Score, threat category, country and ATT&CK technique in every event
The added value

What OneFirewall adds to Splunk

Fewer notables, same coverage

When known attackers are dropped at the perimeter, the scans and brute-force attempts behind many low-value notables never happen.

Better triage context

Every OneFirewall event carries a Crime Score, how widely the source has been seen and the ATT&CK technique, so analysts prioritise faster.

Prevention without a playbook

Blocking known attackers no longer depends on a SOAR flow firing correctly. It's done at the firewall, continuously.

Where Splunk is still the right tool
  • Insider threats and unusual behaviour inside your network
  • Long-term retention, compliance reporting and forensics
  • Correlation across identity, endpoint, cloud and application logs
  • Investigation of new attacks from infrastructure no member has seen yet

OneFirewall doesn't store or search your logs. It makes the data in Splunk smaller and more useful.

FAQ

OneFirewall and Splunk: FAQ

Does OneFirewall replace Splunk?

No. Splunk remains your SIEM. OneFirewall blocks known attackers at your firewalls and sends Splunk enriched CEF events and STIX/TAXII indicators.

How do OneFirewall events reach Splunk?

As CEF over UDP syslog. Configure a UDP input with sourcetype=cef and the fields are parsed automatically.

Can Splunk use OneFirewall indicators in correlation searches?

Yes. Indicators are available as STIX 2.1 over a TAXII 2.1 server, which Splunk ES threat intelligence or a TAXII-capable add-on can ingest.

Will it reduce my Splunk ingest?

It can: sources blocked at the edge generate fewer downstream events. How much depends on how much perimeter noise you index today; a Proof of Value measures it on your traffic.

See what Splunk lets through today.

A free Proof of Value runs against your own traffic. Nothing leaves your perimeter.

Start a Free PoV