Link to .cveignore process from security template

Robert Marshallrequested to merge
do-not-use-security-workflow-to-remove-cveignore-entry into master

What does this MR do?

While working on a deliverable, I found it difficult to discover whether or not CVEignore work should be handled as part of the Security process. This adds a note into the Security Harness in case someone gets to that point and hasn't found that information yet.

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on the dev.gitlab.org mirror for this branch if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened

Merge request reports