> 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/nessus-scanner-reference.md). # Nessus step configuration You can scan your application instances and ingest results from Nessus. ### Workflow descriptions

Orchestration/extraction workflows

Ingestion workflows

### Custom Scan step settings for Nessus scans in STO #### Scanner settings These settings are required for most scanners. For more information, go to the reference for the scanner integration you're setting up. * [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** ``` nessus ``` **Scan type** The target type to scan. **Key** ``` scan_type ``` **Value** ``` instance ``` **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** ``` orchestratedScan ``` ``` ingestionOnly ``` **Product config name** **Key** ``` product_config_name ``` **Value** ``` nessus-web-application ``` #### Target and variant #### Instance #### Product access These settings are available to access your Nessus instance when `policy_type` is `orchestratedScan`. You should [create Harness text secrets](/harness-ai/use-harness-platform/secrets/add-use-text-secrets.md) for your encrypted passwords/tokens and reference them using the format `<+secrets.getValue("my-access-token")>`. **Product access keys** ``` product_domain ``` ``` product_access_id ``` ``` product_access_token ``` ``` product_policy_id ``` ``` product_scanner_id ``` ``` product_template_uuid ``` #### Ingestion file #### Fail on Severity