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

Add Scanner alerts to the dashboard #23

Open
abstractj opened this issue Nov 1, 2023 · 3 comments
Open

Add Scanner alerts to the dashboard #23

abstractj opened this issue Nov 1, 2023 · 3 comments

Comments

@abstractj
Copy link

Proposal

We currently don't have visibility of scanner alerts within our project. To address this, I suggest we leverage Keycloak dashboards to consolidate and display these alerts. This section allows our team to monitor the security alerts, now that they have permission to see security alerts. The section will show the current status of CVEs on third-party dependencies, container images, plus static code analysis.

Proposed layout:

  • Third-party dependencies - will have a link to the open alerts from Snyk and the count of the number of alerts
  • Container images - will have a link to the open alerts from Trivy and the count of the number of alerts
  • Issues in the codebase - will have a link to the open alerts from CodeQL and the count of the number of alerts

Attached is a prototype and if we agree about that, I can implement.

Screenshot from 2023-11-01 09-09-50

@abstractj
Copy link
Author

@stianst FYI

@stianst
Copy link
Owner

stianst commented Dec 12, 2023

Makes sense, I'd probably add a new page "Security" rather than add to an existing page. To implement you need to figure out what API to scrape, and do that as part of the update data job, which should be cached in the repo. Try to do it with as few API calls as possible as we can quickly run into API throttling from GH if we do to many invocations.

@abstractj
Copy link
Author

Makes sense, I'd probably add a new page "Security" rather than add to an existing page. To implement you need to figure out what API to scrape, and do that as part of the update data job, which should be cached in the repo. Try to do it with as few API calls as possible as we can quickly run into API throttling from GH if we do to many invocations.

Thanks will think about it.

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

No branches or pull requests

2 participants