|
9 | 9 | <BODY> |
10 | 10 | <H1>Release 2.16.0</H1> |
11 | 11 |
|
12 | | -This is a bug fix and enhancement release. |
13 | | -<br> |
| 12 | +This is a bug fix and enhancement release. Look out for new |
| 13 | +<a href="https://www.zaproxy.org/blog/">Blog Posts</a> and <a href="https://www.zaproxy.org/videos/">Videos</a> |
| 14 | +which will cover some of these new features in much more depth in the coming days and weeks. |
| 15 | +<p> |
| 16 | +This release was made possible thanks to <a href="https://checkmarx.com/">Checkmarx</a> |
| 17 | +who employ 3 of the <a href="https://www.zaproxy.org/docs/team/">Core Team</a> to work on ZAP. |
| 18 | +<p> |
14 | 19 | These release notes do not include all of the changes included in add-ons updated since 2.15.0. |
15 | 20 | <p> |
16 | 21 | Some of the more significant enhancements include: |
17 | 22 |
|
18 | 23 | <H3>Update to a Minimum of Java 17</H3> |
19 | 24 |
|
20 | | -TODO add details. |
| 25 | +ZAP now requires a minimum of Java 17 to run. This allows us to use more modern Java features in the ZAP codebase. |
21 | 26 |
|
22 | | -<H3>Menu Items Restructured</H3> |
| 27 | +<H3>Detachable Tabs</H3> |
23 | 28 |
|
24 | | -The desktop context sensitive menu items have been reordered, and grouped in a more logical way. |
25 | | -This should make it much easier to find the menu item you want, when you want it. |
| 29 | +You can now detach any of the ZAP desktop tabs so that they will appear in their own windows. |
| 30 | +This means that you can see more than one tab in the group at the same time, and allows you to distribute those windows |
| 31 | +across multiple monitors. |
| 32 | +Just right click any tab to see the 'detach' option and close the tab window to return it to the main ZAP window. |
26 | 33 |
|
27 | | -<H3>Detachable Tabs</H3> |
| 34 | +<H3>Standard Policy Definitions</H3> |
| 35 | + |
| 36 | +We now have a standard set of active scan policy definitions which we recommend for use in specific situations. |
| 37 | +Using these definitions will just enable the most suitable active scan rules. This will speed up your active scans |
| 38 | +and will reduce noise. Some of the standard active scan rules are really targetted at pentesters, and these can waste |
| 39 | +developers time. |
| 40 | +<p> |
| 41 | +For more details see the new <a href="https://www.zaproxy.org/docs/desktop/addons/scan-policies/">Scan Policies</a> add-on. |
| 42 | + |
| 43 | +<H3>Site Tree Export and Pruning</H3> |
28 | 44 |
|
29 | | -TODO add details. |
| 45 | +We now have a standard format for representing the Sites Tree in a text file: |
| 46 | +<a href="https://www.zaproxy.org/docs/desktop/addons/import-export/sites-tree-format/">Sites Tree Format</a>. |
| 47 | +This format uniquely identifies nodes in the Sites tree. |
| 48 | +While this might not sound particularly exciting, it does actually allow you to use ZAP to perform "differential" scans, |
| 49 | +i.e. only attacking endpoints that have changed. This means that ZAP can be used to perform really fast testing in CI/CD. |
30 | 50 |
|
31 | | -<H3>TODO Add More Headline Features</H3> |
| 51 | +<H3>Sequence Scanning Updates</H3> |
32 | 52 |
|
33 | | -TODO add details. |
| 53 | +The <a href="https://www.zaproxy.org/docs/desktop/addons/sequence-scanner/">Sequence Scanner</a> add-on has received |
| 54 | +significant attention. It now runs much more quickly and has full Automation Framework support. |
| 55 | +As a result it has been promoted to Beta status. |
| 56 | + |
| 57 | +<H3>Passive Scanner Moved into an Add-On</H3> |
| 58 | + |
| 59 | +The passive scanner has now been moved into an add-on: <a href="https://www.zaproxy.org/docs/desktop/addons/passive-scanner/">Passive Scanner</a>. |
| 60 | +We have an ongoing plan to move as much functionality out of the core as possible, as this allows us to push out fixes and |
| 61 | +enhancements much more quickly. |
| 62 | + |
| 63 | +<H3>Checkmarx Rebranding</H3> |
| 64 | + |
| 65 | +This release is the first full release with the "ZAP by Checkmarx" branding. |
34 | 66 |
|
35 | 67 | <H3>Docker Hub Organisation Deprecation</H3> |
36 | 68 |
|
37 | 69 | We will not use the <a href="https://hub.docker.com/u/softwaresecurityproject">softwaresecurityproject</a> org for 2.16.0 or following releases. |
38 | | - |
| 70 | +<p> |
39 | 71 | If you still use this org then please switch to <a href="https://hub.docker.com/u/zaproxy">zaproxy</a>. |
40 | 72 |
|
41 | 73 | <h3>Dependency Updates</h3> |
|
0 commit comments