Expose Project Security Dashboard under new Vulnerability Report route
What does this MR do?
This MR simply prepares the necessary backend code to move the Security Dashboard page to Vulnerability Report. Today, the dashboard displays the vulnerability reports, but we want to display charts in this page therefore we'll move the Report into a separate page.
For the sake of iteration, I wanted to first create the backend code, and then work on the security dashboard migration in a separate MR.
This MR introduces no visual changes for the user.
Screenshots
Once enabled, the navigation will look like (though note this MR does not make the change below visible; they merely reflect what the eventual result will be in subsequent iterations).
| today | in the future |
|---|---|
 |
 |
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #235558 (closed)