configure-dast-scan
Add Dynamic Application Security Testing (DAST) steps to existing Harness pipelines using Harness STO scanners. Supports API DAST / Traceable (default), Burp Suite Enterprise, ZAP (OWASP), Nikto, and Nmap. Scans running application instances for vulnerabilities including API security issues, injection flaws, misconfigurations, and exposed services. Can insert the scan step into an existing CI or SecurityTests stage or create a dedicated SecurityTests stage. Use when asked to add DAST scanning, configure dynamic application testing, set up API security scanning, scan a running application, or add runtime security testing to a pipeline. Trigger phrases: add DAST scan, dynamic application security testing, API DAST, configure Traceable, scan running app, add Burp Suite scan, add ZAP scan, add Nikto scan, runtime security scan, API security scan.
harness · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add harness/harness-skills --skill configure-dast-scan技能说明
name: configure-dast-scan description: >- Add Dynamic Application Security Testing (DAST) steps to existing Harness pipelines using Harness STO scanners. Supports API DAST / Traceable (default), Burp Suite Enterprise, ZAP (OWASP), Nikto, and Nmap. Scans running application instances for vulnerabilities including API security issues, injection flaws, misconfigurations, and exposed services. Can insert the scan step into an existing CI or SecurityTests stage or create a dedicated SecurityTests stage. Use when asked to add DAST scanning, configure dynamic application testing, set up API security scanning, scan a running application, or add runtime security testing to a pipeline. Trigger phrases: add DAST scan, dynamic application security testing, API DAST, configure Traceable, scan running app, add Burp Suite scan, add ZAP scan, add Nikto scan, runtime security scan, API security scan. metadata: author: Harness version: 1.0.0 mcp-server: harness-mcp-v2 license: Apache-2.0 compatibility: Requires Harness MCP v2 server (harness-mcp-v2)
Configure DAST Scan
Add a Dynamic Application Security Testing (DAST) step to an existing Harness pipeline using Harness STO scanners. DAST scanners test running application instances for security vulnerabilities at runtime.
Instructions
Step 1: Establish Scope and Pipeline Context
Ask for org, project, and pipeline identifier if not already known. This skill only works with existing pipelines.
Call MCP tool: harness_get
Parameters:
resource_type: "pipeline"
resource_id: "<pipeline_identifier>"
org_id: "<organization>"
project_id: "<project>"
Step 2: Analyze Pipeline Structure
Parse the pipeline YAML to identify:
- All stages and their types (
CI,SecurityTests,Deployment,Approval) - Whether a
SecurityTestsstage already exists - Existing steps in each stage
Present the structure to the user:
Pipeline: <name>
Stage 1: <stage_name> (type: <stage_type>)
- Step 1: <step_name> (type: <step_type>)
...
Ask the user where they want the DAST scanner step added:
Present the available insertion points:
- Any existing
SecurityTestsstage (scanner step is added into that stage'sexecution.steps) - Any existing
CIstage (scanner step is added directly into that stage'sexecution.steps) - A new
SecurityTestsstage (appended to the pipeline)
Recommendation guidance:
- DAST scans run against a live application instance — they are best placed after deployment so the target is running
- If the pipeline has a Deployment stage, recommend adding a
SecurityTestsstage after the deployment stage - If no deployment stage exists, the user must provide the target URL of an already-running instance
- Adding to an existing
SecurityTestsstage is simplest if one already exists
If the user doesn't specify, default to adding a new SecurityTests stage at the end of the pipeline (or after the Deployment stage if one exists).
Step 3: Recommend Scanner Type
Present the available DAST scanners supported in Harness STO:
Available DAST Scanners:
- API DAST (Traceable) (default — Harness native API security scanner, formerly called Traceable)
- Burp Suite Enterprise (commercial, comprehensive web app DAST with crawl + audit)
- ZAP (OWASP Zed Attack Proxy, open-source web app scanner)
- Nikto (open-source, web server scanner)
- Nmap (open-source, network/port scanner with vulnerability scripts)
Default recommendation: Use API DAST (Traceable) — the Harness native DAST scanner for API security testing. It connects with your Traceable account to initiate scans against existing scan configurations, and results integrate directly with Harness STO.
Ask the user which scanner they prefer. If they don't specify, use API DAST (Traceable) as the default.
Step type mapping and scanner auth requirements:
| Scanner | type field | Product auth needed? | Auth fields |
|---|---|---|---|
| API DAST (Traceable) | Traceable | Yes | domain (Traceable platform URL), access_token (API token) |
| Burp Suite Enterprise | BurpEnterprise | Yes | domain (Burp Enterprise URL), access_token (API key) |
| ZAP | Zap | No | — |
| Nikto | Nikto | No | — |
| Nmap | Nmap | No | — |
If the user picks a scanner that requires auth (API DAST, Burp Suite):
- Inform the user that scanner product credentials are required
- Ask for the required secret references from the table above — these must already exist as Harness secrets
- Format them as
<+secrets.getValue("project.<secret_identifier>")> - These go into the
authblock of the step spec
Example prompt to user:
"API DAST (Traceable) requires a platform domain and access token. Please provide:
- Your Traceable platform URL (e.g.,
https://api.traceable.ai/)- The Harness secret identifier for your Traceable API token (e.g.,
traceable_api_token). I'll reference it as<+secrets.getValue("project.traceable_api_token")>."
If the secret doesn't exist yet, suggest creating it first via /create-secret before proceeding.
Step 4: Select Scan Mode (API DAST / Traceable only)
This step applies only to API DAST (Traceable). For other scanners (Burp Suite, ZAP, Nikto, Nmap), default to orchestration and skip to Step 5.
Present the three available scan modes and ask the user which one they want:
Available Scan Modes:
- Orchestration (default) — Triggers a new scan run within an existing Traceable Scan. Results are automatically saved in STO. Requires an active runner in Traceable.
- Extraction — Retrieves the latest scan results from an existing Traceable Scan and imports them into STO. No new scan is triggered — useful for pulling results from scans run on a schedule or externally.
- Ingestion — Reads scan results from a local JSON file and imports them into STO. The user must fetch results separa