# KuboScore

{% hint style="info" %}
**Looking to get started with KuboScore?**

Head to the [getting started](/getting-started/kuboscore.md) page.
{% endhint %}

<figure><img src="/files/DL6qn3gfrZvpaxpxuy7I" alt=""><figcaption></figcaption></figure>

KuboScore runs multiple scenarios on your clusters to check for potential **misconfigurations and bad practices** that will lead to **security incidents or performance issues**.

These scenarios are based on our extensive consulting experiences and years of practice. We crafted some **real life scenarios** that can be executed on your cluster to audit its **state, health, security level, configuration**, and much more.

It’s **free to use**, [**start analyzing your cluster configuration right away**](https://www.kuboscore.io/)**!**

## Features

### Real-life scenarios

KuboScore will run various scenarios that will check the configuration of:

* general cluster components
* core Kubernetes features for applications
* applications communications and traffic restrictions
* external traffic support
* Kubernetes restrictions mechanisms
* cloud services interconnections
* storage support
* security and compliance with security best practices
* important administrative features
* cluster configuration and availability of important add-ons
* existing workloads’ health and compliance with best practices

It will take about **20 to 30 minutes** to perform a complete analysis.

<figure><img src="/files/ltZAribJkBWCrpjVlt02" alt=""><figcaption><p>Follow an ongoing analysis (cloud mode).</p></figcaption></figure>

### Review the results

At the end of the process, you will be provided with a **global score** and some details regarding the scenarios that passed or failed.

<figure><img src="/files/hIwoon8OQKbsZIwkDOAM" alt=""><figcaption><p>Example of a free KuboScore page results.</p></figcaption></figure>

### Get your report

For more in-depth details about each scenario – like root causes, potential consequences or how to fix – you can purchase a **professional report** as well as an **enterprise grade report** to help you investigate and resolve reported configuration issues.

<figure><img src="/files/KksMPMyz8Bobx079Foju" alt=""><figcaption><p>Excerpt from a professional report.</p></figcaption></figure>

## How does it work?

KuboScore is available in two different modes:

* **cloud** mode
* **local** mode

### Cloud mode

In **cloud mode**, we use the **Kubernetes API** to connect to your cluster and run our scenarios. Your cluster must be **publicly** reachable or behind a [*SSH bastion* to which we can connect](/guides/grant-access-to-a-private-network.md).

<figure><img src="/files/Wm3ns57bSIcwg4iV34Wz" alt=""><figcaption><p>Connect KuboScore to your cluster.</p></figcaption></figure>

### Standalone mode

With KuboScore in **local mode**, you can perform a scoring of **any** cluster, as long as **you** can reach it.

You just need to install [KuboScore CLI](/getting-started/kuboscore/local-mode.md) and run it with [sufficient privileges on your cluster](/getting-started/kuboscore/cloud-mode.md#permissions)!

At the end of the scoring, you will get a **file** containing the **scoring results**. You can import this file in [KuboScore](https://kuboscore.io) to **review your results** and **get your report**.

<figure><img src="/files/jBwMVX68WcuEt9OOhOcr" alt=""><figcaption><p>Follow an ongoing analysis (local mode).</p></figcaption></figure>

***

When the analysis is running, whatever mode you chose, **a bunch of resources will be created** on your cluster in order to **assess its state**. You will be able to **follow the execution** and see the **scenarios outcome**.

**Resources that we create are deleted** at the end of the scenarios, by the end of the analysis your cluster will be left **as if we were never there!**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kubolabs.io/our-products/kuboscore.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.