> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/quarantine.md).

# Quarantine: review and release blocked artifacts

Quarantine - review and release blocked artifacts

Quarantine is a reversible hold placed on an artifact when it violates a security policy. A quarantined artifact cannot be pulled by users or pipelines. It remains visible in the registry, is not deleted, and can be released after review or removed permanently.

Quarantine gives your security or platform team time to review findings and decide whether the image is acceptable for use, needs to be rebuilt, or should be deleted entirely.

## How an artifact gets quarantined

### Policy violation after a scan

When security scanning is enabled on a registry, Harness runs the **HARNESS ARTIFACT SCAN PIPELINE** after every push. If you have attached a **Security Tests policy set** to the registry, the policy set is evaluated against the scan results. If the image violates the policy (for example, if the policy quarantines any image with a Critical CVE and the scan finds one), Harness quarantines the image automatically.

The policy set defines the conditions for quarantine. Common policies:

* Quarantine any image with a **Critical** severity CVE.
* Quarantine any image with a **High** severity CVE that has a fix available.
* Quarantine any image with a component whose license is GPL or Affero General Public License (AGPL).

You configure policy sets in the **Security** section of the registry's **Configuration** tab. Go to [Configure security scanning](https://developer.harness.io/artifact-registry/3.0/registries/configure-security-scanning.md) to set up a policy.

### The async scanning window

Scanning runs after a push completes, not before. There is a brief window between the moment a push succeeds and the moment the scan result is applied. During this window, the image is technically available. If the scan finds a policy violation, the image is quarantined once the scan completes, but a pull that occurs inside this window could succeed.

For registries where this window is unacceptable, use the staging-and-promotion pattern: push images to a staging registry, wait for scan results, then promote clean images to a production registry. Go to [Security scanning](https://developer.harness.io/artifact-registry/3.0/concepts/security-scanning.md) for details on this pattern.

{% hint style="info" %}
**Dependency Firewall uses a different mechanism**

For artifacts fetched from external upstream proxies, Dependency Firewall evaluates packages synchronously at the upstream boundary before they are cached. A **Blocked** verdict prevents caching entirely. A **Warning** verdict can quarantine the artifact after caching. Go to [Dependency Firewall](https://developer.harness.io/artifact-registry/3.0/concepts/dependency-firewall.md) for upstream-proxy enforcement.
{% endhint %}

## Find quarantined artifacts

Quarantined artifacts remain in the registry's **Artifacts** list. A quarantined image displays a **Quarantined** status indicator on the artifact detail page. The **Vulnerabilities** column on the Artifacts list reflects the findings that triggered quarantine.

To filter the Artifacts list to show only quarantined images, use the **Show** filter and select **Quarantined**.

## Review findings that triggered quarantine

To understand why an artifact was quarantined:

1. Click the artifact to open the artifact detail page.
2. Select the **Vulnerabilities** tab to see the full list of CVE findings, including the specific findings that violated the policy.
3. Review the severity, affected package, installed version, and whether a fix is available.

Go to [Vulnerability scanning](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/vulnerability-scanning.md) for a detailed explanation of the findings table and how to interpret each field.

## Release from quarantine

Release a quarantined artifact when you have reviewed the findings and determined the image is acceptable for use, for example because the vulnerable component is not reachable in your deployment, or because a policy exception has been granted.

To release an artifact from quarantine:

1. Open the artifact detail page.
2. Select **Release from quarantine** (or use **Show more actions** (**⋮**) on the Artifacts list and select **Release from quarantine**).
3. Confirm the release.

After release, the artifact is pullable again. The findings are not removed; they remain on the Vulnerabilities tab as an audit record. If the same image is re-evaluated against the policy (for example, after the policy is updated), it may be quarantined again.

{% hint style="warning" %}
**Permissions required**

Releasing from quarantine requires the Artifact Registry **Manage Artifacts** permission. If the release action is not visible, contact your Harness account administrator. Go to [RBAC and permissions](https://developer.harness.io/artifact-registry/3.0/reference/rbac-and-permissions.md) for the full permissions reference.
{% endhint %}

## Delete a quarantined artifact

If a quarantined artifact should not be used and does not need to be recovered, delete it rather than releasing it.

To delete a quarantined artifact:

1. Open the artifact detail page, or locate the artifact in the Artifacts list.
2. Open **Show more actions** (**⋮**) and select **Delete**.
3. Enter the artifact name to confirm.
4. Choose whether to **soft delete** (recoverable for the account's configured retention period) or **permanently delete** (immediate and irreversible).

Go to [Delete an artifact](https://developer.harness.io/artifact-registry/3.0/artifacts/delete-an-artifact.md) for details on soft delete, the retention period, and permanent deletion.

## Troubleshooting

<details>

<summary>An image was quarantined immediately after a push that looked clean</summary>

The scan pipeline runs asynchronously after the push. If the image was available briefly after push and then quarantined, the scan completed and found a policy violation. Check the **Vulnerabilities** tab on the artifact detail page to see the specific findings, and review the policy set configured on the registry to confirm which condition triggered quarantine.

</details>

<details>

<summary>The Release from quarantine option is not visible</summary>

Releasing from quarantine requires the **Manage Artifacts** permission in Harness RBAC. If the option does not appear, your role does not include this permission. Ask your account administrator to grant the permission or release the artifact on your behalf. Go to [RBAC and permissions](https://developer.harness.io/artifact-registry/3.0/reference/rbac-and-permissions.md).

</details>

<details>

<summary>An artifact was released from quarantine but was quarantined again</summary>

If the same image is re-evaluated against the policy after release, for example because a scheduled policy re-evaluation ran or the policy set was updated, it can be quarantined again. The findings that triggered the original quarantine are still present in the image. To prevent re-quarantine, rebuild the image with the affected component patched, or adjust the policy to exclude this specific finding.

</details>

<details>

<summary>A pipeline fails with a 403 or "artifact not found" error on an image it previously used</summary>

This is the most common symptom of an artifact being quarantined after a pipeline was already referencing it. Check the artifact's status in the registry. If it is quarantined, review the findings and either release the artifact or rebuild the image. Pinning the pipeline to an image digest rather than a tag helps distinguish this error from a tag-not-found error.

</details>

## Next steps

* To view the scan findings that triggered quarantine, go to [Vulnerability scanning](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/vulnerability-scanning.md).
* To view the SBOM of a quarantined artifact, go to [SBOM: view, score, and download](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/sbom-view-score-and-download.md).
* To configure which policy violations trigger quarantine, go to [Configure security scanning](https://developer.harness.io/artifact-registry/3.0/registries/configure-security-scanning.md).
* To understand the scanning concepts and the staging-registry pattern, go to [Security scanning](https://developer.harness.io/artifact-registry/3.0/concepts/security-scanning.md).
* To trigger a rescan on a quarantined artifact, go to [Re-evaluate a version](https://developer.harness.io/artifact-registry/3.0/artifacts/re-evaluate-a-version.md).

{% @harness-feedback/feedback %}
