Skip to content

Re-enable ZAP Scan step in DAST workflow #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 22, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions .github/workflows/DAST-ZAP-Zed-Attach-Proxy-Checkmarx.yml
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,10 @@
with:
allow_issue_writing: false
target: "${{ env.ZAP_TARGET }}"
# - name: ZAP Scan
# uses: zaproxy/[email protected]
# with:
# target: "${{ env.ZAP_TARGET }}"
- name: ZAP Scan
uses: zaproxy/[email protected]

Check warning

Code scanning / CodeQL

Unpinned tag for a non-immutable Action in workflow Medium

Unpinned 3rd party Action 'DAST - Zed Attack Proxy (ZAP) Full Scan' step
Uses Step
uses 'zaproxy/action-baseline' with ref 'v0.4.0', not a pinned commit hash
with:
target: "${{ env.ZAP_TARGET }}"
- uses: SvanBoxel/zaproxy-to-ghas@main
- name: Upload SARIF file
uses: github/codeql-action/upload-sarif@v3
Expand Down
Loading