> 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/qualys-web-app-scanner-reference.md).

# Qualys Web Application Scanning (WAS) step configuration

You can ingest your application scan results from Qualys Web Application Scanning (WAS) into STO.

### Workflow description <a href="#workflow-description" id="workflow-description"></a>

### Custom Scan step settings for Qualys scans in STO <a href="#custom-scan-step-settings-for-qualys-scans-in-sto" id="custom-scan-step-settings-for-qualys-scans-in-sto"></a>

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 <a href="#scanner-settings" id="scanner-settings"></a>

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**

**Key**

```
product_name
```

**Value**

```
qualys
```

**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**

```
ingestionOnly
```

**Product config name**

**Key**

```
product_config_name
```

**Value**

```
default
```

#### Target and variant <a href="#target-and-variant" id="target-and-variant"></a>

#### Ingestion file <a href="#ingestion-file" id="ingestion-file"></a>

#### Fail on Severity <a href="#fail-on-severity" id="fail-on-severity"></a>

### Proxy settings <a href="#proxy-settings" id="proxy-settings"></a>