> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/capabilities/code-reviews/secrets-detection/supported-secret-categories.md).

# Supported Secret Categories

## Overview

| Category                            | Example Providers & Tokens                                                                                                                                                | Notes                                                                                                                                       |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| Cloud platforms                     | AWS access keys, Azure Storage SAS tokens, GCP API keys, IBM COS HMAC keys, SoftLayer credentials, HashiCorp Terraform passwords                                          | Alerts include remediation guidance and links to rotation documentation.                                                                    |
| Developer tooling & CI              | GitHub personal access tokens, Bitbucket app passwords, Artifactory API keys, npm access tokens, Slack webhooks, SendGrid API keys, Airtable tokens, Square access tokens | Nullify suppresses known test tokens while flagging production secrets introduced in commits or history.                                    |
| Authentication artefacts            | JWTs, HTTP basic-auth strings, OAuth bearer tokens, webhook signing secrets                                                                                               | Detectors parse headers and base64 payloads to catch embedded credentials.                                                                  |
| Generic API keys                    | High-entropy keys that do not match a known provider but behave like credentials                                                                                          | Rules combine entropy thresholds with contextual keywords to minimise false positives.                                                      |
| Personally identifiable information | Email addresses, phone numbers, postal addresses, dates of birth, payment cards                                                                                           | PII detections are explained in [Confidential Data Detection](/capabilities/code-reviews/secrets-detection/confidential-data-detection.md). |

Have a provider that is not listed? Define a [custom pattern](/capabilities/code-reviews/secrets-detection.md#policy-controls) or contact Nullify support to add a managed detector.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nullify.ai/capabilities/code-reviews/secrets-detection/supported-secret-categories.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.