Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time
46 lines (33 sloc) 2.92 KB


Kubernetes Security Release Process and Security Committee documentation.

Product Security Committee (PSC)

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

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

Associate members include:

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

Emeritus members:

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

Contacting the PSC

There are a number of contact points for the PSC 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 PSC. 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 PSC 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.