> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xdr-agent/9.4-cortex-xdr-agent-admin-guide/introduction.md). # Introduction Learn about the Cortex XDR Agent installation procedures. Cortex XDR agent is installed on all endpoints in your organization. It works in conjunction with your Cortex platform to monitor and protect these endpoints from a wide range of security threats. The agent collects and sends endpoint telemetry data to the Cortex server, where it is analyzed for suspicious activities, indicators of compromise, and potential security incidents. The Cortex XDR agent plays a crucial role in providing real-time visibility into endpoint activity, detecting and blocking malware, analyzing endpoint behavior for signs of compromise, and facilitating response actions. It helps security teams identify and respond to threats effectively, minimizing the risk of data breaches and unauthorized access. The Cortex XDR agent communicates with the server at a 5-minute heartbeat interval to send status information and retrieve the latest security policy. This guide explains the installation and configuration procedures for Cortex XDR agent setup and operation on, Windows, MacOS, and Linux operating systems. Additional guides are available for agent installation and operation on Android and iOS devices. ## Agent types The Cortex XDR agent comes in three types. They differ in which capabilities run on the endpoint and how many of the endpoint's resources they use. You choose the agent type when you create the installation package, and the agent keeps it after installation. * **Standard:** Complete security coverage with all Cortex XDR capabilities. * **Cloud Optimized:** Low footprint for essential runtime security on Linux cloud workloads, such as virtual machines and Kubernetes nodes. * **Targeted:** A modular sensor that runs specific capabilities, such as Agentic Endpoint Security (AES), without the full set of Cortex XDR capabilities. | | Standard | Cloud Optimized | Targeted | | ------------------------------ | --------------------------------------- | --------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | **Platforms** | All supported platforms | Linux | Windows, macOS, and Linux | | **Capabilities** | All Cortex XDR capabilities | Essential runtime protection and detection for cloud workloads. | AES (Windows, macOS, and Linux). Active Directory Security Posture Management (AD-SPM) (Windows only) | | **Installation package types** | All | Standalone, Kubernetes, and Helm | Standalone | | **Minimum agent version** | See the Cortex XDR Compatibility Matrix | 9.4 | 9.4 | | **Linux operation mode** | Kernel or User mode (eBPF) | User mode (eBPF) | User mode, with no active modules | For more information about Cloud Optimized agents, see [Cloud Optimized agent for Linux](/cortex-xdr-agent/9.4-cortex-xdr-agent-admin-guide/cortex-xdr-agent-for-linux/cloud-optimized-agent-for-linux.md). #### Targeted agents * **Requirements:** Agent 9.4 or later. AES is available on Windows, macOS, and Linux. AD-SPM is available on Windows only. * **Install:** [Create a Standalone installation package](/cortex-xdr/protect-your-endpoints/install-and-manage-endpoints/create-an-agent-installation-package.md) and select **Targeted** under **Agent Type**. Only agent versions 9.4 and later are listed. Then install the package the same way as a Standard agent for the endpoint's operating system. * **Change agent type:** For full Cortex XDR capabilities, you can change your Targeted agent type to Standard from the Cortex XDR management console without reinstalling it. For more information on changing an agent type, see [Change a Cortex XDR agent type](/cortex-xdr/protect-your-endpoints/install-and-manage-endpoints/set-up-endpoint-protection/change-an-agent-type.md). {% hint style="info" %} #### Note The agent console is not available to end users on Targeted agents for Windows and macOS. {% endhint %} For compatibility with operating systems per agent release versions see the [Cortex XDR Compatibility Matrix](/compatibility-matrix/where-can-i-install-the-cortex-xdr-agent.md). With every Cortex product release, new agent features are released with specific agent versions. For feature support, known and addressed issues, and changes to default behavior by Cortex XDR agent version, see the [Cortex XDR Agent Releases](/agent-release-notes/cortex-xdr-agent-releases/readme.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-xdr-agent/9.4-cortex-xdr-agent-admin-guide/introduction.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.