Integrating Dast With Owasp Zap In Pipeline

---
name: integrating-dast-with-owasp-zap-in-pipeline
description: Use when this skill covers integrating OWASP ZAP (Zed Attack Proxy) for
  Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring
  baseline, full, and API scans against running applications, interpreting ZAP findings,
  tuning scan policies, and establishing DAST quality gates in GitHub Actions and
  GitLab CI.
domain: cybersecurity
tags:
- devsecops
- cicd
- dast
- owasp-zap
- dynamic-testing
- secure-sdlc
subdomain: devsecops
version: 1.0.0
author: oyi77
license: Apache-2.0
nist_csf:
- PR.PS-01
- GV.SC-07
- ID.IM-04
- PR.PS-04
category: cybersecurity
---

# Integrating Dast With Owasp Zap In Pipeline

## Overview

Cybersecurity skill for integrating dast with owasp zap in pipeline. Follows industry best practices and security standards.

## When to Use
**Trigger phrases:**
- "integrating dast with owasp zap in pipeline"
- "This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Applicati"


- When testing running web applications for vulnerabilities like XSS, SQLi, CSRF, and misconfigurations
- When SAST alone is insufficient and runtime behavior testing is required
- When compliance mandates dynamic security testing of web applications before production
- When testing APIs (REST/GraphQL) for authentication, authorization, and injection flaws
- When establishing continuous DAST scanning in staging environments before production deployment

**Do not use** for scanning source code (use SAST), for scanning dependencies (use SCA), or for infrastructure configuration scanning (use IaC scanning tools).


## When NOT to Use

- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope


## Prerequisites

- OWASP ZAP Docker image or installed locally (zaproxy/zap-stable or zaproxy/action-*)
- Running target application accessible from the CI/CD runner (staging URL or Docker service)
- ZAP scan rules configuration (optional, for tuning)
- OpenAPI/Swagger specification for API scanning (optional)

## Workflow

```python
# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
```

1. **Define Objectives** — Clarify the goals and scope for dast.
2. **Gather Resources** — Collect tools, data, and access needed for dast.
3. **Execute Process** — Carry out dast operations methodically.
4. **Verify Quality** — Check results against acceptance criteria.
5. **Document Outcomes** — Record findings, decisions, and next steps.

## Tools

- **owasp zap in pipeline** — Primary tool for this skill
- **Analysis Platform** — Data processing and visualization
- **Collaboration Tools** — Team coordination and knowledge sharing


## Process

1. **Prepare** — Gather requirements, verify prerequisites, set up environment
1. **Execute** — Run integrating dast with owasp zap in pipeline workflow with configured parameters
1. **Verify** — Validate output meets requirements, document results

## Verification

- [ ] All dast procedures executed completely and documented
- [ ] Findings validated against multiple data sources
- [ ] False positives identified and filtered
- [ ] Results documented with evidence and timestamps
- [ ] Recommendations provided with risk-based prioritization

## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |