Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/content/en/about_defectdojo/pro_features.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ See our [Connectors Guide](/en/connecting_your_tools/connectors/about_connectors

Supported tools for Connectors include:

* Anchore
* AWS Security Hub
* BurpSuite
* Checkmarx ONE
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ But everyone needs a starting point, and that's where Connectors come in. Connec

We currently support Connectors for the following tools, with more on the way:

* **Anchore**
* **AWS Security Hub**
* **BurpSuite**
* **Checkmarx ONE**
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,17 @@ Whenever possible, we recommend creating a new 'DefectDojo Bot' account within y

# **Supported Connectors**

## **Anchore**

The Anchore connector uses a user's API token to pull data from Anchore Enterprise. Products will be mapped and discovered based on "Applications", which are composed of multiple Images in Anchore - see [Anchore Enterprise Documentation](https://docs.anchore.com/current/docs/sbom_management/application_groups/application_management_anchorectl/) for more information.

#### Connector Mappings

1. The Anchore URL in the **Location** field: this is the URL where you access the Anchore.
2. Enter a valid API Key in the Secret field. This is the API key associated with your Burp Service account.

See the official [Anchore documentation](https://docs.anchore.com/current/docs/) for more information on creating a token for Anchore.

## **AWS Security Hub**

The AWS Security Hub connector uses an AWS access key to interact with the Security Hub APIs.
Expand Down
2 changes: 1 addition & 1 deletion docs/content/en/connecting_your_tools/parsers/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ DefectDojo can parse data from 180+ security reports and counting.

| [Connectors](../connectors/about_connectors): supported tools | [Smart Upload](../import_scan_files/smart_upload/): supported tools |
| --- | --- |
| AWS Security Hub, BurpSuite, Checkmarx ONE, Dependency-Track, Probely, Semgrep, SonarQube, Snyk, Tenable | Nexpose, NMap, OpenVas, Qualys, Tenable, Wiz |
| Anchore, AWS Security Hub, BurpSuite, Checkmarx ONE, Dependency-Track, Probely, Semgrep, SonarQube, Snyk, Tenable | Nexpose, NMap, OpenVas, Qualys, Tenable, Wiz |

# All Supported Tools

Expand Down
4 changes: 0 additions & 4 deletions docs/content/en/connecting_your_tools/parsers/file/wiz.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,6 @@ toc_hide: true
weight: 1
---

# Wiz Scanner Parser Documentation

## Overview

The [Wiz](https://www.wiz.io/) parser for DefectDojo supports imports from both Wiz Scanner Standard and SCA (Software Composition Analysis) .csv output from Wiz.io. This document details the parsing of both formats into DefectDojo field mappings, unmapped fields, and location of each field's parsing code for easier troubleshooting and analysis.

## Supported File Types
Expand Down