> 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/security-testing-orchestration/new-to-sto/key-concepts/ingest-scan-results-into-an-sto-pipeline.md).

# Run an ingestion scan in an STO Pipeline

In an *ingestion scan*, you configure a step to ingest scan results from a data file. The pipeline then analyzes, deduplicates, and displays the results. Ingestion scans might require more work to set up then orchestration scans, but they also support a wide variety of use cases. Ingestion scans enable you to:

* Ingest results from scanners that don't currently have integrations with Harness STO.
* Ingest results from scans that ran in a previous step or stage, or outside the pipeline entirely.
* Ingest results from custom scans with advanced settings that address specific security requirements.

To ingest scan results from outside a Security step, you set up your pipeline as follows:

1. A Run step saves scan results to a shared folder. The step might run the scan locally, download results from an external source, or copy results from another location in the workspace into the shared folder.
2. A [Security or Security Tests step](/security-testing-orchestration/use-sto/sto-scanner-configuration/security-step-settings-reference.md#security-steps-and-scanner-templates-in-sto) ingests the results from the shared folder. Then it analyzes, deduplicates, and displays the results.

![](/files/FNVaJswAvLZsGD5osy76)

For a complete list of supported scanners, go to [Harness STO scanner support](/security-testing-orchestration/new-to-sto/sto-whats-supported/scanners.md).

### Example workflows <a href="#example-workflows" id="example-workflows"></a>

Here are some example ingestion-only workflows that target specific use cases:

* [SAST code scans using Semgrep](/security-testing-orchestration/use-sto/sto-scanner-configuration/semgrep/sast-scan-semgrep.md)
* [Run STO scans using GitHub Action and Drone Plugin steps](/security-testing-orchestration/troubleshooting-and-resources/sto-use-cases/set-up-sto-pipelines/run-scans-using-github-actions.md)
* [Example workflow: Ingest SARIF data from a Checkmarx GitHub Action scan](/security-testing-orchestration/use-sto/sto-scanner-configuration/checkmarx/checkmarx-github-action-ingestion.md)
* [Create a build-scan-push pipeline (STO only)](/security-testing-orchestration/troubleshooting-and-resources/sto-use-cases/set-up-sto-pipelines/build-scan-push-workflows/build-scan-push-sto-only.md)

### See also <a href="#see-also" id="see-also"></a>

* [Ingest SARIF scan results into STO](/security-testing-orchestration/use-sto/sto-custom-scanning-and-ingestion/ingest-sarif-data.md)
* [Ingest Results from unsupported scanners](/security-testing-orchestration/use-sto/sto-custom-scanning-and-ingestion/ingesting-issues-from-other-scanners.md)
* [Harness STO scanner support](/security-testing-orchestration/new-to-sto/sto-whats-supported/scanners.md)