OneFirewall vs Microsoft Sentinel: less ingest, more context.
Microsoft Sentinel detects and investigates across your Microsoft and third-party data. OneFirewall blocks attackers the Alliance has already confirmed, at your firewalls and WAFs, and sends Sentinel enriched CEF events and STIX indicators.
SIEM · Last reviewed: 20 November 2026
Sentinel and OneFirewall are complementary. Sentinel is a cloud-native SIEM and SOAR: analytics rules, incidents and Logic App playbooks over a Log Analytics workspace. OneFirewall blocks known attackers before they reach you, so Sentinel ingests less perimeter noise, and gives Sentinel Crime Score and ATT&CK context on what remains.
A SIEM built on Log Analytics
Microsoft Sentinel stores data in a Log Analytics workspace, brought in by data connectors: native ones for Microsoft services, and standard ones such as Common Event Format (CEF) via AMA, which writes to the CommonSecurityLog table. Analytics rules written in KQL create incidents; automation rules and Logic App playbooks respond.
Threat intelligence comes in through the Threat Intelligence – TAXII connector or the upload API, and analytics rules match indicators against your logs. Sentinel is billed mainly on data ingested, so every perimeter event has a direct cost.
- Deep integration with Defender XDR, Entra ID and Azure
- KQL analytics and playbook automation
- Ingest-based pricing makes noisy sources expensive
- Blocking happens through playbooks, after an incident
CEF into CommonSecurityLog, STIX into threat intelligence
OneFirewall uses Sentinel's standard connectors, so no custom parser or function app is needed.
Connect the events
Enable the CEF via AMA connector and point the WCF Agent's syslog output at your forwarder. OneFirewall events land in CommonSecurityLog, with Crime Score and threat category in the DeviceCustomString fields.
Connect the indicators
Add the OneFirewall TAXII 2.1 server in the Threat Intelligence – TAXII connector. Indicators become available to Sentinel's TI matching analytics.
Hunt and visualise
Use KQL to report what OneFirewall blocked, by category and source, or join OneFirewall IPs against sign-in and firewall logs.
Block upstream
The WCF Agent pushes the same intelligence to your firewalls and WAFs, including Azure-adjacent controls, so known attackers are dropped without waiting for a playbook.
What the configuration looks like
// Sentinel: "Common Event Format (CEF) via AMA" connector -> CommonSecurityLog CommonSecurityLog | where DeviceVendor == "OneFirewall" | extend CrimeScore = toint(DeviceCustomString1), Category = DeviceCustomString2 | where DeviceAction == "blocked" | summarize Blocked = count(), Attackers = dcount(SourceIP) by Category, bin(TimeGenerated, 1h)
The CEF field mapping is documented in the event format reference; all fields are configurable from the OneFirewall console.
Microsoft Sentinel and OneFirewall, capability by capability
| Capability | Microsoft Sentinel | OneFirewall |
|---|---|---|
| Primary job | Collect, detect, investigate and automate response | Block attackers already confirmed by the Alliance, at your existing controls |
| Intelligence | Microsoft threat intelligence plus feeds you connect | Live, scored indicators from 290+ organisations |
| From detection to block | Incident, then automation rule or Logic App | Automatic at firewall, IPS and WAF in under 30 seconds |
| Cost driver | Data ingested into Log Analytics | Per device; doesn't grow with log volume |
| Onboarding | Connector per source | Standard CEF via AMA and TAXII connectors |
| Event context | Depends on the source | Crime Score, threat category, country and ATT&CK technique |
What OneFirewall adds to Microsoft Sentinel
Lower ingest from the perimeter
Attackers dropped at the edge don't produce the firewall and WAF events you'd otherwise pay to ingest.
Indicators with a confidence you can see
Each indicator comes with a Crime Score backed by multi-member confirmation, so TI matches are worth an analyst's time.
Prevention that doesn't wait for a playbook
Known attackers are blocked continuously, not after an incident fires and a Logic App runs.
- Detection across Microsoft 365, Entra ID, Azure and Defender XDR
- UEBA and investigation of behaviour inside your tenant
- Incident management and automated response playbooks
- Long-term retention and compliance reporting
OneFirewall doesn't store your logs. It sends Sentinel less noise and better context.
OneFirewall and Microsoft Sentinel: FAQ
Which Sentinel connector does OneFirewall use?
Common Event Format (CEF) via AMA for events, which writes to CommonSecurityLog, and Threat Intelligence – TAXII for indicators.
Where does the Crime Score appear?
In the CEF custom string fields, which map to DeviceCustomString1 and its label in CommonSecurityLog. Labels are configurable.
Can it reduce my Sentinel bill?
It can reduce perimeter events, because known attackers are blocked before they generate them. A Proof of Value measures how much on your own traffic.
Does OneFirewall replace Sentinel?
No. Sentinel stays your SIEM and SOAR. OneFirewall adds prevention upstream and context to Sentinel's data.
