> 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-agentix/configure-cortex-agentix/cortex-agentix-data-sources-and-connectors/vendor-specific-data-sources-and-connectors/proofpoint/proofpoint.md).

# Proofpoint

Use Proofpoint data for Cortex AgentiX.

{% hint style="warning" %}
**Important**

This connector is only available for tenants that onboarded after July 26, 2026. For tenants that onboarded before this date, use Marketplace to access the standalone integration. For more information, see [Marketplace](/cortex-agentix/configure-cortex-agentix/marketplace.md).
{% endhint %}

Proofpoint is an email security and threat protection platform that guards against phishing, malware, and advanced email attacks. It includes Targeted Attack Protection (TAP), Threat Response for automated issue response, Protection Server for email gateway management, Cloud Threat Response, Browser Isolation, and URL phishing validation via IsItPhishing.

This connector includes the following sub-capabilities (Marketplace integrations link to PAN DEV for more information):

* [IsItPhishing](https://xsoar.pan.dev/docs/reference/integrations/is-it-phishing): Collaborative web service that provides validation on whether a URL is a phishing page or not by analyzing the content of the webpage. This connector is available with any active Cortex XSIAM or Cortex AgentiX license.
* Proofpoint Cloud Threat Response: Fetches Proofpoint Cloud Threat Response (CTR) incidents into Cortex XSIAM for case management, and exposes commands to list and retrieve incident details. This connector is available with any active Cortex XSIAM or Cortex AgentiX license.
* [Proofpoint Protection Server v2](https://xsoar.pan.dev/docs/reference/integrations/proofpoint-protection-server-v2): Proofpoint email security appliance. This connector is available with any active Cortex XSIAM or Cortex AgentiX license.
* [Proofpoint TAP v2](https://xsoar.pan.dev/docs/reference/integrations/proofpoint-tap-v2): Use the Proofpoint Targeted Attack Protection (TAP) integration to protect against and provide additional visibility into phishing and other malicious email attacks. This connector is available with any active Cortex XSIAM or Cortex AgentiX license.
* [Proofpoint Threat Protection](https://xsoar.pan.dev/docs/reference/integrations/proofpoint-threat-protection): Threat Protection APIs are REST APIs that allow Proofpoint On Demand customers to retrieve, add, update or delete certain PoD configurations. This connector is available with any active Cortex XSIAM or Cortex AgentiX license.
* [Proofpoint Threat Response](https://xsoar.pan.dev/docs/reference/integrations/proofpoint-threat-response): Use the Proofpoint Threat Response integration to orchestrate and automate incident response. This connector is available with any active Cortex XSIAM or Cortex AgentiX license.

To configure this connector, follow the steps outlined in the configuration wizard.


---

# 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-agentix/configure-cortex-agentix/cortex-agentix-data-sources-and-connectors/vendor-specific-data-sources-and-connectors/proofpoint/proofpoint.md?ask=<question>&goal=<user_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.