Automation Framework version 0.44.0
·
3022 commits
to main
since this release
Added
- Active scan policy job.
- Add job to configure the active scanner,
activeScan-config. - Allow to enable/disable jobs (Issue 5845).
- Method to allow the user to set the exit code via a script.
- Add exitStatus job (Issue #6928)
Changed
- Update minimum ZAP version to 2.16.0.
- Maintenance changes.
- Updated automation framework documentation and templates for
activeScanjob to reflect changes to the default value of threadPerHost parameter - Update help for the "requestor" job.
- Update help to indicate that job order is important (Issue 8675).
- Fields with default or missing values are omitted for the following automation jobs in saved plans:
activeScandelayrequestor
Removed
- Remove job implementations that were previously migrated to the Passive Scanner add-on (Issue 7959).
Fixed
- Templates generated with
-autogenminor-autogenmaxwere invalid in some cases. - Allow to choose one thread for the
activeScanjob through the GUI. - Active Scan jobs will once again use the default policy if neither a policy nor a policyDefinition has been set.
- Bug in job alert tests related to alert matching.
- Active scan rule ID 0 (Directory Browsing) will be included in the plan (yaml) when saved (Issue 8746).
- Sizing/display of the Active Scan Policy job rule add/modify dialogs.