Skills dast-zap
๐Ÿ“ฆ

dast-zap

v0.1.0 Content revision r1 High Risk โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access๐Ÿ”‘ Env variables

Automate OWASP ZAP DAST Scans

Security teams need repeatable runtime testing before releases. This skill guides authorized OWASP ZAP scans, authentication setup, API testing, and CI reporting.

Supports: Claude Codex Code(CC)
โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "dast-zap" from https://skillstore.io/skills/agentsecops-dast-zap.md and its manifest at https://skillstore.io/api/skills/agentsecops-dast-zap/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "dast-zap". Plan a ZAP scan for a staging application before release.

Expected outcome:

  • Recommended a baseline scan on every merge request and a full scan before release.
  • Defined staging scope, report artifacts, and thresholds for high and medium findings.
  • Added authorization, rate limiting, and report review checkpoints.

Using "dast-zap". Set up authenticated scanning for a form login.

Expected outcome:

  • Outlined required login URL, test account, password environment variable, and verification URL.
  • Explained session checks and re-authentication handling for long scans.
  • Included guidance to keep credentials out of repository files.

Using "dast-zap". Triage ZAP findings after a scan.

Expected outcome:

  • Grouped findings by severity and OWASP category.
  • Separated likely false positives from items needing manual verification.
  • Suggested next remediation steps and evidence to collect.

Security Audit

High Risk
v9 โ€ข 7/23/2026 Open versioned report

Most static detections are documentation or visible templates for authorized OWASP ZAP testing and were dismissed as false positives. Confirmed issues include privileged package installation and an API-key-in-URL example. Semantic review also found reusable fixed credentials, fail-open GitLab gates, and mutable CI dependencies; no prompt injection or malicious intent was found.

11
Files scanned
2,913
Lines analyzed
2
Review items
0
False positives ignored

Confirmed security concerns (3)

High
Hardcoded Sample Credentials in Reusable Templates
Reusable authentication examples contain fixed passwords such as TestPassword123!, AdminPassword123!, and SecureP@ssw0rd. Users may copy these values into real scan contexts and expose accessible test accounts.
The cited files contain literal password values in copyable context templates and documentation. The example domains reduce immediate exposure but do not remove insecure-default risk.
High
Fail-Open GitLab Security Gates
The GitLab scan jobs suppress scanner failures with || true. The security gate also succeeds when the baseline report is absent.
The template explicitly suppresses three scanner exit codes and treats a missing report as a successful skip. This directly permits failed scans to bypass the gate.
High
Mutable CI Dependencies
The CI templates execute containers and actions referenced by mutable tags, including latest. A changed upstream tag could execute with repository permissions or CI secrets.
The cited workflows use version tags and latest container tags instead of immutable commit or image digests. CI executes those dependencies with workflow privileges.
Capability review items (2)

These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.

High
sudo privilege escalation
sudo apt-get update && sudo apt-get install -y jq
The GitHub Actions template installs jq with sudo at runtime. This is a real privileged CI step and increases supply-chain and runner-hardening risk if copied unchanged.
High
Generic API/secret keys
--target https://api.example.com?api_key=your-api-key \
The guide demonstrates placing an API key in a query string. Even with placeholder text, this pattern can leak credentials through logs, browser history, and proxies.

Risk Factors

โš™๏ธ External commands (50)
๐ŸŒ Network access (50)
assets/gitlab_ci.yml:10 assets/zap_context.xml:17 assets/zap_context.xml:20 assets/zap_context.xml:21 assets/zap_context.xml:22 assets/zap_context.xml:49 assets/zap_context.xml:56 assets/zap_context.xml:85 assets/zap_context.xml:165 assets/zap_context.xml:172 assets/zap_context.xml:173 assets/zap_context.xml:174 assets/zap_context.xml:175 references/api_testing_guide.md:26 references/api_testing_guide.md:39 references/api_testing_guide.md:50 references/api_testing_guide.md:57 references/api_testing_guide.md:68 references/api_testing_guide.md:75 references/api_testing_guide.md:90 references/api_testing_guide.md:93 references/api_testing_guide.md:120 references/api_testing_guide.md:133 references/api_testing_guide.md:144 references/api_testing_guide.md:211 references/api_testing_guide.md:316 references/api_testing_guide.md:318 references/api_testing_guide.md:329 references/api_testing_guide.md:330 references/api_testing_guide.md:392 references/api_testing_guide.md:397 references/api_testing_guide.md:401 references/api_testing_guide.md:406 references/api_testing_guide.md:417 references/api_testing_guide.md:422 references/api_testing_guide.md:432 references/api_testing_guide.md:436 references/api_testing_guide.md:456 references/api_testing_guide.md:466 references/authentication_guide.md:29 references/authentication_guide.md:31 references/authentication_guide.md:34 references/authentication_guide.md:56 references/authentication_guide.md:61 references/authentication_guide.md:63 references/authentication_guide.md:100 references/authentication_guide.md:113 references/authentication_guide.md:125 references/authentication_guide.md:140 references/authentication_guide.md:169
๐Ÿ“ Filesystem access (4)
๐Ÿ”‘ Env variables (2)
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/agentsecops-dast-zap/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/agentsecops-dast-zap/security.svg)](https://skillstore.io/skills/agentsecops-dast-zap?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/agentsecops-dast-zap?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentsecops-dast-zap/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/agentsecops-dast-zap.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

AgentSecOps. (2026). dast-zap security audit report (audit version 9) [Author version 0.1.0]. Skillstore. https://skillstore.io/skills/agentsecops-dast-zap/audits/9

BibTeX citation

@techreport{agentsecops-agentsecops-dast-zap-2026, author = {AgentSecOps}, title = {dast-zap security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/agentsecops-dast-zap/audits/9}, note = {Author version 0.1.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "dast-zap security audit report (audit version 9)" version: "0.1.0" type: report authors: - name: "AgentSecOps" date-released: "2026-07-23" url: "https://skillstore.io/skills/agentsecops-dast-zap/audits/9" identifiers: - type: other value: "skillstore:agentsecops-dast-zap:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
59
Architecture
100
Maintainability
87
Content
70
Community
91
Spec Compliance

What You Can Build

Add DAST to release checks

Create a CI job that runs ZAP against staging and publishes reports for release review.

Test authenticated application areas

Configure ZAP authentication context files and test protected pages with dedicated test accounts.

Validate API security coverage

Use OpenAPI, GraphQL, or SOAP guidance to scan API endpoints and review findings.

Try These Prompts

Plan a baseline scan
Help me plan an authorized OWASP ZAP baseline scan for my staging URL. Include scope, report outputs, and safe defaults.
Create CI scan steps
Draft CI steps for an OWASP ZAP scan against staging. Include artifacts, thresholds, and how to handle scan failures.
Configure authenticated scanning
Guide me through an authenticated ZAP scan using test credentials from environment variables and a verification URL.
Review API DAST strategy
Design an OWASP ZAP API testing workflow for OpenAPI and GraphQL endpoints. Include authentication, rate limits, and reporting.

Best Practices

  • Use dedicated staging targets and written authorization for every active scan.
  • Store scan credentials in environment variables or a secrets manager.
  • Review high-risk findings manually before suppressing or closing them.

Avoid

  • Run active scans against production or third-party systems without approval.
  • Commit ZAP context files that contain real passwords or API tokens.
  • Suppress all ZAP findings without documented verification.

Frequently Asked Questions

Does this skill run OWASP ZAP by itself?
No. It provides guidance and templates that a user or agent can apply in an authorized environment.
Can it test authenticated pages?
Yes. It explains form, token, OAuth, and basic authentication patterns for ZAP scans.
Can it scan APIs?
Yes. It covers OpenAPI, GraphQL, SOAP, and manual API testing approaches.
Is active scanning safe for production?
Active scanning can send attack payloads. Use staging or maintenance windows unless production approval is explicit.
Does it replace security review?
No. ZAP findings need validation, context, and prioritization by qualified reviewers.
What tools are required?
Docker and OWASP ZAP are the primary requirements. Some workflows may also use Python, Java, or CI tooling.

Developer Details

License

MIT

Author version

v0.1.0

Skillstore revision

r1

Ref

9e952417e76879bc9d853e1b8b2cd6d6d8d4a1c2

Maintenance freshness

7/24/2026

Usage

10 downloads ยท 219 views

File structure

๐Ÿ“ assets/

๐Ÿ“„ .gitkeep

๐Ÿ“„ github_action.yml

๐Ÿ“„ gitlab_ci.yml

๐Ÿ“„ zap_automation.yaml

๐Ÿ“„ zap_context.xml

๐Ÿ“ references/

๐Ÿ“„ api_testing_guide.md

๐Ÿ“„ authentication_guide.md

๐Ÿ“„ EXAMPLE.md

๐Ÿ“„ false_positive_handling.md

๐Ÿ“„ owasp_mapping.md

๐Ÿ“„ SKILL.md

More from AgentSecOps

View all
View all