Define process to detect, fix and release critical issues on released fleetdm/fleet
docker images.
#25902
Labels
~engineering-initiated
Engineering-initiated story, such as a bug, refactor, or contributor experience improvement.
#g-orchestration
Orchestration product group
:release
Ready to write code. Scheduled in a release. See "Making changes" in handbook.
~risk-reduction
Related to improvements that could help reduce risk of outages, security, privacy, or trust issues.
Goal
Fleet to detect vulnerabilities in released fleetdm/fleet docker images (instead of our customers/users reporting them to us), e.g. #25748.
We need to:
status.md
somewhere on our repository).Examples:
PS: Our process should start with
CRITICAL
vulnerabilities and then iterate toHIGH
severity later.The text was updated successfully, but these errors were encountered: