-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Blog post] Current State of findings from Kubernetes Third Party Security Audit of 2019 #56
Comments
@PushkarJ: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'm interested in working on this, but would likely need a bit of assistance. |
Awesome @cailynse Let me share a draft with you in next couple of weeks with placeholders where you could contribute :) |
I'm an editor for the Kubernetes blog, and I can help introduce folks to other people from the blog editorial side. |
Description
Write a blog post as pre-cursor to publication of third party security of audit 2021/22 that describes the current state of findings from the audit of 2019
Motivation
As we prepare for #13 it is useful, to take a look back current state of Third Party Security audit of 2019. This issue attempted to keep track of status of findings reported kubernetes/kubernetes#81146 . The blog post will attempt to dive deeper into this and become a point in time summary of the current state of the findings reported from 2019.
This will help folks gain confidence through transparent communication of work done by community to address the findings and bubble up any findings that need help from community contributors
/cc @reylejano
/sig security docs
/area security blog
/wg security-audit
The text was updated successfully, but these errors were encountered: