> 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/3.0/use-sto/sto-scanner-configuration/reapsaw-scanner-reference.md).
# Reapsaw step configuration
You can ingest scan results for your code repositories from [Reapsaw](https://github.com/dowjones/reapsaw/wiki).
### Workflow description
### Custom Scan step settings for Reapsaw scans in STO
The recommended workflow is to add a Custom Scan step to a Security or Build stage and then configure it as described below.
#### Scanner settings
These settings are all required.
* [Product name](#product-name)
* [Scan type](#scan-type)
* [Policy type](#policy-type)
* [Product config name](#product-config-name)
**Product name**
The scanner name. This is required for all Custom Scan steps.
**Key**
```
product_name
```
**Value**
```
reapsaw
```
**Scan type**
The target type to scan.
**Key**
```
scan_type
```
**Value**
```
repository
```
**Policy type**
The [scan mode](/security-testing-orchestration/3.0/new-to-sto/key-concepts/sto-workflows-overview.md) to use.
**Key**
```
policy_type
```
**Value**
```
ingestionOnly
```
**Product config name**
Required for most scanner integrations.
**Key**
```
product_config_name
```
**Value**
```
default
```
#### Target and variant
#### Repository
#### Ingestion file
#### Fail on Severity