Skip to content

Commit 784a45c

Browse files
authored
Merge pull request #5627 from Shubham82/fix_link
Fix the link for Third-Party Security Audit Working Group.
2 parents d830438 + 3f917fe commit 784a45c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

sig-security/charter.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ This charter adheres to the conventions described in the [Kubernetes Charter REA
66

77
SIG Security covers horizontal security initiatives for the Kubernetes project, including regular security audits, the vulnerability management process, cross-cutting security documentation, and security community management. As a process-oriented SIG, it does not directly own Kubernetes component code. This SIG replaces the Security Audit Working Group. Instead, SIG Security focuses on improving the security of the Kubernetes project across all components.
88

9-
This SIG grew out of the [Third-Party Security Audit Working Group](https://github.com/kubernetes/community/tree/master/wg-security-audit), which managed each recurrent Third-Party Security Audit over the course of the audit’s lifecycle. The Working Group worked closely with selected vendors, the Product Security Committee, and the CNCF. It created the RFP, selected the vendors, and managed the vendors’ engagement with other SIGs and subject matter experts.
9+
This SIG grew out of the [Third-Party Security Audit Working Group](https://github.com/kubernetes/community/tree/master/sig-security/security-audit-2019), which managed each recurrent Third-Party Security Audit over the course of the audit’s lifecycle. The Working Group worked closely with selected vendors, the Product Security Committee, and the CNCF. It created the RFP, selected the vendors, and managed the vendors’ engagement with other SIGs and subject matter experts.
1010

1111
SIG Security continues to manage the third-party security audits, while serving a wider mission of advocating for security-related structural or systemic issues and default configuration settings, managing the non-embargoed (public) vulnerability process, defining the bug bounty, creating official Kubernetes Hardening Guides and security documents, and serving as a public relations contact point for Kubernetes security.
1212

0 commit comments

Comments
 (0)