Skip to content
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

Update ZAP GitHub Actions URLs and images #2028

Merged
merged 1 commit into from
Aug 2, 2023
Merged
Show file tree
Hide file tree
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
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ authors:
- nirojan
---

[![zap-action](./images/zap-action.png)](https://github.com/marketplace/actions/owasp-zap-baseline-scan)
[![zap-action](./images/zap-action.png)](https://github.com/marketplace/actions/zap-baseline-scan)

With the increasing number of web application security breaches, it is essential to keep your web application secure at all times.
Furthermore having security integrated into your CI/CD pipeline (DevSecOps) will become a lifesaver if you are actively
Expand All @@ -25,7 +25,7 @@ such as — creating a new issue, pushing a commit, or on a scheduled basis. Thi
without involving any of your own infrastructures. The ZAP baseline action is available in the GitHub Marketplace under
the actions/security category.

The [ZAP baseline-action](https://github.com/marketplace/actions/owasp-zap-baseline-scan) can be configured to periodically
The [ZAP baseline-action](https://github.com/marketplace/actions/zap-baseline-scan) can be configured to periodically
scan a publicly available web application. Also, ZAP baseline-action can be configured to public and private repositories as well.
Based on the scan results ZAP will maintain an active issue in GitHub repository. The action will update the issue if it identifies
any new or resolved alerts and will close the issue if all the alerts have been resolved. A detailed report is attached to the
Expand Down Expand Up @@ -110,6 +110,6 @@ Also, you can view the scan logs by navigating to the ZAP [scan job](https://git


We are excited to hear your thoughts and feedback for the new ZAP Baseline Action. If you find the action useful please star the action.
Also, checkout our [ZAP full scan action](https://github.com/marketplace/actions/owasp-zap-full-scan) on how to perform active scanning
Also, checkout our [ZAP full scan action](https://github.com/marketplace/actions/zap-full-scan) on how to perform active scanning
on your web applications. Reach us through the [user group](https://groups.google.com/forum/#!forum/zaproxy-users) or for any additional
enhancements please feel free to create an issue in the [following repository](https://github.com/zaproxy/action-baseline).
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -12,11 +12,11 @@ authors:
- nirojan
---

[![zap-action](./images/zap-action.png)](https://github.com/marketplace/actions/owasp-zap-full-scan)
[![zap-action](./images/zap-action.png)](https://github.com/marketplace/actions/zap-full-scan)

[ZAP full scan GitHub action](https://github.com/marketplace/actions/owasp-zap-full-scan) provides free dynamic application
[ZAP full scan GitHub action](https://github.com/marketplace/actions/zap-full-scan) provides free dynamic application
security testing (DAST) of your web applications. DAST is also known as black-box testing, which allows ZAP to identify
potential vulnerabilities in your web applications. We previously introduced the [ZAP baseline scan GitHub action](https://github.com/marketplace/actions/owasp-zap-baseline-scan)
potential vulnerabilities in your web applications. We previously introduced the [ZAP baseline scan GitHub action](https://github.com/marketplace/actions/zap-baseline-scan)
to passively identify potential alerts in a web application. However, unlike the baseline scan, ZAP full scan attacks the web application
to find additional vulnerabilities.

Expand Down
6 changes: 3 additions & 3 deletions site/content/docs/docker/about.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,9 @@ The `zap_tuned()` [Scan Hook](../scan-hooks/) is called after these changes have
### GitHub Actions
The following GitHub Actions wrap the above packaged scans and also support raising GitHub issues for potential vulnerabilities found:

* [OWASP ZAP Baseline Scan](https://github.com/marketplace/actions/owasp-zap-baseline-scan)
* [OWASP ZAP Full Scan](https://github.com/marketplace/actions/owasp-zap-full-scan)
* [OWASP ZAP API Scan](https://github.com/marketplace/actions/owasp-zap-api-scan)
* [ZAP Baseline Scan](https://github.com/marketplace/actions/zap-baseline-scan)
* [ZAP Full Scan](https://github.com/marketplace/actions/zap-full-scan)
* [ZAP API Scan](https://github.com/marketplace/actions/zap-api-scan)

For more details see the blog posts:

Expand Down