Scope Security Dashboard for Projects with Production deployments or Releases
Release notes
Problem to solve
The security dashboard capability today shows all projects without any discrimination for the state of that project which makes it difficult to determine what items are most important to look at.
An example of a Security Dashboard that would benefit from an option to more narrowly scope the projects
Intended users
Metrics
User experience goal
Security Analysts ought to quickly be able to look for the projects that need to be secured on the Security Dashboard.
Proposal
We ought to provide users the ability to filter out projects that have either:
- Create a Release Object
- Deployed to Production
Further details
This could then allow security analysts look only at projects that ought to have good security practices and allow developers to have projects that need less scrutiny.
- This complements the Scan Execution Policies as they also align to "production" requirements.
- We could use this to make the Security Dashboard valuable for non-ultimate customers! They could answer - "how many projects" are deploying to production or releasing and don't have security setup!
- Additional efforts to make deployments more valuable at the group level: &4276
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.