docs(connectors): Escape connector reference

Document the Escape (escape.tech) API-security DAST connector: the
API-key prerequisite, the Location/Secret/Minimum-Severity mappings, and
the whole-account model (every organization -> every application -> a
Record per application with a scan; each latest-scan issue -> finding,
severity/CWE/OWASP-tag/method-tag/endpoint/remediation, dynamic, dedupe
on issue id).

Companion to connectors#762 and dojo-pro#2013.

sc-13909

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: 2 people

docs/content/import_data/pro/connectors/connectors_tool_reference.md

@@ -511,6 +511,24 @@ You will need an Edgescan API token. Create one from your Edgescan account under
 
 Each Edgescan asset becomes a Record, and each open vulnerability on that asset is imported as a finding. Severity is mapped from Edgescan's numeric scale (1–5) to DefectDojo's Info–Critical, and CVE references, the CWE, and a CVSS v3 vector are included where Edgescan provides them.
 
+## **Escape**
+
+The Escape connector uses the [Escape](https://escape.tech) API to import **API\-security (DAST) findings**. DefectDojo enumerates every organization the token can access and every application within each, creates a Record for each application that has a scan, and imports that application's latest scan issues as findings — there is no per\-application configuration.
+
+#### Prerequisites
+
+You will need an Escape **API key**, created in the Escape app under **Settings → API keys**. The key is sent in the `Authorization: Key` header and is never logged.
+
+#### Connector Mappings
+
+1. Leave the **Location** field blank to use `https://public.escape.tech/v2`, or enter your Escape API host explicitly.
+2. Enter the Escape API key in the **Secret** field.
+3. Optionally, set a **Minimum Severity** to limit which findings are imported.
+
+DefectDojo maps each **application** to a Record and each scan **issue** to a finding: the severity comes from Escape's rating (Critical/High/Medium/Low), the CWE is carried over, the OWASP category and HTTP method become tags, the affected URL becomes the endpoint, and the remediation guidance is included. Findings are recorded as dynamic findings and de\-duplicated on Escape's issue id.
+
+See the [Escape API documentation](https://docs.escape.tech/) for more information.
+
 ## **Fairwinds Insights**
 
 The Fairwinds Insights connector uses the [Fairwinds Insights](https://insights.fairwinds.com) REST API to import **Kubernetes security findings** across your whole organization. DefectDojo enumerates every active **cluster** and creates a Record for each one, then imports that cluster's Security **action items** \(from Polaris, Trivy, Kube\-bench, OPA and the other Insights reports\) as findings — there is no per\-cluster configuration.