-
-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global Auditing Views #349
Comments
Addition: Some filtering options, like filtering for projects with specific tags, or filter for a specific project and its children could be useful possibly too, especially if someone if using top level projects to group by department or similar |
Very excited to see some of the work in this come to fruition @rkg-mm. |
Looking forward to this! Without a global overview for policy-violations (and filter) etc. we'll have to go into each project and check, which is more than annoying. |
@strowi we have a basically working solution for both, vuln and audit views, we just need to find some time to fix some performance issues for big setups. I hope we can get it done soon and have it in next version. |
@rkg-mm thank you for the fast answer and the status update! wasn't sure if the target was short or long-term. |
Current Behavior
Dependency-Track is very project oriented today, which makes sense so far for the usage by each project team.
But it lacks features for a global Security Team, which is responsible to have an overview about all projects.
There is a "vulnerabilities" view, but as of today, it lists 23.609 vulnerabilities in my case, which are ALL vulnerabilities from all imported sources, not only the ones, which are found in a project. This makes sense for a specific use case: Managing own vulnerabilities, manually added. Apart from that, it doesn't seem to be very helpful.
Proposed Behavior
A new entry should be in the main menu, which leads to a set of views relevant to a global security team (or auditing team, if you want to include responsibles for license or other policy issues as well). Name to be found, but something like "Global Auditing" would describe it well probably.
This view should host different sub-views. Some examples I came up with or saw in other requests so far:
Each view should have a specific permission required to see it. E.g. somebody responsible for policy violations could only be responsible for licensing issues, while not handling vulnerabilities.
Questions to solve:
Checklist
The text was updated successfully, but these errors were encountered: