> 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-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/docker/connect-docker-hub-registry/manage-a-docker-hub-connector.md).

# Manage a Docker Hub connector

Manage the Docker Hub registry connector in Cortex Cloud.

After you add a **Docker Hub** connector, you can modify the connector settings and configure the scanning scope to control which images are scanned in the connected registry.

To manage the connector, follow these steps:

1. Navigate to **Settings** → **Data Sources & Integrations**.
2. Find the **Docker Hub** data source from the list of data sources, or use the filter to search.
3. Select the **Docker Hub** row. A pane opens with a list of integration instances and their details.

   You can create a new instance by selecting **Add Instance** and following the [onboarding wizard](/cortex-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/docker/connect-docker-hub-registry.md) to define the settings.
4. Right click an instance to perform actions on it as follows:

<table data-header-hidden><thead><tr><th width="153.83984375">Action</th><th>Instructions</th></tr></thead><tbody><tr><td><strong>Action</strong></td><td><strong>Instructions</strong></td></tr><tr><td><strong>Edit</strong></td><td><p>Edit the <strong>Docker integration</strong> instance.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><ul><li>If you selected <strong>Scan with Broker VM</strong> mode, you can't change to a different scan mode (such as <strong>Cloud Discovery</strong> or <strong>Scan with Outpost</strong>) when you edit the instance.</li><li>When editing an instance configured for <strong>Scan with Broker VM</strong>, you must re-enter your authentication credentials, including <strong>Username</strong>, <strong>Password</strong>, and <strong>CA certificate</strong>.</li></ul></div></td></tr><tr><td><strong>Exclude/Include images</strong></td><td>Define conditions to automatically exclude or include specific images while scanning. Conditions can be based on <strong>Repository</strong> or <strong>Tags</strong>. These conditions apply automatically to newly discovered images in the account.</td></tr><tr><td><strong>Disable</strong></td><td>Stops image scanning for the connector without deleting it.</td></tr><tr><td><strong>Delete</strong></td><td>Removes the connector.</td></tr></tbody></table>

<br>


---

# 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-cloud-posture-management/cortex-cloud-data-sources-and-connectors/vendor-specific-data-sources/docker/connect-docker-hub-registry/manage-a-docker-hub-connector.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.