Security Principles

In a Kubernetes environment, security is paramount. kspacr provides secure multi-tenancy and ensures that namespace isolation is enforced. This means that users within the cluster are not able to break out of their assigned namespaces.

Reporting Issues

If you come across any security-related issues or think you've discovered a weak spot in our system, we encourage you to get in touch with us. You can send us an email at security@kspacr.com.

Please do not hesitate to reach out!

Policy Enforcement

kspacr runs a policy enforcement solution that is continuously monitoring workloads and cross-checking them against our set of policies to make sure that no application having insecure settings gets deployed to the namespaces. When a violation of a policy is found, an explanation of the issue is provided.

The policy evaluation process is entirely local.

Your files and content

Your files and their contents are not sent to our SaaS backend, they reside only in the private container registry and the Kubernetes clusters in the selected region. Policy checks are performed locally (in-cluster). kspacr does not access to your files and their contents.

Network protocols

All communication is done via https, encrypted using SSL with industry best practices in mind.

Vulnerability Remediation

At kspacr, we take the security of our systems and services very seriously. Vulnerability Remediation is the process of identifying, assessing, and addressing vulnerabilities in a system. At kspacr, we are committed to patching or otherwise remedying vulnerabilities within a timeframe that is appropriate for the severity of the vulnerability.

We classify vulnerabilities based on their severity and address them within specific timeframes:

Critical: These are the most severe vulnerabilities that pose an immediate risk to our systems and services. We aim to remediate these within 24 hours.
High: These vulnerabilities are less severe than critical ones but still pose a significant risk. We aim to remediate these within 1 week.
Medium: These vulnerabilities pose a moderate risk and are remediated within 1 month.
Low: These vulnerabilities pose a low risk and are remediated within 3 months.
Informational: These are potential vulnerabilities that do not pose an immediate risk. We remediate these as necessary.