> 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/content-security/code42-dlp.md).

# Code42 DLP

## Step 1: Generate API Client

1. **Log in to the Code42 Console**
   * Go to your organization's Code42 Incydr web console (e.g., `https://console.us.code42.com`).
2. **Navigate to API Client Management**
   * In the left-hand menu, look for ***Administration*** or ***Settings***.
   * Select **API Clients** or ***Integrations*** depending on your version.
3. **Create a New API Client**
   * Click ***Add API Client*** or ***Create New Integration***.
   * Provide a name and optional description for the client.
4. **Generate Credentials**
   * Once created, the console will display:
     * ***Client ID*** (a long alphanumeric string)
     * ***Client Secret*** (shown only once—copy and store securely)

## Step 2: Assign necessary

1. **Assign Permissions**
   * Ensure the API client has access to ***Audit Log*** endpoints.
   * You may need to assign roles or scopes like `audit.read` or `log.read`.

***

## Deliverables

Please email them to <support@threatdefence.com>

1. **API Credentials**
   * Your ***Client ID***
   * Your ***Client Secret***
   * Your Code42 API domain e.g., ***'***[***https://api.us.code42.com***](https://api.us.code42.com)

***


---

# 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/content-security/code42-dlp.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.