> 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/proofpoint/proofpoint-targeted-attack-protection/ingest-logs-from-proofpoint-targeted-attack-protection.md).

# Ingest logs from Proofpoint Targeted Attack Protection

Ingest logs from Proofpoint Targeted Attack Protection in Cortex XSIAM.

To receive logs from Proofpoint Targeted Attack Protection (TAP), you must first configure TAP service credentials in the TAP dashboard, and then the Collection Integrations settings in Cortex XSIAM based on your Proofpoint TAP configuration. After you set up data collection, Cortex XSIAM begins receiving new logs and data from the source.

When Cortex XSIAM begins receiving logs, the app creates a new dataset (`proofpoint_tap_raw`) that you can use to initiate XQL Search queries. For example queries, refer to the in-app XQL Library.

Configure the Proofpoint TAP collection in Cortex XSIAM.

1. Generate TAP Service Credentials in Proofpoint TAP.

   TAP service credentials can be generated in the TAP Dashboard, where you will receive a Proofpoint Service Principal for authentication and Proofpoint API Secret for authentication. Record these credentials as you will need to provide them when configuring the Proofpoint Targeted Attack Protection data collector in Cortex XSIAM. For more information on generating TAP service credentials, see [Generate TAP Service Credentials](https://ptr-docs.proofpoint.com/ptr-guides/integrations-files/ptr-tap/).
2. Configure the Proofpoint TAP collection in Cortex XSIAM.
   1. Navigate to **Settings** → **Data Sources & Integrations**.
   2. Click **+ Add New**, search for Proofpoint Targeted Attack Protection, then hover over it and click **Add**.
   3. Set these parameters:
      * Name: Specify a descriptive name for your log collection configuration.
      * Proofpoint Endpoint: All Proofpoint endpoints are available on the `tap-api-v2.proofpoint.com` host. You can leave the default configuration or specify another host.
      * Service Principal: Specify the Proofpoint Service Principal for authentication. TAP service credentials can be generated in the TAP Dashboard.
      * API Secret: Specify the Proofpoint API Secret for authentication. TAP service credentials can be generated in the TAP Dashboard.
   4. Click Test to validate access, and then click Enable.

      Once events start to come in, a green check mark appears underneath the Proofpoint Targeted Attack Protection configuration with the amount of data received.
3. (Optional) Manage your Proofpoint Targeted Attack Protection data collector.

   After you enable the Proofpoint Targeted Attack Protection data collector, you can make additional changes as needed.

   You can perform any of the following:

   * Edit the Proofpoint Targeted Attack Protection data collector settings.
   * Disable the Proofpoint Targeted Attack Protection data collector.
   * Delete the Proofpoint Targeted Attack Protection data collector.


---

# 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-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/proofpoint/proofpoint-targeted-attack-protection/ingest-logs-from-proofpoint-targeted-attack-protection.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.