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

Improved Active/Passive Rules Management #3870

Open
davewichers opened this issue Sep 6, 2017 · 2 comments
Open

Improved Active/Passive Rules Management #3870

davewichers opened this issue Sep 6, 2017 · 2 comments

Comments

@davewichers
Copy link

I'm finding the Scan configuration manager a bit confusing. Here are some suggested improvements:

Apparently the 'Active' scan rules are managed by the Analyse->Scan Policy Manager, but the Passive rules are managed under 3 items buried under Options.

I suggest we put both the Active and Passive scan management options under the Analyse menu and label what's there now the 'Active' Scan Policy Manager, and put the other 3 under a new item 'Passive' Scan Policy Manager. The Passive Scan Policy Manager can manage the 3 passive options we have under Options currently. This will also remove 3 items from the Options list, which is REALLY long.

I think it would be good to add indications in both the Active and Passive scan policy managers that there are Beta and Alpha rules that they can import and provide buttons/links to get them. Either via the download plugin interface, or by direct file import.

I also think we should clarify how/where someone can download plugins if they are using ZAP offline and then import them via the File->Import or whatever feature is used to pull in plugins that way.

@psiinon
Copy link
Member

psiinon commented Sep 7, 2017

Maybe just move the Passive Scan Rules, as the Tags are logically different, and the Passive Scanner pane is equivalent to the Active Scan one?
Note we also have a Active Scan Input Vectors pane.
Theres no reason why the Scan Policy Manager couldnt have (std gear) buttons for the relevant Option pages...

@benken-parasoft
Copy link

The problem is that there does not seem to be any simple way for an organization to easily define and distribute a unified scan policy. Having the active scan rules configured in a policy file only accomplishes half the goal. For the passive scan, the "policy" would need to take the form of a script (or something) to configure what rules are enabled and the alert threshold for each of them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants