-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Misc ZAP Updates #914
Conversation
…pliance-enforcement into CE-1378-zap-updates
…pliance-enforcement into CE-1378-zap-updates
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really appreciate the work on this, always nice to do cleanup, improve standards and workflows.
Reading through the leftover ZAPs, none stick out as concerning. As with most policy tools you get some noise.
target: https://${{ env.PREFIX }}-frontend.${{ env.DOMAIN }}/api | ||
- name: Check for Back End High Risk Alerts | ||
run: | | ||
HIGH_RISK_COUNT=$(jq '[.site[].alerts[] | select(.riskcode == "3")] | length' report_json.json) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really clever use of jq in the zap report output!
Description
Please provide a summary of the change and the issue fixed. Please include relevant context. List dependency changes.
Made some changes to the Caddy File and Libraries in order to address the following vulnerabilities:
- CSP: Wildcard Directive
- CSP: script-src unsafe-eval
- CSP: script-src unsafe-inline
- Dangerous JS Function (Upgraded library)
- Deprecated Feature Policy Header Set
Updated the GitHub actions to do the following:
The following ZAP reports were unable to be resolved:
Fixes # (issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist
Further comments
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in:
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in:
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in:
Thanks for the PR!
Deployments, as required, will be available below:
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: