Versioned security assessment

Report ID: SA-D46E6208

7/7/2026, 8:37:45 PM

dast-zap security assessment v8

Skill Security Certification Report

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

Highest confirmed finding severity

High

1 confirmed security finding requires attention.

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.

Most static detections are documentation or template examples for authorized OWASP ZAP DAST workflows, so they were dismissed as false positives. Confirmed issues remain for a privileged CI package-install step, an unsafe API-key-in-URL example, and hardcoded sample credentials in reusable authentication templates.

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

11 Files scanned · 2,913 Lines analyzed

3 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 116 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 96 evidence locations

Capability review items (2)
High
assets/github_action.yml:177
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
references/api_testing_guide.md:75
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 findings

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

Confirmed security concerns (1)

RISK-001 High
assets/zap_context.xml:120-122assets/zap_context.xml:143-145references/authentication_guide.md:77-80
Hardcoded Sample Credentials in Reusable Templates
The package includes reusable authentication examples with fixed passwords such as TestPassword123!, AdminPassword123!, and SecureP@ssw0rd. Users may copy these templates into real scan contexts and accidentally commit usable credentials.
The cited files contain literal password values in context templates and documentation. They are examples, but the files are intended to be copied for authenticated scans.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    High
    Hardcoded sample passwords appear in authentication templates and examples.
    Replace literal passwords with environment-variable placeholders and add comments that real credentials must never be committed.
  2. FIX-002
    High
    The API testing guide shows an API key in a query string.
    Remove the query-string API key pattern and recommend headers or environment-backed secret injection instead.
  3. FIX-003
    High
    The GitHub Actions template installs jq with sudo during the workflow.
    Use a pinned container image or preinstalled runner tooling to avoid runtime privileged package installation.

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.

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