Reapsaw step configuration
Scan code repositories with Reapsaw.
You can ingest scan results for your code repositories from Reapsaw.
Workflow description
This workflow applies to scanner integrations that support Ingestion mode.
Add a Build or Security stage to your pipeline.
Add a Run step and set it up to save your scan results to a shared folder.
For more information, go to Run an ingestion scan in an STO Pipeline.
Add a Custom Scan step.
Review the Important notes for Custom Scan steps for additional requirements and relevant information.
Add the relevant
key:valuepairs to Settings.
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
The scanner name. This is required for all Custom Scan steps.
Key
Value
Scan type
The target type to scan.
Key
Value
Policy type
The scan mode to use.
Key
Value
Product config name
Required for most scanner integrations.
Key
Value
Target and variant
Every Custom Scan step needs a target and baseline.
Target name
Key
Value
A user-defined label for the code repository, container, application, or configuration to scan. Specify a unique, descriptive name. This makes it much easier to navigate your scan results in the STO UI.
Target variant
Key
Value
A user-defined label for the branch, tag, or other target variant to scan.
Repository
Every Custom Scan step needs a target and baseline.
Target name
Key
Value
A user-defined label for the code repository, container, application, or configuration to scan. Specify a unique, descriptive name. This makes it much easier to navigate your scan results in the STO UI.
Target variant
Key
Value
A user-defined label for the branch, tag, or other target variant to scan.
Ingestion file
This setting applies to Custom Scan steps when the policy_type is ingestionOnly.
Key
Value
The path to your scan results when running an Ingestion scan, for example /shared/scan_results/myscan.latest.sarif.
The data file must be in a supported format for the scanner.
The data file must be accessible to the scan step. It's good practice to save your scan results to a shared path in your stage. In the visual editor, go to the stage where you're running the scan. Then go to Overview > Shared Paths. You can also add the path to the YAML stage definition like this:
Fail on Severity
If the scan finds any vulnerability with the specified severity level or higher, the pipeline fails automatically. NONE means do not fail on severity.
For more information, go to:
Key
Value
Last updated
Was this helpful?