Blog about new browser-based DAST active checks
Triage (REQUIRED)
Not appropriate for corporate communications.
Proposal
Browser-based DAST recently released the first of the GitLab-built active checks. This is included on the GitLab 16.4 release notes, but being a significant change in how the scanner works, I wanted to include a little more information about what the active checks are and how they work.
This blog post would be similar to the one about DAST passive checks.
Checklist
-
[ ]Does this align with a time-sensitive release, campaign or announcement? Please add link to pertinent info such as eBook landing page -
[ ]If wide-spread customer impacting or sensitive, mention@lboughner
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
[ ]If the post is about one of GitLab's Technology Partners, including integration partners, mention@mjoscelyn
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
[ ]If the post is about one of GitLab's customers, mention@nicolecsmith
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
[ ]Indicate if this post requires additional approval from internal or external parties before publishing (please tag needed sign off DRIs as necessary) -
[ ]Please upload any images to the MR before tagging the editorial team.