Datasets and Presets

The Cortex XDR XQL query language supports built-in datasets, custom datasets, and presets.
Every XQL query begins by identifying a data source that the query will run against. Each data source has a unique name, and a series of fields. Your query specifies the data source, and then provides stages that identify fields of interest and perform operations against those fields.
You can query against either datasets or presets.

Datasets

The standard, built-in data source that is available in every Cortex XDR instance is the
xdr_data
dataset. This is a very large dataset with many hundreds of available fields. See the
Cortex XDR XQL Schema Reference
for information about this dataset.
This dataset is comprised of both raw EDR events reported by the Cortex XDR agent, and of logs from different sources such as third-party logs. To help you investigate events more efficiently, Cortex XDR also stitches these logs and events together into common schemas called
stories
. These stories are available using the Cortex XDR presets.
You use the
dataset
keyword to specify a dataset on your query.
You can create a custom dataset using the Target stage.
Depending on your integrations, you might also have the following datasets available for queries:
Ingested Data
Dataset
AWS CloudTrail and Amazon CloudWatch
<Vendor>_<Product>_raw
Azure AD
azure_ad_raw
Checkpoint FW1/VPN1
<Vendor>_<Product>_raw
Cisco ASA
cisco_asa_raw
Corelight Zeek
corelight_zeek_raw
CSV logs in shared Windows directory
Custom datasets—Select from pre-existing user-created datasets or add a new dataset.
Elasticsearch Filebeat
<Vendor>_<Product>_raw
Fortinet Fortigate
<Vendor>_<Product>_raw
Google Cloud Platform (GCP) logs
google_cloud_raw
Google Kubernetes Engine (GKE)
<Vendor>_<Product>_raw
JSON or text logs from third-party source over HTTP
<Vendor>_<Product>_raw
Okta
okta_sso_raw
PANW EDR
xdr_data
PANW NGFW
panw_ngfw_*_raw
Current supports threat, traffic, URL, and hipmatch logs only. These datasets use the query field names as described in the Cortex schema documentation.
PingFederate
ping_identity_pingfederate_raw
PingOne for Enterprise
pingone_sso_raw
Syslog/CEF
<CEFVendor>_<CEFProduct>_raw
Windows Event Collector (WEC)
xdr_data
Windows DHCP using Elasticsearch Filebeat
windows_dhcp_raw
Zscaler Cloud Firewall
<Vendor>_<Product>_raw
Dataset names can use uppercase characters, but in queries dataset names are always treated as if they are lowercase.
Upon ingestion, all fields are retained even fields with a null value. You can also use the Cortex XDR XQL query language to query ingestion rules for null values.

Presets

Presets offer groupings of xdr_data fields that are useful for analyzing specific areas of network and endpoint activity. All of the fields available for a preset are also available on the larger xdr_data dataset, but by using the preset your query can run more efficiently.
Two of the available presets are
stories
. These contain information stitched together from Cortex XDR agent events and log files to form a common schema. They are
authentication_story
and
network_story
.
You use the
preset
keyword to specify a dataset on your query.
See the Cortex XDR XQL Schema Reference for information about the presets available to you, including the fields available for each preset.

Recommended For You