OneFirewall vs Check Point: ThreatCloud plus the Alliance.
Check Point Quantum gateways enforce with ThreatCloud AI behind them. OneFirewall adds a second, independent intelligence source: IPs, domains, URLs and file hashes confirmed by 290+ organisations, delivered through Check Point's own External Feeds or blocked at SecureXL speed.
Firewalls & NGFW · Last reviewed: 20 November 2026
Check Point and OneFirewall are complementary. ThreatCloud AI powers Check Point's IPS, Anti-Bot and Threat Emulation blades with Check Point's own research. OneFirewall feeds Alliance indicators into the same Threat Prevention policy, or straight into the SecureXL fast path, so the gateway also blocks attackers that other members, running other vendors, have already confirmed.
Software Blades, ThreatCloud AI and the SecureXL fast path
A Check Point Quantum Security Gateway runs Software Blades on Gaia OS: Firewall, IPS, Anti-Bot, Anti-Virus, URL Filtering and Threat Emulation (SandBlast). Their verdicts come from ThreatCloud AI, Check Point's cloud intelligence service, and everything is managed centrally in SmartConsole.
Two features matter for third-party intelligence. External Feeds (Threat Prevention › Indicators) let a gateway download custom indicators and enforce them in Threat Prevention. SecureXL is the acceleration layer: entries in its SAM (Suspicious Activity Monitor) table are dropped before policy lookup, at hardware speed.
- Deep inspection blades, sandboxing and central policy management
- ThreatCloud AI intelligence is Check Point's own
- External Feeds accept IP, domain, URL and file-hash indicators
- SecureXL SAM entries are the fastest way to drop a source on a gateway
Three ways in, depending on how you run Check Point
OneFirewall supports Check Point in API mode (no agent) and agent mode. Most members start with External Feeds and add SecureXL for high-volume perimeters.
External Feeds (API mode)
In SmartConsole, create four External Feeds (IP, domain, URL and file hash) pointing at the Alliance API with your JWT as the Authorization: Bearer header and a 5-minute refresh. Use them in a Threat Prevention rule with action Prevent, Drop or Reject.
Management API group (agent mode)
The WCF Agent keeps a network group object (for example OneFirewall_IPS) up to date through the Check Point management API, on the domain, policy and gateways you specify, and installs policy.
SecureXL SAM (agent mode)
For the fastest path, the agent pushes IPs above your Crime Score threshold into the SAM table on each gateway or VSID. Traffic is dropped before policy lookup, and the block is removed automatically when the score decays.
What the configuration looks like
// WCF Agent config.json (agent-based mode: SecureXL / SAM)
"ips": {
"checkpoint_securexl": {
"active": true,
"connections": "ofa@<gateway-address>",
"password": "********",
"command": "bash artifacts/checkpoint/install-securexl.sh",
"vsids": "1,2"
}
}
// API mode instead: SmartConsole > Security Policies > Threat Prevention >
// Indicators > External Feeds (IP, domain, URL, hash; JWT Bearer; 5 min)
Requirements: Gaia R80.10 or later (R80.40 to R82 for SecureXL), outbound HTTPS 443 to app.onefirewall.com, and a OneFirewall API token.
Check Point and OneFirewall, capability by capability
| Capability | Check Point Quantum | OneFirewall |
|---|---|---|
| Primary job | Inspect and enforce: firewall, IPS, Anti-Bot, sandboxing | Decide which IPs, domains, URLs and hashes should be blocked, based on live Alliance data |
| Intelligence source | ThreatCloud AI (Check Point research and telemetry) | 290+ independent organisations across sectors and firewall vendors |
| Indicator types | Signatures, reputations, sandbox verdicts | IP, domain, URL and MD5/SHA1/SHA256 file hashes, each with a Crime Score |
| Enforcement path | Threat Prevention policy, IPS, Anti-Bot | External Feeds in Threat Prevention, a managed group in Access policy, or SecureXL SAM drops before policy lookup |
| Stale blocks | Custom indicators stay until removed | Removed automatically when the Crime Score decays below your threshold |
| Multi-vendor estates | Check Point gateways | The same intelligence reaches Fortinet, Palo Alto, cloud WAFs and SIEMs |
What OneFirewall adds to Check Point
A second opinion ThreatCloud doesn't have
Alliance members report what actually hits their perimeters, whichever vendor they run. That cross-vendor view is not in any single vendor's cloud.
Blocking that costs no inspection
SecureXL SAM drops happen before the rulebase and blades. Known-bad sources stop consuming IPS and Threat Emulation capacity.
No more hand-built blocklists
Engineers stop pasting IPs into groups. Feeds refresh every five minutes, and expired indicators clean themselves up.
- IPS signatures and exploit protection inside allowed traffic
- Threat Emulation and Extraction for unknown files
- Application Control, URL Filtering and identity-aware policy
- Central management, logging and compliance reporting in SmartConsole
Full setup steps for each method are in the Check Point and SecureXL integration guides.
OneFirewall and Check Point: FAQ
Which Check Point versions are supported?
External Feeds work on Gaia R80.10 through R82. The SecureXL SAM integration supports R80.40, R81, R81.10, R81.20 and R82.
Do I need to install anything on the gateway?
Not for External Feeds, which use native SmartConsole objects. The SecureXL and management-API methods use the WCF Agent, which runs on a separate VM and connects to your management server.
What indicator types can Check Point consume from OneFirewall?
Four feeds: malicious IPs, domains, URLs and file hashes (MD5, SHA1, SHA256), each added as a separate External Feed.
Does OneFirewall replace ThreatCloud?
No. ThreatCloud keeps powering your blades. OneFirewall adds Alliance-confirmed indicators that come from outside Check Point's customer base.
