Thank you for your interest in the security of the KubeSlice Controller project. We take security seriously, and we appreciate your assistance in identifying and disclosing security vulnerabilities responsibly.

If you discover a security vulnerability in the KubeSlice Controller project, please follow these steps to report it:

1. Privately disclose the vulnerability to the project maintainers. You have two options:

   • Email us at security@kubeslice.io.
   • Create a new security advisory on the Security Advisories page.

2. Provide a detailed description of the vulnerability, including information about the affected versions of the project.

3. We will acknowledge your report within 48 hours, and we will work with you to verify and address the issue promptly.

4. Once the vulnerability is confirmed and mitigated, we will work on releasing a fix. We will credit you for your responsible disclosure if you desire.

To view the latest security advisories for the KubeSlice Controller project, please visit the Security Advisories page.

The KubeSlice Controller project is actively maintained, and we typically provide security updates for the latest release and the previous release. Users are encouraged to keep their installations up to date with the latest releases to ensure they are protected against known vulnerabilities.

While we strive to maintain a secure codebase, users and contributors can help by following these security best practices:

• Regularly Update: Keep your KubeSlice Controller installation and its dependencies up to date to benefit from the latest security fixes.

• Implement Access Controls: Limit access to the controller and its resources only to authorized personnel and entities. Employ Kubernetes RBAC (Role-Based Access Control) and other access control mechanisms.

• Scan for Vulnerabilities: Use security scanning tools to regularly scan your Kubernetes clusters and the controller for potential vulnerabilities.

• Audit Logs: Enable and regularly review logs for the controller and your Kubernetes environment to identify any suspicious activities.

• Third-party Dependencies: Be cautious when using third-party libraries or tools in your deployment and keep them updated as well.

• Educate Team Members: Ensure that your team is educated about security best practices and follows them when working with KubeSlice Controller.

We would like to thank the security researchers and contributors who have helped improve the security of the KubeSlice Controller project by responsibly disclosing security vulnerabilities.

If you have any questions or concerns regarding this security policy or the security of the KubeSlice Controller project, please contact us at security@kubeslice.io.

This security policy is subject to change as the project evolves. Please check back regularly for updates and revisions.