Versioned security assessment

Report ID: SA-9029957F

6/28/2026, 5:27:19 AM

dast-zap security assessment v6

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
dast-zap
Version
v6
Maintainer
AgentSecOps
Source
github.com/AgentSecOps/SecOpsAgentKit/tree/main/skills/appsec/dast-zap
Coverage
10 Files scanned · 2,903 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

Static analysis produced many command, network, filesystem, and secret-related matches, but most are documented OWASP ZAP examples and CI templates. No prompt injection or confirmed malicious exfiltration was found. The real risk is that the skill enables active security scanning and executable automation, so users need authorization and review before use.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

10 Files scanned · 2,903 Lines analyzed

4 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 130 evidence locations

Filesystem access

May read or write local files.

Observed in 4 evidence locations

Env variables

May read values from the process environment.

Observed in 2 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 237 evidence locations

Capability review items (4)
Medium
SKILL.md:99-121assets/zap_automation.yaml:112-127
Authorized Active DAST Traffic Required
The skill provides active OWASP ZAP scan guidance and an automation job that can send attack traffic to target applications. This is legitimate security testing, but it can disrupt systems or violate policy if run without written authorization.
The cited sections explicitly describe active scanning and include an activeScan job. The risk depends on user authorization, so this is a confirmed operational risk rather than malicious behavior.
Medium
assets/github_action.yml:174-181assets/gitlab_ci.yml:21-30assets/gitlab_ci.yml:55-69
Executable CI and Docker Templates Need Review
The bundled CI templates run Docker-based ZAP scans and install parsing tools in pipeline environments. The commands are expected for this skill, but marketplace users should review targets, mounts, and permissions before use.
Static command findings map to real shell commands in CI templates. They appear purposeful and not obfuscated, but they execute in user infrastructure and warrant review.
Low
assets/zap_automation.yaml:33-47SKILL.md:149-157
Secret References Are Environment Placeholders
The analyzer flagged API key and credential references. The reviewed files use environment-variable placeholders for ZAP and test authentication rather than hardcoded secret values.
The evidence shows placeholder variables such as TEST_PASSWORD and ZAP_API_KEY. No literal credential value was found in the reviewed lines.
Low
references/api_testing_guide.md:219-231references/false_positive_handling.md:160-172
Sensitive File Paths Appear in Test Payload Documentation
The sensitive file detections are examples for XXE and path traversal verification. They do not show the skill reading local files or collecting host credentials.
The paths appear inside labeled vulnerability test payload examples. The context supports a false-positive classification for local credential access.

Risk findings

Confirmed security concerns are separated from items that still need review.

No confirmed security findings were recorded for this completed audit.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Static false positives ignored (1)
Low
SKILL.md:37-58assets/zap_context.xml:15-22assets/gitlab_ci.yml:8-11
Hardcoded URLs Are Example Targets
Hardcoded URL findings use example.com, target-app.com, staging hosts, or official documentation links. These are examples and references, not hidden outbound endpoints.
The reviewed URLs are visible configuration examples and documentation references. I did not find evidence of covert network destinations.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable