roles: Split security team by areas#422
Merged
Merged
Conversation
joestringer
commented
Jul 15, 2026
joestringer
commented
Jul 15, 2026
mtardy
approved these changes
Jul 15, 2026
mtardy
left a comment
mtardy
left a comment
Member
There was a problem hiding this comment.
from tetragon and my PoV, lgtm, thanks for doing this!
kkourt
reviewed
Jul 15, 2026
joestringer
commented
Jul 15, 2026
joestringer
force-pushed
the
pr/joe/security-overhaul
branch
from
July 21, 2026 23:07
faa0766 to
3b85546
Compare
joestringer
added
the
dont-merge/maintainer-coordination
kkourt
approved these changes
Jul 22, 2026
joestringer
marked this pull request as ready for review
July 22, 2026 20:43
joestringer
force-pushed
the
pr/joe/security-overhaul
branch
2 times, most recently
from
July 22, 2026 20:44
352aeaf to
393276d
Compare
Following discussion with Peter about how to manage the current wave of security reports across the organization, I thought it may be useful to establish three teams with clear responsibilities. The security team overall will be a superset of these teams, then these teams can determine internally how to handle security response within their specific domains (overall response, general cilium, and tetragon). Signed-off-by: Joe Stringer <[email protected]>
Signed-off-by: Kornilios Kourtis <[email protected]>
This reflects the more narrow default scope for this team (primarily focused on the Cilium subproject). Signed-off-by: Joe Stringer <[email protected]>
joestringer
force-pushed
the
pr/joe/security-overhaul
branch
from
July 22, 2026 20:46
393276d to
079afd5
Compare
joestringer
removed
the
dont-merge/maintainer-coordination
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
9 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.
Following discussion with Peter about how to manage the current wave of
security reports across the organization, I thought it may be useful to
establish three teams with clear responsibilities. The security team
overall will be a superset of these teams, then these teams can
determine internally how to handle security response within their
specific domains (overall response, general cilium, and tetragon).
Fixes: #356