> 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/compatibility-matrix/cortex-xdr-agent-compatibility-with-third-party-security-products.md). # Cortex XDR agent compatibility with third-party security products Review the considerations related to third-party security software integration with Cortex XDR agent software. This information outlines important considerations regarding the integration of third-party security software with Cortex XDR agent software. The following tables detail the supported security products that can run alongside Cortex XDR, along with their known limitations or the required additional actions to ensure proper integration with Cortex XDR agents. It is important to note that while other third-party applications may be compatible with Cortex XDR agents, Palo Alto Networks has not conducted compatibility testing on these products. Customers who intend to install such applications alongside Cortex XDR agents are advised to perform thorough internal testing to ensure there are no conflicts or performance issues. Cortex XDR agent does not require broad preemptive exceptions for common server roles and enterprise workloads (such as Exchange, Hyper-V, Database Engines.) Exceptions should only be used if specific issues arise. Should you encounter any problems during the integration process with the following third-party security software, please contact your support team for assistance. --- # 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/compatibility-matrix/cortex-xdr-agent-compatibility-with-third-party-security-products.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.