Update DAST vulnerability definitions

Problem to solve

DAST pins to specific versions of vulnerability definitions. There has recently been a release of one of the definitions, so it is likely worth incorporating these into DAST.

Intended users

• Sasha (Software Developer)
• Sam (Security Analyst)

Further details

ZAP extension releases:

• Passive scanner rules version 28
• FuzzDB Files version 6

Proposal

• The latest versions of extensions release should be pinned in the DAST Dockerfile
• Tests should be updated
• A changelog should be added
• DAST should be released

Documentation

None required.

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Gold/Ultimate

Links / references