Data source catalog

Every source XenXDR recognises for detection, with the status of each.

Detections declare which data sources they need. This is the catalog those declarations draw from, with the input each source arrives through.

Endpoint and operating system

SourceArrives throughNotes
Windows process creationAgent (Sysmon, Security log)Process-based content-pack rules need Sysmon.
Windows Security logAgentLogons, account and privilege events.
Windows SysmonAgentAll Sysmon event types the host's configuration emits.
Windows PowerShell script blocksAgentRequires script block logging enabled by policy.
Microsoft Defender AntivirusAgentDetections and protection state.
XenXDR agent telemetryAgentHeartbeat, containment, tool availability, response actions.
Linux auditdAgent or syslogRequires the recommended rules for full coverage.
Linux syslog and journaldAgent or syslog

Network

SourceArrives throughNotes
Firewall, FortiGateSyslogNative format recognised; response action available.
Firewall, other vendorsSyslog (CEF or LEEF)Header and CEF fields parsed; vendor extensions under fields.
DNS queriesAgent (Sysmon) or syslog
Network connectionsAgent (Sysmon)Connection records with process attribution.

Identity and cloud

SourceArrives throughStatus
Okta System LogPull connectorLive
Microsoft Entra ID sign-ins and auditPull connectorLive
Microsoft 365Pull connectorLive
Fluence Account audit logPush with an ingest keyLive
AWS CloudTrailPull connectorComing soon
CrowdStrike FalconPull connectorComing soon
Microsoft Defender for EndpointPull connectorComing soon
Google WorkspacePull connectorComing soon

"Coming soon" means the connector can be configured in the console but does not yet collect. It is shown with that label there too.

Everything else

Any JSON, HEC or syslog sender lands in the store with its fields preserved. Detections can be written against them with the event.module value the sender uses. Ask support if you want a source promoted to the catalog with a native mapping.