Audit & Boost your Kubernetes

Are you:

  • transforming your K8s clusters into a microservice platforms to deliver your digital solutions to business faster?
  • in need of expertise and specialists to maintain or develop your K8s clusters & DevOps processes?
  • aiming to make your K8s clusters more reliable, auditable, secure and easier to maintain?
  • deploying DevOps toolkit and automation processes on your K8s clusters and looking for an experienced partner to help you in the process?

Want to learn more?

Why should you do an audit?

  • Detection of misconfigurations
  • Identification of vulnerabilities in the cluster, container
    images and components
  • Verification of compliance with best practices
  • Reducing the risk of attacks by detecting weak points
  • Early detection of errors reduces the risk of failures and costly
    downtime
  • Verification of the resilience to failures of cluster components
  • Ensuring continuity of operation for applications running in
    the cluster
  • Identification of areas and processes that require
    improvement
  • Development of a plan to increase the technological and
    process maturity of the cluster
  • Implementation of the planned improvements and
    verification of the results

The core part of the process consists in testing compliance with the 145 best practices and patterns and assigning the result of the test.

A practice may be:

FULLFILLED – Test passed. No actions required.

PARTIALLY FULFILLED – The practice test showed that it is not fully fulfilled. An explanation is provided in the comments. Additional information regarding the recommended actions is described in the area summary.

NOT FULFILLED – Immediate corrective actions are required.

After the audit, the client receives a document presenting the analysis of the cluster configuration in 9 areas:

  • Cluster architecture and configuration
  • Access management (RBAC)
  • Container security
  • Network and communication
  • Resource management and performance
  • Storage and data
  • Management and monitoring
  • Backup & Disaster Recovery
  • Compliance and conformity (CIS Benchmark, NSA/CISA, MITRE)

In the final summary, a roadmap of developmental and corrective changes to be implemented on the cluster is proposed, based on the results of the analysis carried out. Each change is assigned one of the following priorities (taking into account the potential risk it eliminates)

Priority Risk Description
CRITICAL Immediate threat to security or availability Requires immediate action. Leaving the issue unresolved risks a security breach, data loss, or an interruption to critical services.
HIGH Significant security or compliance gaps Indicates significant deficiencies that should be planned and addressed within a 1–4 week timeframe. Delay increases the risk of incident escalation and loss of compliance with regulatory requirements.
MEDIUM Moderate risk, requires planning The area requires improvement, but does not pose a direct threat. Implementation should be planned within the next 1–3 months as part of the regular development cycle.
LOW Optimization and best practices Recommendations regarding optimization, automation, or alignment with best practices. Implementation can be planned over a longer time horizon (3–6 months).

Get your offering today!

Selected Sorigo Kubernetes projects

sas_viya

Kubernetes clusters for AI platform

Deployment of Kubernetes platform for SAS Viya analytics and artificial intelligence platform....
Suse_Rancher

SUSE Rancher deployment in finance

Sorigo deployed SUSE Rancher K8S cluster management solution....

Geo redundant Kubernetes platform

Architecture design and deployment of high-available Kubernetes clusters enterprise sales system....

Interested? Book a meeting!

kacper-profile

Kacper Wasiak

Sales Director – International