Update docs for Dependency Scanning to link to Application Security section on expected behaviour and configuration of secure scanners
MR
Problem to solve
Customers are unsure how our analyzers work and what the job statuses etc mean
we need to provide, for all scanners, clarity around that, as well as consistency
then each scanner can link to that area for an explanation of "how it works by default"
each scanner can then provide directions to alter that if a user wants.
to do for all scanners (sast, dast etc) nicole will work on and then get engineering approval and then tech writer approval
Further details
Proposal
Create a new section in the Dependency Scanning user documentation, briefly describe the new behavior, and link to the doc section created in #301123 (closed), in the Application Security user documentation.
The new doc section can be named after the one that's been created in Application Security user docs.
Who can address the issue
No special skill required