> 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/use-artifact-registry/platform-integrations/security-integrations/ssd-ar-integrations.md).

# Artifact Registry and Secure Software Delivery

Learn how to use Artifact Registry with the secure software delivery modules including [Security Testing Orchestration](/security-testing-orchestration/readme.md) and [Supply Chain Security](/software-supply-chain-assurance/readme.md).

### Secure Software Delivery <a href="#secure-software-delivery" id="secure-software-delivery"></a>

Seamlessly reference artifacts stored in Harness Artifact Registry within your STO or SCS (also referred to as Software Support Chain Assurance or SSCA) pipeline steps. This functionality eliminates the need for an external connector, providing a streamlined and user-friendly experience while enabling efficient and simplified workflows.

{% hint style="info" %}
**EXAMPLE SCS STAGE**

Examples of SCS stages can be a **Software Bill of Materials (SBOM)** or **Supply Chain Levels for Software Artifacts (SLSA)**.
{% endhint %}

To reference an artifact in an SCS or STO stage, follow these steps:

1. Navigate to your pipeline, and enter your `SCS` or `STO` stage.
2. Select or add a new SCS or STO step to your pipeline.
3. Under **Source**, select the source (HAR by default).
4. In the **Registry** field, select your Artifact Registry, or add a new one.
5. Add your artifact's `imageName:tag`
6. Click `Apply Changes` at the top right, and you are done! No connectors needed.

{% hint style="info" %}
**SLSA STEP PARAMETERS**

In SLSA stages, if you add an SLSA Generation step, provide the Registry, Image and Artifact Digest, which is a sha256 hash.
{% endhint %}