Skip to content

Commit 8e0064d

Browse files
committed
feat: security and code of conduct addition and slack URL fix
Signed-off-by: Aditya Prasad Mohanty <[email protected]>
1 parent 874debd commit 8e0064d

File tree

5 files changed

+95
-3
lines changed

5 files changed

+95
-3
lines changed

CODE_OF_CONDUCT.md

+47
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
## Community Code of Conduct v1.0
2+
3+
This is Code of Conduct is based on the [CNCF Code of
4+
Conduct](https://github.com/cncf/foundation/edit/master/code-of-conduct.md).
5+
See the referred document for translated versions into different languages. The
6+
text below is modified with KubeArmor community specific contact details.
7+
8+
### Contributor Code of Conduct
9+
10+
As contributors and maintainers of this project, and in the interest of fostering
11+
an open and welcoming community, we pledge to respect all people who contribute
12+
through reporting issues, posting feature requests, updating documentation,
13+
submitting pull requests or patches, and other activities.
14+
15+
We are committed to making participation in this project a harassment-free experience for
16+
everyone, regardless of level of experience, gender, gender identity and expression,
17+
sexual orientation, disability, personal appearance, body size, race, ethnicity, age,
18+
religion, or nationality.
19+
20+
Examples of unacceptable behavior by participants include:
21+
22+
* The use of sexualized language or imagery
23+
* Personal attacks
24+
* Trolling or insulting/derogatory comments
25+
* Public or private harassment
26+
* Publishing others' private information, such as physical or electronic addresses,
27+
without explicit permission
28+
* Other unethical or unprofessional conduct.
29+
30+
Project maintainers have the right and responsibility to remove, edit, or reject
31+
comments, commits, code, wiki edits, issues, and other contributions that are not
32+
aligned to this Code of Conduct. By adopting this Code of Conduct, project maintainers
33+
commit themselves to fairly and consistently applying these principles to every aspect
34+
of managing this project. Project maintainers who do not follow or enforce the Code of
35+
Conduct may be permanently removed from the project team.
36+
37+
This code of conduct applies both within project spaces and in public spaces
38+
when an individual is representing the project or its community.
39+
40+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
41+
reported by contacting the project maintainers or our mediator, Nandhini Ananthakalyanaraman
42+
(<[email protected]>). Individuals found to be in violation of the Code of Conduct may be
43+
removed from the project and prevented from future participation.
44+
45+
This Code of Conduct is adapted from the Contributor Covenant
46+
(http://contributor-covenant.org), version 1.2.0, available at
47+
http://contributor-covenant.org/version/1/2/0/

SECURITY.md

+45
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
# Security Policy
2+
The Maintainers and contributors to KubeArmor take the security of our software seriously.
3+
The KubeArmor community has adopted the below security disclosures and response policy to promptly respond to critical issues.
4+
5+
Please do not report security vulnerabilities through public GitHub issues.
6+
7+
## Security bulletins
8+
For information regarding the security of this project please join our [slack channel](https://join.slack.com/t/kubearmor/shared_invite/zt-2bhlgoxw1-WTLMm_ica8PIhhNBNr2GfA).
9+
10+
## Reporting a Vulnerability
11+
### When you should?
12+
- You think you discovered a potential security vulnerability in KubeArmor.
13+
- You are unsure how a vulnerability affects KubeArmor.
14+
- You think you discovered a vulnerability in the dependency of KubeArmor. For those projects, please leverage their reporting policy.
15+
16+
### When you should not?
17+
- You need assistance in configuring KubeArmor for security - please discuss this is in the [slack channel](https://join.slack.com/t/kubearmor/shared_invite/zt-2bhlgoxw1-WTLMm_ica8PIhhNBNr2GfA).
18+
- You need help applying security-related updates.
19+
- Your issue is not security-related.
20+
21+
### Please use the below process to report a vulnerability to the project:
22+
1. Email the **KubeArmor security group at [email protected]**
23+
24+
* Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
25+
* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
26+
* Full paths of the source file(s) related to the manifestation of the issue
27+
* Location of the affected source code (tag/branch/commit or direct URL)
28+
* Any special configuration required to reproduce the issue
29+
* Step-by-step instructions to reproduce the issue
30+
* Proof-of-concept or exploit code (if possible)
31+
* Impact of the issue, including how an attacker might exploit the issue
32+
33+
* These information will help us triage your report more quickly.
34+
35+
2. The project security team will send an initial response to the disclosure in 3-5 days. Once the vulnerability and fix are confirmed, the team will plan to release the fix in 7 to 28 days based on the severity and complexity.
36+
37+
3. You may be contacted by a project maintainer to further discuss the reported item. Please bear with us as we seek to understand the breadth and scope of the reported problem, recreate it, and confirm if there is a vulnerability present.
38+
39+
## Supported Versions
40+
KubeArmor versions follow [Semantic Versioning](https://semver.org/) terminology and are expressed as x.y.z:
41+
- where x is the major version
42+
- y is the minor version
43+
- and z is the patch version
44+
45+
Security fixes may be backported to some recent minor releases, depending on severity and feasibility. Patch releases are cut from those branches periodically, plus additional urgent releases, when required.

docusaurus.config.js

+1-1
Original file line numberDiff line numberDiff line change
@@ -238,7 +238,7 @@ const config = {
238238
},
239239
{
240240
label: "Slack",
241-
to: "https://join.slack.com/t/kubearmor/shared_invite/zt-1ltmqdbc6-rSHw~LM6MesZZasmP2hAcA/",
241+
to: "https://join.slack.com/t/kubearmor/shared_invite/zt-2bhlgoxw1-WTLMm_ica8PIhhNBNr2GfA",
242242
},
243243
{
244244
label: "LinkedIn",

src/components/HomepageCommunity/index.js

+1-1
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ export default function HomepageCommunity() {
4242
cardIcon={communityLogo1}
4343
/>
4444
<Card
45-
cardLink="https://join.slack.com/t/kubearmor/shared_invite/zt-1ltmqdbc6-rSHw~LM6MesZZasmP2hAcA/"
45+
cardLink="https://join.slack.com/t/kubearmor/shared_invite/zt-2bhlgoxw1-WTLMm_ica8PIhhNBNr2GfA"
4646
cardData="600+ Members"
4747
cardTitle="Slack Channel"
4848
cardIcon={communityLogo2}

src/components/SlackIconButton/index.js

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ export default function SlackIconButton () {
77
return (
88
<Link
99
className={`slack-icon-button ${styles.button}`}
10-
to="https://join.slack.com/t/kubearmor/shared_invite/zt-1ltmqdbc6-rSHw~LM6MesZZasmP2hAcA/"
10+
to="https://join.slack.com/t/kubearmor/shared_invite/zt-2bhlgoxw1-WTLMm_ica8PIhhNBNr2GfA"
1111
>
1212
<FaSlack color="var(--color-white)" />
1313
Join Slack

0 commit comments

Comments
 (0)