> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/siem-integrations/email-security/proofpoint.md). # Proofpoint ![Proofpoint logo](https://4191868192-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOlFHF8fl339QOw3Og8L7%2Fuploads%2Fgit-blob-8083221a8c72108bbbc623b0b483e605b8038bb7%2Fproofpoint2024.jpg?alt=media) Integrating Proofpoint with ThreatDefence enables ingestion of advanced email threat intelligence and security alerts into the ThreatDefence platform, providing greater visibility into targeted attacks, phishing attempts, and other email-borne threats. *** ## Step 1: Create New TAP Connected Application Credential 1. Log in to the **TAP dashboard** at . 2. Navigate to **Settings → Connected Applications**. 3. Click **Create New Credential**. 4. Name the new credential set and click **Generate**. 5. Copy the generated **Service Principal** and **Secret**. Store them securely. *** ## Step 2: Configuration in ThreatDefence Provide the following details to your ThreatDefence representative at [**support@threatdefence.com**](mailto:support@threatdefence.com): * **Service Principal** * **Secret** *** If you have any questions or need assistance, please contact ****. --- # 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://docs.threatdefence.com/siem-integrations/email-security/proofpoint.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.