Convert active and passive scan rules to scripts
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
ZAP has a large number of active and passive scan rules (the code that detects potential vulnerabilities) written in Java.
Converting these into one or more of the scripting languages that ZAP supports (which includes Javascript, Jython, Jruby and Zest) would allow users to easily tweak these rules to from within ZAP without having to use a full development environment.
This would be particularly useful for experienced pentesters who want to tune ZAP for a particular target application and/or vulnerability.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue targets ZAP's Java active and passive scan rules and proposes conversion to supported scripting languages, including Javascript, Jython, Jruby, and Zest. No files, tests, or entry points are named, so begin by inventorying the scan-rule implementations and their existing test coverage. Completion criteria for the conversion are not defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, javascript
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100