Skip to main content Inicio Creadores agentsecops secopsagentkit dast-zap
dast-zap Dynamic application security testing (DAST) using OWASP ZAP (Zed Attack Proxy) with passive and active scanning, API testing, and OWASP Top 10 vulnerability detection. Use when: (1) Performing runtime security testing of web applications and APIs, (2) Detecting vulnerabilities like XSS, SQL injection, and authentication flaws in deployed applications, (3) Automating security scans in CI/CD pipelines with Docker containers, (4) Conducting authenticated testing with session management, (5) Generating security reports with OWASP and CWE mappings for compliance.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/AgentSecOps/SecOpsAgentKit --skill dast-zapEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Explorador de archivos
11 archivos Más de este repositorio Interactive HTTPS proxy for API security testing with traffic interception, modification, and replay capabilities. Supports HTTP/1, HTTP/2, HTTP/3, WebSockets, and TLS-protected protocols. Includes Python scripting API for automation and multiple interfaces (console, web, CLI). Use when: (1) Intercepting and analyzing API traffic for security testing, (2) Modifying HTTP/HTTPS requests and responses to test API behavior, (3) Recording and replaying API traffic for testing, (4) Debugging mobile app or thick client API communications, (5) Automating API security tests with Python scripts, (6) Exporting traffic in HAR format for analysis.
API specification linting and security validation using Stoplight's Spectral with support for OpenAPI, AsyncAPI, and Arazzo specifications. Validates API definitions against security best practices, OWASP API Security Top 10, and custom organizational standards. Use when: (1) Validating OpenAPI/AsyncAPI specifications for security issues and design flaws, (2) Enforcing API design standards and governance policies across API portfolios, (3) Creating custom security rules for API specifications in CI/CD pipelines, (4) Detecting authentication, authorization, and data exposure issues in API definitions, (5) Ensuring API specifications comply with organizational security standards and regulatory requirements.
Fast web fuzzer for DAST testing with directory enumeration, parameter fuzzing, and virtual host discovery. Written in Go for high-performance HTTP fuzzing with extensive filtering capabilities. Supports multiple fuzzing modes (clusterbomb, pitchfork, sniper) and recursive scanning. Use when: (1) Discovering hidden directories, files, and endpoints on web applications, (2) Fuzzing GET and POST parameters to identify injection vulnerabilities, (3) Enumerating virtual hosts and subdomains, (4) Testing authentication endpoints with credential fuzzing, (5) Finding backup files and sensitive data exposures, (6) Performing comprehensive web application reconnaissance.
name dast-zap description Dynamic application security testing (DAST) using OWASP ZAP (Zed Attack Proxy) with passive and active scanning, API testing, and OWASP Top 10 vulnerability detection. Use when: (1) Performing runtime security testing of web applications and APIs, (2) Detecting vulnerabilities like XSS, SQL injection, and authentication flaws in deployed applications, (3) Automating security scans in CI/CD pipelines with Docker containers, (4) Conducting authenticated testing with session management, (5) Generating security reports with OWASP and CWE mappings for compliance.
version 0.1.0 maintainer SirAppSec category appsec tags ["dast","zap","web-security","owasp","vulnerability-scanning","api-testing","penetration-testing"] frameworks ["OWASP","CWE"] dependencies {"tools":["docker"],"optional":["python3","java"]} references ["https://www.zaproxy.org/docs/","https://www.zaproxy.org/docs/docker/","https://www.zaproxy.org/docs/desktop/start/features/"]
DAST with OWASP ZAP
Overview
OWASP ZAP (Zed Attack Proxy) is an open-source DAST tool that acts as a manipulator-in-the-middle proxy to intercept,
inspect, and test web application traffic for security vulnerabilities. ZAP provides automated passive and active
scanning, API testing capabilities, and seamless CI/CD integration for runtime security testing.
Quick Start
Baseline Scan (Docker)
Run a quick passive security scan:
docker run -t zaproxy/zap-stable zap-baseline.py -t https://target-app.com -r baseline-report.html
Full Active Scan (Docker)
Perform comprehensive active vulnerability testing:
docker run -t zaproxy/zap-stable zap-full-scan.py -t https://target-app.com -r full-scan-report.html
API Scan with OpenAPI Spec
Test APIs using OpenAPI/Swagger specification:
docker run -v $(pwd ):/zap/wrk/:rw -t zaproxy/zap-stable zap-api-scan.py \
-t https://api.target.com \
-f openapi \
-d /zap/wrk/openapi-spec.yaml \
-r /zap/wrk/api-report.html
Core Workflow
Step 1: Define Scan Scope and Target
Identify the target application URL and define scope:
TARGET_URL="https://target-app.com"
Scope Considerations:
Exclude third-party domains and CDN URLs
Include all application subdomains and API endpoints
Respect scope limitations in penetration testing engagements
Step 2: Run Passive Scanning
Execute passive scanning to analyze traffic without active attacks:
docker run -t zaproxy/zap-stable zap-baseline.py \
-t $TARGET_URL \
-r baseline-report.html \
-J baseline-report.json
What Passive Scanning Detects:
Missing security headers (CSP, HSTS, X-Frame-Options)
Information disclosure in responses
Cookie security issues (HttpOnly, Secure flags)
Basic authentication weaknesses
Application fingerprinting data
Step 3: Execute Active Scanning Perform active vulnerability testing (requires authorization):
docker run -t zaproxy/zap-stable zap-full-scan.py \
-t $TARGET_URL \
-r full-scan-report.html \
-J full-scan-report.json \
-z "-config api.addrs.addr.name=.* -config api.addrs.addr.regex=true"
Active Scanning Coverage:
SQL Injection (SQLi)
Cross-Site Scripting (XSS)
Path Traversal
Command Injection
XML External Entity (XXE)
Server-Side Request Forgery (SSRF)
Security Misconfigurations
WARNING: Active scanning performs real attacks. Only run against applications you have explicit authorization to test.
Step 4: Test APIs with Specifications Scan REST, GraphQL, and SOAP APIs:
docker run -v $(pwd ):/zap/wrk/:rw -t zaproxy/zap-stable zap-api-scan.py \
-t https://api.target.com \
-f openapi \
-d /zap/wrk/openapi.yaml \
-r /zap/wrk/api-report.html
docker run -v $(pwd ):/zap/wrk/:rw -t zaproxy/zap-stable zap-api-scan.py \
-t https://api.target.com/graphql \
-f graphql \
-d /zap/wrk/schema.graphql \
-r /zap/wrk/graphql-report.html
Consult references/api_testing_guide.md for advanced API testing patterns including authentication and rate limiting.
Step 5: Handle Authentication For testing authenticated application areas:
python3 scripts/zap_auth_scanner.py \
--target $TARGET_URL \
--auth-type form \
--login-url https://target-app.com/login \
--username testuser \
--password-env ZAP_AUTH_PASSWORD \
--output auth-scan-report.html
Authentication methods supported:
Form-based authentication
HTTP Basic/Digest authentication
OAuth 2.0 flows
API key/token authentication
Script-based custom authentication
See references/authentication_guide.md for detailed authentication configuration.
Step 6: Analyze Results and Generate Reports Review findings by risk level:
docker run -v $(pwd ):/zap/wrk/:rw -t zaproxy/zap-stable zap-full-scan.py \
-t $TARGET_URL \
-r /zap/wrk/report.html \
-J /zap/wrk/report.json \
-x /zap/wrk/report.xml
High : Critical vulnerabilities requiring immediate remediation (SQLi, RCE, authentication bypass)Medium : Significant security weaknesses (XSS, CSRF, sensitive data exposure)Low : Security concerns with lower exploitability (information disclosure, minor misconfigurations)Informational : Security best practices and observations Map findings to OWASP Top 10 using references/owasp_mapping.md.
Automation & CI/CD Integration
GitHub Actions Integration Add ZAP scanning to GitHub workflows:
name: ZAP Security Scan
on: [push , pull_request ]
jobs:
zap_scan:
runs-on: ubuntu-latest
name: OWASP ZAP Baseline Scan
steps:
- name: Checkout
uses: actions/checkout@v2
- name: ZAP Baseline Scan
uses: zaproxy/action-baseline@v0.7.0
with:
target: 'https://staging.target-app.com'
rules_file_name: '.zap/rules.tsv'
cmd_options: '-a'
Docker Automation Framework Use YAML-based automation for advanced workflows:
docker run -v $(pwd ):/zap/wrk/:rw -t zaproxy/zap-stable \
zap.sh -cmd -autorun /zap/wrk/zap_automation.yaml
The bundled assets/zap_automation.yaml template includes:
Environment configuration
Spider and AJAX spider settings
Passive and active scan policies
Authentication configuration
Report generation
CI/CD Best Practices
Use baseline scans for every commit/PR (low false positives)
Run full scans on staging environments before production deployment
Configure API scans for microservices and REST endpoints
Set failure thresholds to break builds on high-severity findings
Generate SARIF reports for GitHub Security tab integration
See scripts/ci_integration.sh for complete CI/CD integration examples.
Security Considerations
Authorization : Always obtain written authorization before scanning production systems or third-party applicationsRate Limiting : Configure scan speed to avoid overwhelming target applications or triggering DDoS protectionsSensitive Data : Never include production credentials in scan configurations; use environment variables or secrets managementScan Timing : Run active scans during maintenance windows or against dedicated testing environmentsLegal Compliance : Adhere to computer fraud and abuse laws; unauthorized scanning may be illegalAudit Logging : Log all scan executions, targets, findings, and remediation actions for compliance auditsData Retention : Sanitize scan reports before sharing; they may contain sensitive application dataFalse Positives : Manually verify findings before raising security incidents; DAST tools generate false positives
Bundled Resources
Scripts (scripts/)
zap_baseline_scan.sh - Automated baseline scanning with configurable targets and reportingzap_full_scan.sh - Comprehensive active scanning with exclusion ruleszap_api_scan.py - API testing with OpenAPI/GraphQL specification supportzap_auth_scanner.py - Authenticated scanning with multiple authentication methodsci_integration.sh - CI/CD integration examples for Jenkins, GitLab CI, GitHub Actions
References (references/)
authentication_guide.md - Complete authentication configuration for form-based, OAuth, and token authenticationowasp_mapping.md - Mapping of ZAP alerts to OWASP Top 10 2021 and CWE classificationsapi_testing_guide.md - Advanced API testing patterns for REST, GraphQL, SOAP, and WebSocketscan_policies.md - Custom scan policy configuration for different application typesfalse_positive_handling.md - Common false positives and verification techniques
Assets (assets/)
zap_automation.yaml - Automation framework configuration templatezap_context.xml - Context configuration with authentication and session managementscan_policy_modern_web.policy - Scan policy optimized for modern JavaScript applicationsscan_policy_api.policy - Scan policy for REST and GraphQL APIsgithub_action.yml - GitHub Actions workflow templategitlab_ci.yml - GitLab CI pipeline template
Common Patterns
Pattern 1: Progressive Scanning (Speed vs. Coverage) Start with fast scans and progressively increase depth:
docker run -t zaproxy/zap-stable zap-baseline.py -t $TARGET_URL -r baseline.html
docker run -t zaproxy/zap-stable zap-baseline.py -t $TARGET_URL -r baseline.html -c baseline-rules.tsv
docker run -t zaproxy/zap-stable zap-full-scan.py -t $TARGET_URL -r full.html -c full-rules.tsv
Pattern 2: API-First Testing Prioritize API security testing:
docker run -v $(pwd ):/zap/wrk/:rw -t zaproxy/zap-stable zap-api-scan.py \
-t https://api.target.com -f openapi -d /zap/wrk/openapi.yaml -r /zap/wrk/api.html
python3 scripts/zap_auth_scanner.py --target https://api.target.com --auth-type bearer --token-env API_TOKEN
Pattern 3: Authenticated Web Application Testing Test complete application including protected areas:
python3 scripts/zap_auth_scanner.py \
--target https://app.target.com \
--auth-type form \
--login-url https://app.target.com/login \
--username testuser \
--password-env APP_PASSWORD \
--verification-url https://app.target.com/dashboard \
--output authenticated-scan.html
Pattern 4: CI/CD Security Gate Implement ZAP as a security gate in deployment pipelines:
docker run -t zaproxy/zap-stable zap-baseline.py \
-t https://staging.target.com \
-r baseline-report.html \
-J baseline-report.json \
--hook=scripts/ci_integration.sh
if [ $? -ne 0 ]; then
echo "Security scan failed! High-risk vulnerabilities detected."
exit 1
fi
Integration Points
CI/CD : GitHub Actions, GitLab CI, Jenkins, Azure DevOps, CircleCIIssue Tracking : Jira, GitHub Issues (via SARIF), ServiceNowSecurity Tools : Defect Dojo (vulnerability management), SonarQube, OWASP Dependency-CheckSDLC : Pre-production testing phase, security regression testing, penetration testing preparationAuthentication : Integrates with OAuth providers, SAML, API gateways, custom authentication scriptsReporting : HTML, JSON, XML, Markdown, SARIF (for GitHub Security), PDF (via custom scripts)
Troubleshooting
Issue: Docker Container Cannot Reach Target Application Solution : For scanning applications running on localhost or in other containers:
HOST_IP=$(ip -4 addr show docker0 | grep -Po 'inet \K[\d.]+' )
docker run -t zaproxy/zap-stable zap-baseline.py -t http://$HOST_IP :8080
docker network create zap-network
docker run --network zap-network -t zaproxy/zap-stable zap-baseline.py -t http://app-container:8080
Issue: Scan Completes Too Quickly (Incomplete Coverage) Solution : Increase spider depth and scan duration:
docker run -t zaproxy/zap-stable zap-baseline.py \
-t $TARGET_URL \
-r report.html \
-z "-config spider.maxDepth=10 -config spider.maxDuration=60"
For JavaScript-heavy applications, use AJAX spider or Automation Framework.
Issue: High False Positive Rate Solution : Create custom scan policy and rules file:
echo "10202 https://target.com/static/.* .* 798 IGNORE" >> .zap/rules.tsv
docker run -t zaproxy/zap-stable zap-baseline.py -t $TARGET_URL -c .zap/rules.tsv
Issue: Authentication Session Expires During Scan Solution : Configure session re-authentication:
python3 scripts/zap_auth_scanner.py \
--target $TARGET_URL \
--auth-type form \
--login-url https://target.com/login \
--username testuser \
--password-env PASSWORD \
--re-authenticate-on 401,403 \
--verification-interval 300
Issue: Scan Triggering Rate Limiting or WAF Blocking Solution : Reduce scan aggressiveness:
docker run -t zaproxy/zap-stable zap-baseline.py \
-t $TARGET_URL \
-r report.html \
-z "-config scanner.threadPerHost=1 -config scanner.delayInMs=1000"
References 