> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-integrations/3rd-party-integrations/registry/docker-hub.md).
# Docker Hub
Integrate Docker Hub with OX to centralize security findings alongside container, pipeline, cloud, and runtime signals already in OX.
OX scans Docker Hub on a schedule and on demand, enriches findings with OX context (application mapping, workflows, and compliance), and presents a unified queue for investigation and reporting.
After you connect, Docker Hub scan results appear in the Active issues page (use the filter **Source tool > Docker Hub**).
## What OX adds
* **Context and correlation:** OX maps Docker Hub findings to applications, services, and teams to show impact and ownership.
* **Prioritization with severity factors:** OX may reprioritize scanner severities when exploitability and environment context reduce risk (for example, Critical → High). Severity factors explain why the priority changed.
* **Evidence at a glance:** When available, OX displays scanner evidence, file locations, and remediation guidance alongside OX analytics to speed triage.
## Connection Methods
For general information about connection methods, see[ Connection methods](/get-started/onboarding-to-ox/source-control/connection-methods.md).
Connect to OX with a Docker Hub username and token.
## Prerequisites
**OX**
* Permission to configure connectors
**Docker Hub**
* Create a personal access token (PAT).
* **IP Whitelisting:** Add the [OX Security IP address](/get-started/onboarding-to-ox/prerequisites-and-access.md) to Docker Hub's whitelist or your firewall rules.
## Connect with username and token
### **Step 1: Create personal access token \[Docker]**
1. Verify that the [prerequisites ](#prerequisites)are in place.
2. Log in to the Docker Hub workspace.
3. Go to **Account Settings > Personal access token** and select **Generate access token**.
4. In **Create access token**, enter:
* **Token name**: A name of the token
* **Expiry:** Set to None
* **Access permissions:** Read-only
5. Select **Generate**. Docker generates a token.
6. Copy and save the user name and token. Save them securely. You cannot view the token again. **Best practice:** Store the token in a secrets manager and set a reminder to rotate it according to your policy.
### **Step 2: Connect OX to Docker \[OX]**
1. Verify that the [prerequisites ](#prerequisites)are in place.
2. In OX, go to **Connectors > Registry** and select **Docker Hub**.
3. In **Configure your Docker Hub credentials,** select the link **HELP CONNECTING DOCKER HUB** to open an online summary of the connection process.
4. Enter the following parameters:
Parameter
Details
User Name
The Docker token user name
Password
The Docker token
3. Select **CONNECT**. OX validates the credentials.
4. In **Configure your Docker Hub connector**, select the images you want OX to scan.\
\
5. Select **SAVE**.
6. In **Configure your Docker Hub credentials**, select **VERIFY CONNECTIVITY**.\
A green checkmark indicates a successful connection. If verification fails, check your credentials and permissions.
**Optional configurations**
* To change the images OX scans and monitors, see the section [Change the locations OX scans](#change-the-locations-ox-scans).
* For information on the OX Broker, see the article [OX Broker](/get-started/onboarding-to-ox/prerequisites-and-access/ox-deployment/ox-broker.md).
## Change the locations OX scans
Once you have a connection, you can change the locations that OX scans and monitors.
1. Use the **Gear** icon at the bottom of the Configuration screen.
2. OX displays the locations or objects that OX scans and monitors.
3. Change the selection as needed.
4. Select **SAVE**.
---
# 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.ox.security/ox-integrations/3rd-party-integrations/registry/docker-hub.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.
.png?alt=media)