Rolling tokens in Cortex XDR are used to perform administration on agents without relying on static credentials. This improves security by providing time-limited, automatically rotating tokens that maintain agent management access without exposing long-lived credentials.

The "partially protected" status on a Linux endpoint typically occurs when the kernel modules fail to load because of unsupported kernel versions or when the agent is outdated and requires an upgrade. Both conditions prevent the agent from providing full protection capabilities.

For upgrading a non-Linux Kubernetes cluster, the correct installer type is Helm, since Helm charts are the supported method for deploying and managing Cortex XDR agents in Kubernetes environments.

The URL https:// -docker.pkg.dev is used in Palo Alto Networks infrastructure to download Engine Docker containers. This ensures the Cortex XSIAM engine components are pulled securely from the regional Docker registry.

For Cortex XDR agents to use the Broker VM as a download source, the Agent Settings profile must specify the Broker VM as the update source, and the Broker VM must be configured with an FQDN so agents can reliably resolve and connect to it.

To prevent Cortex XSIAM from automatically extracting indicators (like IPs, domains, and URLs) from a script’s output, you must use 'AutoExtract': False in the script. This disables the auto-extraction mechanism for that script.

The MODEL section in a data model rule is used to map log fields to the corresponding Cortex XSIAM Data Model (XDM) fields. This ensures that ingested data aligns with XDM, enabling consistent analytics, detections, and queries across different data sources.