<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently piloting, details can be found in this issue: https://gitlab.com/gitlab-com/Product/-/issues/1392 and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. --> ### Release notes Today, the vulnerability management experience at the Instance level is limited in both functionality and flexibility. The current experience is a single page that combines vulnerability details, metrics visualizations, and configuration. It does not offer much room to expand any of these functions nor does it lend itself well to be leveraged by our other security features. We've made a foundational change to security visibility and management in GitLab. The Instance Security Dashboard has been transformed into a Security Center. The biggest change is introducing a new menu structure. Rather than a single page, you will now find a Security Dashboard, Vulnerability Report, and Settings area. While functionally the same as the old page, breaking things apart enables future enhancements that would have been difficult otherwise. This also creates a top-level framework for including other security-related functionality in the future. The dedicated Vulnerability Report now has more room to display important details and will inherit those currently found on the Project vulnerability list. Separating the vulnerability metrics widgets into their own area creates a true Security Dashboard. This is now a dedicated canvas for future visualizations—not just for managing vulnerabilities for but for any of our security-related metrics. Finally, splitting out Settings into their own area creates a new shared space for instance-level security configuration beyond vulnerability management. Documentation: https://docs.gitlab.com/ee/user/application_security/security_dashboard/#instance-security-dashboard  ### Overview The current Instance Security Dashboard is limited in both functionality and visibility (because of its menu placement). This Epic will cover rethinking both the design and layout. We will redesign the current Instance Security Dashboard to become the information architecture/navigation structure for a future central point of security visibility and management in GitLab. For Viable, this is primarily about taking the current single-page dashboard and establishing a new menu structure for additional future features. A first step is splitting out the Vulnerability list into a separate page/area. ### Proposal 1. Split Vulnerability List from Instance Security Dashboard 1. Create Settings area for instance-wide configuration of security settings, policies, and tools configurations 1. Provide UI menu structure/site map and placeholder spaces for other Secure & Defend groups to build their needed settings, visualizations 1. Create Instance Security Dashboard configuration area