> 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/output-variables.md).

# Output variables in STO pipeline executions

When a scan step finishes successfully, it generates the following output variables for the number of issues detected for each severity level:

* CRITICAL
* HIGH
* MEDIUM
* LOW
* IGNORED — The number of issues that were detected but ignored due to exemptions
* TOTAL

Scan steps also generate a set of "new" variables you can use to determine the next stage of your pipeline. These variables show the number of new issues detected in the current scan compared to the last scan. If this is the first scan for the target, these variables reflect new issues compared to the baseline. You can use these variables to determine the next stage of your pipeline:

* NEW\_CRITICAL
* NEW\_HIGH
* NEW\_MEDIUM
* NEW\_LOW
* NEW\_UNASSIGNED (Reserved for future use)
* NEW\_TOTAL

To view the output variables for a scan, go to the Pipeline Execution page, select the scan step, and click **Output**.

![output variables for a scan](/files/uRZEE22za7A6Pby2w7h9)

For information about how severity levels are calculated, go to [Severities](/security-testing-orchestration/new-to-sto/key-concepts/severities.md).