l3montree-dev / l3montree-dev/devguard

Org/ Group/ Project Daily Risk Summary as E-Mail

Open
#2,075 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component/devguard-api component/devguard-web feature-request
Dominant language
Go
Stars
161
Forks
43
Avg merge
1d 8h
Merged PRs (30d)
37

Description

Is your feature request related to a problem? Please describe.
As I SOC / CERT / Securiy Body of my Org I would like a brief summary of newly identified risks for my Org - e.g. new critical CVEs grouped by Project in my daily e-mail inbox.

Ideas:

  • Daily (even with no new CVEs to make sure the "cronjob" runs and management is not wondering "do we have new CVEs or is the process broken?)
  • Weekly summary of the changes (new CVEs (by project) / fixed CVEs (by project) / Management Summary Stuff..)
  • Who can subscribe to this? everybody or a specific role?
  • Configurable Risk Threshold
  • Configurable "Project Exposure Threshold" (e.g. how many projects are affected by the new risk)
  • Configurable "Risk Matrix": sample
    • include every Risk > 9
    • OR include only Risk > 8 and project count > 5
    • OR include only Risk > 7 and project count > 10
  • List the amount of projects affected by the new risks
  • Exclude specific projects or only include specific projects
  • Configurable E-Mail Title (e.g. Placeholder for the specified projects)
  • Configurable Branches to be scanned or ignored / included

Related to #2074 - might be the same, just "on another level".

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified. Start by reviewing related issue #2074 and mapping the existing CVE, project-risk, subscription, threshold, and email workflows. Done requires an agreed scope for daily and weekly summaries, recipients, filters, thresholds, branch handling, and email configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.