<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=299959) </details> <!--IssueSummary end--> The following discussions from !50216 should be addressed: - [ ] @bmiller1 started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50216#note_468589076): (+5 comments) > Unsure if this MR meets the criteria to at-mention gitlab-com/gl-security/appsec. Please advise. - [ ] @bmiller1 started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50216#note_477798686): (+5 comments) > Good catch @lmcandrew. I missed that completely. > > I would like to see us catch this case further up the stack but I am still learning my way around the code flow. Moving it up too far and the reader loses the temporal context of the test. > > Do you have any recommendations as to a good point, both logially and contextually, to perform the test?