process: document the VMT vulnerability management process - #1291
Draft
vdemeester wants to merge 1 commit into
Draft
process: document the VMT vulnerability management process#1291vdemeester wants to merge 1 commit into
vdemeester wants to merge 1 commit into
Conversation
The reporter-facing security policy lives in tektoncd/.github, but the team-side process the VMT actually follows is undocumented. New contributors have no way to learn how triage, embargoed fix development, or publication work, and there is no written expectation of what VMT membership involves. Add process/security-vmt.md covering scope, intake, triage states and timelines, private fix development, publication, the weekly digest, membership, and escalation. It links to the security policy rather than duplicating it. Several points are marked TODO where the team has not yet decided: downstream pre-notification, the on-call rotation model, and the inactivity threshold for offboarding. Triage and fix-time objectives are proposals and need VMT agreement.
tekton-robot
added
kind/documentation
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
tekton-robot
added
the
size/L
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.
Changes
Adds
process/security-vmt.md, a team-facing document for the Tekton Vulnerability Management Team (VMT), plus a TOC entry inprocess/README.md.Today there is no written VMT process anywhere. The reporter-facing policy lives in
tektoncd/.github/SECURITY.mdand is intentionally not duplicated here — this doc links to it and covers what happens on the team side.Sections: scope, intake, triage (states / CVSS / SLO table), fix development (private forks, embargo), publication, weekly digest & staleness, membership (job, assignment, joining, permissions, leaving), escalation.
Why draft
This is opened as a draft to gather VMT and community feedback, not to merge as-is. Several points are proposals rather than descriptions of current practice:
SECURITY.md.TODOblocks remain in the doc, each needing a team decision:Feedback on the numbers and on the three TODOs is exactly what I'm looking for. Happy to split this up or move sections elsewhere if reviewers prefer.
/kind documentation