> 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/fortify-on-demand-scanner-reference.md).

# Fortify on Demand step configuration

You can scan your repositories and ingest scan results from [Fortify on Demand](https://www.microfocus.com/documentation/fortify-on-demand/).

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

<details>

<summary>Orchestration/extraction workflows</summary>

</details>

<details>

<summary>Ingestion workflows</summary>

</details>

### Custom Scan step settings for Fortify on Demand <a href="#custom-scan-step-settings-for-fortify-on-demand" id="custom-scan-step-settings-for-fortify-on-demand"></a>

#### Scanner settings <a href="#scanner-settings" id="scanner-settings"></a>

These settings are required.

* [Product name](#product-name)
* [Scan type](#scan-type)
* [Policy type](#policy-type)
* [Product config name](#product-config-name)

**Product name**

The scanner name.

**Key**

```
product_name
```

**Value**

```yaml
fortifyondemand
```

**Scan type**

The target type to scan.

**Key**

```
scan_type
```

**Value**

```
repository
```

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

```
dataLoad
```

**Product config name**

**Key**

```
product_config_name
```

**Value**

If `product_lookup_type` = `Static`:

```
sast
```

If `product_lookup_type` = `Dynamic`:

```
dast
```

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

#### Repository <a href="#repository" id="repository"></a>

#### Product access <a href="#product-access" id="product-access"></a>

These settings are available to access your Fortify on Demand SaaS instance when `policy_type` is `orchestratedScan` or `dataLoad`.

You should [create Harness text secrets](/harness-ai/use-harness-platform/secrets/add-use-text-secrets.md) for your encrypted passwords and tokens and reference them using the format `<+secrets.getValue("my-access-token")>`.

**Product access keys**

```
product_domain
```

```
product_access_id
```

```
product_access_token
```

```
product_owner_id
```

```
product_entitlement
```

```
product_scan_type
```

```
product_app_name
```

```
product_release_name
```

```
product_target_language
```

```
product_target_language_version
```

```
product_audit_type
```

```
product_data_center
```

**Product scan settings**

**Key**

```
product_scan_settings
```

**Values**

```
Custom
```

```
default
```

**Product lookup type**

**Key**

```
product_lookup_type
```

**Values**

```
Dynamic
```

```
Static
```

```
Mobile
```

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