Skip to content
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

Open
2 tasks done
rkg-mm opened this issue Dec 7, 2022 · 5 comments
Open
2 tasks done

Global Auditing Views #349

rkg-mm opened this issue Dec 7, 2022 · 5 comments
Labels
enhancement New feature or request

Comments

@rkg-mm
Copy link
Contributor

rkg-mm commented Dec 7, 2022

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:

  1. Flat list of Vulnerabilities (see Add View to list latest vulnerabilities and policy violations of all projects dependency-track#1770), which can help to e.g. sort by "newest" occurance date, to go through stuff added in the last days to a project
  2. Flat list of Policy violations (also part of Add View to list latest vulnerabilities and policy violations of all projects dependency-track#1770), same as above, would I would separate them due to different fields and possible permissions
    • Including filters to filter for specific policies
  3. Vulnerability summary: A list of vulnerabilities currently found in all projects, grouped by vulnerability alias. Showing some vulnerability details (criticality, name, etc.) plus a count, to how many projects it applies. Clicking the entry will show a list of affected projects linking to them.
  4. A list of suppressed findings, see system wide vulnerability management dependency-track#1495
  5. More ideas or known tickets that could be included? -> Put in comments and I'll add them

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:

  1. Will this show all projects information (requiring a permission to see every project independent of ACL) or only projects I have access to (following ACL permissions). Not sure how much impact the ACL checks would have on the performance here.
  2. Good name for it?

Checklist

@rkg-mm rkg-mm added the enhancement New feature or request label Dec 7, 2022
@rkg-mm
Copy link
Contributor Author

rkg-mm commented Dec 8, 2022

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

@stgarf-sx
Copy link

stgarf-sx commented Apr 28, 2023

Very excited to see some of the work in this come to fruition @rkg-mm.

@strowi
Copy link

strowi commented May 10, 2023

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.

@rkg-mm
Copy link
Contributor Author

rkg-mm commented May 10, 2023

@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.

@strowi
Copy link

strowi commented May 10, 2023

@rkg-mm thank you for the fast answer and the status update! wasn't sure if the target was short or long-term.
Looking forward to it. 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants