-
Notifications
You must be signed in to change notification settings - Fork 56
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
Feature: specify minimum severity #9
Comments
You can effectively already do this by setting any rules you are not interested in to IGNORE in your rules file. This is a finer grain control, but will have the same effect. I worry that creating too many options will make the action harder to understand and therefore less useful. |
Can you create an info page here or in ZAP docs with all rules? I found that, but I need to run the scan in my local machine and get the ´gen.conf´. Maybe with it in docs, we can help more people that don't know the ZAP profoundly. I don't know if rules are updated weekly, in this case, we need some actions to update the docs every time that a rule is added. My gen.conf generate today:
|
You mean like this one https://www.zaproxy.org/docs/alerts/ ? |
Exactly, thanks! Can you add this link in GH Actions please? |
How can i report after i get alerts. Actually Bug bounty Platforms need Impact with POC . How can i report. Any suggestions. |
In that case you're the "expert" not ZAP. Also the User Group is a much better place for discussion not our issue tracker. |
Since ZAP vulnerability scans can generate a lot of issues, it might be nice to be able to e.g. ignore any LOW or INFO vulnerabilities. (so that issues are not created)
e.g.
The text was updated successfully, but these errors were encountered: