Skip to content

Commit 227fcad

Browse files
authored
Create SECURITY.md
1 parent e365751 commit 227fcad

File tree

1 file changed

+53
-0
lines changed

1 file changed

+53
-0
lines changed

SECURITY.md

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
# 🛡️ Security Policy
2+
3+
## 🔹 Supported Versions
4+
The following table shows the versions of Kube-NetLag currently receiving **security updates**.
5+
6+
| Version | Supported |
7+
|----------|--------------------|
8+
| `latest` | ✅ Actively supported |
9+
| `0.1.x` | ✅ Security patches only |
10+
| `< 0.1` | ❌ No longer supported |
11+
12+
If you are using an **unsupported version**, we strongly recommend upgrading to the **latest release**.
13+
14+
---
15+
16+
## 🚨 Reporting a Vulnerability
17+
18+
We take security issues **very seriously**. If you discover a vulnerability in **Kube-NetLag**, please follow these steps:
19+
20+
### 📩 **How to Report**
21+
1. **DO NOT** create a public GitHub issue for security vulnerabilities.
22+
2. Instead, **email** us at **[aplazidis@gmail.com](mailto:aplazidis@gmail.com)** with:
23+
- A detailed description of the vulnerability.
24+
- Steps to reproduce the issue.
25+
- Potential impact and severity assessment.
26+
- Any suggested fixes (if available).
27+
28+
### 🔒 **Responsible Disclosure**
29+
- We will **acknowledge your report within 48 hours**.
30+
- A fix will be developed **privately** and released in a security patch.
31+
- You will be **credited** in the release notes (unless you wish to remain anonymous).
32+
- If the issue is **critical**, we may **coordinate disclosure** with the CNCF or Kubernetes security teams.
33+
34+
---
35+
36+
## **Security Best Practices**
37+
To keep your **Kube-NetLag** deployment secure:
38+
- **Use the latest version** (check [releases](https://github.com/AposLaz/kube-netlag/releases)).
39+
- **Follow the principle of least privilege** for Kubernetes RBAC.
40+
- **Monitor Prometheus metrics** for unexpected network behavior.
41+
- **Use TLS encryption** for secure communication (if applicable).
42+
- **Regularly update your Kubernetes cluster**.
43+
44+
---
45+
46+
## 🛠️ **Security Tools**
47+
We encourage users to test Kube-NetLag with **security tools** like:
48+
- [Trivy](https://github.com/aquasecurity/trivy) – Container security scanning.
49+
- [Falco](https://github.com/falcosecurity/falco) – Runtime security monitoring.
50+
51+
---
52+
53+
If you have any **security concerns** or suggestions, feel free to reach out! 🚀

0 commit comments

Comments
 (0)