<!---
This is an autogenerated file!

Please do not edit this file directly, but instead make changes to the
sigs.yaml file in the project root.

To understand how this file is generated, see https://git.k8s.io/community/generator/README.md
--->
# Security Response Committee

The Kubernetes Security Response Committee is the body that is responsible for receiving and responding to reports of security issues in Kubernetes projects.


## Members

* Sri Saran Balaji (**[@SaranBalaji90](https://github.com/SaranBalaji90)**), Amazon
* CJ Cullen (**[@cjcullen](https://github.com/cjcullen)**), Google
* Craig Ingram (**[@cji](https://github.com/cji)**), Google
* Mo Khan (**[@enj](https://github.com/enj)**), Microsoft
* Joel Smith (**[@joelsmith](https://github.com/joelsmith)**), Red Hat
* Luke Hinds (**[@lukehinds](https://github.com/lukehinds)**), Red Hat
* Micah Hausler (**[@micahhausler](https://github.com/micahhausler)**), Amazon
* Rita Zhang (**[@ritazh](https://github.com/ritazh)**), Microsoft
* Tabitha Sable (**[@tabbysable](https://github.com/tabbysable)**), Datadog

## Contact
- Private Mailing List: security@kubernetes.io
- [Open Community Issues/PRs](https://github.com/kubernetes/community/labels/committee%2Fsecurity-response)
- GitHub Teams:
    - [@kubernetes/security-response-committee](https://github.com/orgs/kubernetes/teams/security-response-committee) - General Discussion
- Steering Committee Liaison: Stephen Augustus (**[@justaugustus](https://github.com/justaugustus)**)

## Subprojects

The following [subprojects][subproject-definition] are owned by the Security Response Committee:
### committee-security-response
Policies and documentation for the Security Response Committee
- **Owners:**
  - [kubernetes/committee-security-response](https://github.com/kubernetes/committee-security-response/blob/main/OWNERS)

[subproject-definition]: https://github.com/kubernetes/community/blob/master/governance.md#subprojects
<!-- BEGIN CUSTOM CONTENT -->

<!-- END CUSTOM CONTENT -->
