Deployment
Cloud-native SaaS only
agent installs in minutes per endpoint
SaaS is standard; on-premises deployment available
uncommon among major EDR vendors
Cloud-managed via Microsoft 365 Defender portal
agent deployment via Intune, Group Policy, or System Center
Self-hosted (all-in-one server, single-node, or multi-node cluster) or Wazuh Cloud SaaS
Self-hosted; runs as a daemon (clamd) or command-line scanner; commonly…
integrated into Postfix/Sendmail mail flow
Cloud-managed SaaS console or on-premises GravityZone Control Center for self-hosted
Typical deployment time
Minutes per endpoint
enterprise-wide rollout typically days to weeks
Same-day for small deployments
multi-week phased rollouts for thousands of endpoints
Hours for Windows-centric M365-licensed organizations
longer when consolidating multiple endpoint vendors
All-in-one PoC
hours; production multi-node cluster: days to weeks (DevOps/security engineering required)
Minutes to hours for basic setup
production integration depends on the host system (mail gateway, file scanner, etc.)
Hours for SMB deployments
days to weeks for distributed enterprise rollouts
Key integrations
Splunk, IBM QRadar, ServiceNow, Jira, Palo Alto XSOAR, AWS Security Hub,…
Microsoft Sentinel, Okta, Zscaler
Splunk, IBM QRadar, ServiceNow, Cortex XSOAR, Okta, Microsoft Sentinel, AWS, Azure, Slack
Microsoft Sentinel, Entra ID, Intune, Purview, Defender for Cloud, Office 365
third-party connectors via Microsoft Graph Security API
VirusTotal, MISP, TheHive, Cortex, Slack, PagerDuty, ServiceNow, Splunk…
forwarder, Elastic, Suricata; OSSEC-compatible rules
Postfix, Sendmail, Exim, ProFTPD, Squid, Amavis, ClamWin (Windows GUI)
third-party signature feeds available (e.g., SecuriteInfo)
Microsoft 365, Active Directory, Azure AD, AWS, Splunk, ServiceNow, Microsoft…
Sentinel, MISP