Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.


Kubernetes Security Release Process and Security Committee documentation.

Security Response Committee (SRC)

The Security Response Committee (SRC) is responsible for triaging and handling the security issues for Kubernetes. Following are the current Security Response Committee members:

  • CJ Cullen (@cjcullen) <>
  • Joel Smith (@joelsmith) <> [4096R/0x1688ADC79BECDDAF]
  • Luke Hinds (@lukehinds)
  • Micah Hausler (@micahhausler) <>
  • Swamy Shivaganga Nagaraju (@swamymsft) <>
  • Tabitha Sable (@tabbysable) <>
  • Tim Allclair (@tallclair) <>

Associate members include:

  • Mo Khan (@enj) <>
  • Sam Fowler (@sfowl) <>
  • Taahir Ahmed (@ahmedtd) <>

Emeritus members:

  • Brandon Philips (@philips) <>
  • Jess Frazelle (@jessfraz) <>
  • Jonathan Pulsifer (@jonpulsifer) <>
  • Jordan Liggitt (@liggitt) <> [4096R/0x39928704103C7229]
  • Craig Ingram (@cji) <>

Contacting the SRC

There are a number of contact points for the SRC and release managers in charge of security releases. Please use the correct forum for the best and fastest response.

List or Group Visibility Uses Private Kubernetes security disclosures. This list is closely monitored and triaged by the SRC. See the disclosure guide for full details.
kubernetes-security-discuss Google Group Public Discussion about security disclosure handling, this document, and other updates. Private Release Managers private discussion. All members are subscribed to Private SRC private discussion. All members are subscribed to

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.


Kubernetes Security Process and Security Committee docs




No releases published


No packages published