Document recommendation for appsec review of new gems
What does this MR do and why?
I think we've already been requesting appsec reviews for new gems. New gem additions happen very infrequently so it should not be much additional burden on AppSec and I think the risk can be underappreciated so I think it's important to document this somewhere. I couldn't find this written explicitly anywhere in our docs already but I did find it probably should also get some mentions in the appsec security pages as well.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.