For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sto Ref Legacy Orchestrated

The following settings are required for Custom Scan steps where the policy_type is orchestratedScan.

  • product_domain Domain of the application instance to scan. You can include the full path to the app in this field, or split the full path between the Domain and the Path fields. Example: https://myapp.io/portal/us

  • product_access_token The access token used to log in to a specific product in the scanner. This is required for some scans. In most cases this is a password or an API key.

    You should create a Harness text secret with your encrypted token and reference the secret using the format <+secrets.getValue("project.container-access-id")>. For more information, go to Add and Reference Text Secrets.

For a complete workflow description and example, go to Run an Orchestration Scan in an STO Pipeline.

Last updated

Was this helpful?