ef108be474
* Rename of Product Security Committee After some discussions, we decided to put it to the steering committee that a rename may be prudent, as 'Product' can be confusing (suggests downstream). The recommendation is Security Response Committee Ref: #5596 Signed-off-by: Luke Hinds <lhinds@redhat.com> * Generate docs Signed-off-by: Luke Hinds <lhinds@redhat.com> * Fix spelling mistake Signed-off-by: Luke Hinds <lhinds@redhat.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
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
- CJ Cullen (@cjcullen), Google
- Joel Smith (@joelsmith), Red Hat
- Luke Hinds (@lukehinds), Red Hat
- Micah Hausler (@micahhausler), Amazon
- Swamy Shivaganga Nagaraju (@swamymsft), Microsoft
- Tabitha Sable (@tabbysable), Datadog
- Tim Allclair (@tallclair), Apple
Contact
- Private Mailing List: security@kubernetes.io
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/security-response-committee - General Discussion
Subprojects
The following subprojects are owned by the Security Response Committee:
security
Policies and documentation for the Security Response Committee
- Owners: