Govern: Security Policies 17.4 Planning Issue

Previous planning issue: Govern: Security Policies 17.3 Planning Issue (#472374 - closed)

Narrative

During our last milestone, our team delivered substantial improvement to External Status Check: Add authentication to merge request external st... (#433035 - closed), which increases the security of External Status Checks, giving customers the ability to verify if the request is coming from the GitLab instance! Great work, team!

However, that was not the only area that our team was focused on. We moved forward with Use database read model for merge request appr... (&9971 - closed), Manage scheduled scan execution pipeline concur... (&13997 - closed) and Enforce, measure and increase Scan Execution Po... (&14460) (part of Refine Policy Application Limits (&8084)). Additionally, we are finalizing our work around Prevent branch modification when a policy disab... (&13776 - closed), which will be a great addition to our features as well! We continue our work around them, and we plan to close this refactoring and performance improvements in this milestone.

In the upcoming milestone, apart from finalizing the mentioned epics, we want to start working on new ones:

continue improvements around Pipeline Execution Policies with:
Improve compatibility between security policies... (&14119) - where we want to improve compatibility between Scan Execution and Merge Request Approval Policies and Security Analyzers,

Additionally, as in every release, we want to continue solving bugs to improve the UX of Security Policy features and ensure they work correctly. Our customers are increasingly interested in using our features, so we must ensure that Scan Execution and Merge Request Approval Policies work as expected.