OneFirewall vs IBM QRadar: fewer offenses, richer context.
QRadar correlates events into offenses for your SOC to investigate. OneFirewall blocks attackers the Alliance has already confirmed, at your firewalls, and sends QRadar normalised CEF events with Crime Score and MITRE ATT&CK context.
SIEM · Last reviewed: 20 November 2026
QRadar and OneFirewall are complementary. QRadar is the correlation and investigation engine. OneFirewall is the intelligence and prevention layer in front of it: it removes known attackers at the perimeter, so they don't generate events and offenses, and enriches what QRadar does see.
DSMs, rules and offenses
IBM QRadar SIEM collects events and flows from log sources, normalises them with Device Support Modules (DSMs) and runs them through its Custom Rule Engine. Matching rules and building blocks raise offenses, which group related activity for analysts. Reference sets hold watchlists, such as malicious IPs, that rules can test against.
QRadar is usually licensed by events per second (EPS) and flows per minute, so high-volume perimeter noise affects both capacity and analyst workload. Like any SIEM, it detects; blocking requires an analyst or SOAR.
- Strong normalisation and correlation across many log sources
- Reference sets let rules match threat intelligence
- EPS-based capacity makes noise expensive
- Detection, not prevention
A Universal CEF log source, plus intelligence and syslog
Everything uses QRadar features you already have. No custom DSM is needed.
Add a log source
In Admin › Log Sources, add a Universal CEF source for the WCF Agent over UDP syslog. Events are normalised and categorised automatically, with Crime Score, threat category and ATT&CK technique as custom properties.
Load the indicators
Pull OneFirewall indicators over TAXII 2.1 (for example with QRadar's threat intelligence app) into reference sets, and use them in rules and searches.
Forward QRadar data (optional)
Add a syslog destination for the WCF Agent on UDP 514. OneFirewall scores the connections and shows which allowed traffic came from known attackers.
Block at the edge
The WCF Agent pushes the same intelligence to your firewalls and WAFs, so known attackers are stopped before they produce events and offenses.
What the configuration looks like
# QRadar: Admin > Log Sources > Add Log Source Type: Universal CEF Protocol: Syslog (UDP 514) Identifier: <wcf-agent-ip> # Example event as QRadar receives it CEF:0|OneFirewall|WCF Agent|2.4|NET-1001|Outbound connection blocked - malicious destination|8| src=10.20.1.15 dst=203.0.113.47 dpt=443 act=blocked cs1Label=CrimeScore cs1=847 cs2Label=ThreatCategory cs2=C2
Event formats are documented on the OFA Events page and in the CEF reference.
QRadar and OneFirewall, capability by capability
| Capability | IBM QRadar | OneFirewall |
|---|---|---|
| Primary job | Normalise, correlate and raise offenses | Block attackers already confirmed by the Alliance, at your existing controls |
| Threat intelligence | Reference sets and feeds you configure | Live, scored indicators from 290+ organisations |
| From offense to block | Analyst or SOAR action | Automatic at firewall, IPS and WAF in under 30 seconds |
| Capacity | Licensed by EPS and flows | Per device; doesn't grow with event volume |
| Onboarding | DSM per log source | Universal CEF, no custom parser |
| Event context | Depends on the source | Crime Score, members seen, country and ATT&CK technique |
What OneFirewall adds to QRadar
Fewer low-value offenses
Known scanners and brute-forcers dropped at the edge don't generate events, so they don't raise offenses.
Intelligence your rules can trust
Reference sets filled with multi-member-confirmed indicators produce fewer false positives than raw open-source lists.
Prevention without waiting for a rule
Blocking doesn't depend on an offense being raised and actioned. It happens continuously at the firewall.
- Correlation across identity, endpoint, network and cloud events
- Offense management and investigation
- Flow analysis and network anomaly detection
- Compliance reporting and log retention
OneFirewall doesn't replace your SIEM. It reduces the noise that reaches it and adds context to what remains.
OneFirewall and QRadar: FAQ
How does QRadar receive OneFirewall events?
Add a Universal CEF log source for the WCF Agent over UDP syslog. Events are normalised and categorised automatically.
Can QRadar rules use OneFirewall indicators?
Yes. Indicators are available as STIX 2.1 over TAXII 2.1 and can be loaded into reference sets for rules and searches.
Can OneFirewall analyse logs already in QRadar?
Yes. Configure a syslog destination to the WCF Agent on UDP 514 and OneFirewall scores those connections.
Does OneFirewall replace QRadar?
No. QRadar stays your SIEM. OneFirewall blocks known attackers upstream and enriches QRadar's events.
