You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/zh/docs/reference/issues-security/security.md
+22-20Lines changed: 22 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
---
2
2
title: Kubernetes 安全和信息披露
3
+
aliases: [/zh/security/]
3
4
content_type: concept
4
5
weight: 20
5
6
---
@@ -27,7 +28,7 @@ This page describes Kubernetes security and disclosure information.
27
28
<!--
28
29
## Security Announcements
29
30
-->
30
-
## 安全公告
31
+
## 安全公告 {#security-announcements}
31
32
32
33
<!--
33
34
Join the [kubernetes-security-announce](https://groups.google.com/forum/#!forum/kubernetes-security-announce) group for emails about security and major API announcements.
@@ -37,28 +38,28 @@ Join the [kubernetes-security-announce](https://groups.google.com/forum/#!forum/
37
38
<!--
38
39
## Report a Vulnerability
39
40
-->
40
-
## 报告一个漏洞
41
+
## 报告一个漏洞 {#report-a-vulnerability}
41
42
42
43
<!--
43
-
We’re extremely grateful for security researchers and users that report vulnerabilities to the Kubernetes Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
44
+
We're extremely grateful for security researchers and users that report vulnerabilities to the Kubernetes Open Source Community. All reports are thoroughly investigated by a set of community volunteers.
44
45
-->
45
46
我们非常感谢向 Kubernetes 开源社区报告漏洞的安全研究人员和用户。
46
47
所有的报告都由社区志愿者进行彻底调查。
47
48
48
49
<!--
49
-
To make a report, please email the private [[email protected]](mailto:[email protected]) list with the security details and the details expected for [all Kubernetes bug reports](https://git.k8s.io/kubernetes/.github/ISSUE_TEMPLATE/bug-report.md).
50
+
To make a report, submit your vulnerability to the [Kubernetes bug bounty program](https://hackerone.com/kubernetes). This allows triage and handling of the vulnerability with standardized response times.
You can also email the private [[email protected]](mailto:[email protected]) list with the security details and the details expected for [all Kubernetes bug reports](https://github.com/kubernetes/kubernetes/blob/master/.github/ISSUE_TEMPLATE/bug-report.yaml).
You may encrypt your email to this list using the GPG keys of the [Security Response Committee members](https://git.k8s.io/security/README.md#product-security-committee-psc). Encryption using GPG is NOT required to make a disclosure.
- You need help tuning Kubernetes components for security
91
92
- You need help applying security related updates
92
93
- Your issue is not security related
93
94
-->
94
-
-你需要帮助调整 Kubernetes 组件的安全性
95
-
-你需要帮助应用与安全相关的更新
95
+
-你需要调整 Kubernetes 组件安全性的帮助
96
+
-你需要应用与安全相关更新的帮助
96
97
- 你的问题与安全无关
97
98
98
99
<!--
99
100
## Security Vulnerability Response
100
101
-->
101
-
## 安全漏洞响应
102
+
## 安全漏洞响应 {#security-vulnerability-response}
102
103
103
104
<!--
104
105
Each report is acknowledged and analyzed by Security Response Committee members within 3 working days. This will set off the [Security Release Process](https://git.k8s.io/security/security-release-process.md#disclosures).
Any vulnerability information shared with Product Security Team stays within Kubernetes project and will not be disseminated to other projects unless it is necessary to get the issue fixed.
110
+
Any vulnerability information shared with Security Response Committee stays within Kubernetes project and will not be disseminated to other projects unless it is necessary to get the issue fixed.
@@ -118,7 +119,7 @@ As the security issue moves from triage, to identified fix, to release planning
118
119
<!--
119
120
## Public Disclosure Timing
120
121
-->
121
-
## 公开披露时间
122
+
## 公开披露时间 {#public-disclosure-timing}
122
123
123
124
<!--
124
125
A public disclosure date is negotiated by the Kubernetes Security Response Committee and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation is available.
@@ -132,7 +133,8 @@ It is reasonable to delay disclosure when the bug or the fix is not yet fully un
The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. As a basic default, we expect report date to disclosure date to be on the order of 7 days. The Kubernetes product security team holds the final say when setting a disclosure date.
136
+
The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. For a vulnerability with a straightforward mitigation, we expect report date to disclosure date to be on the order of 7 days. The Kubernetes Security Response Committee holds the final say when setting a disclosure date.
0 commit comments