Skip to content

Commit 84c6479

Browse files
authored
Add security reporting page (#253)
Signed-off-by: Mike Ng <[email protected]>
1 parent 4e8c52e commit 84c6479

File tree

1 file changed

+30
-0
lines changed

1 file changed

+30
-0
lines changed

content/en/docs/security/_index.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
title: Security
3+
weight: 9
4+
---
5+
6+
The Open Cluster Management (OCM) community welcomes and appreciates responsible disclosure of security vulnerabilities.
7+
8+
If you know of a security issue with OCM, please report it to [[email protected]](mailto:[email protected]).
9+
The OCM project owners receive security disclosures by default.
10+
They may share disclosures with others as required to make and propagate fixes.
11+
12+
The OCM community security reporting process follows the
13+
[Kubernetes security reporting process](https://kubernetes.io/docs/reference/issues-security/security/)
14+
as standard.
15+
16+
## Security Vulnerability Response
17+
18+
Each report is acknowledged and analyzed by OCM project owners within 5 working days.
19+
This will set off the Security Release Process.
20+
21+
Any vulnerability information shared with OCM project owners stays within the OCM community
22+
and will not be disseminated to other projects unless it is necessary to get the issue fixed.
23+
24+
As the security issue moves from triage, to identified fix, to release planning we will keep the reporter updated.
25+
26+
## Security Release Process
27+
28+
Refer to the Kubernetes
29+
[Security Release Process](https://github.com/kubernetes/committee-security-response/blob/main/security-release-process.md)
30+
for details on the security disclosures and response policy.

0 commit comments

Comments
 (0)