Repository navigation
Add csaf email notifications final - #108
Merged
mmacata merged 3 commits intoSep 30, 2026
Merged
Conversation
mmacata
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds CSAF email notifications to the reusable SBOM vulnerability workflow. Notifications are sent for new Dependency-Track findings or relevant analysis state changes, with the validated CSAF VEX report attached. The last notified event is stored as a Dependency-Track project property to prevent duplicate emails. Email configuration uses the organization-level CYBERSECURITY_EMAIL variable and CYBERSECURITY_EMAIL_APP_PASSWORD secret. The README was updated accordingly.
The Dependency-Track analysis states IN_TRIAGE, NOT_AFFECTED, and EXPLOITABLE are mapped to the CSAF VEX product statuses under_investigation, known_not_affected, and known_affected. The RESOLVED state is currently left unmapped because there is no clear 1:1 equivalent. In CSAF, fixed specifically means that the affected product or version contains a fix, while RESOLVED in Dependency-Track only indicates that the analysis has been concluded and does not necessarily prove that a fix is present.