# Runtime Dashboard

The Runtime dashboard provides visibility into your [runtime environment](/secure-runtime/ox-runtime-sensor.md), including cluster health, open source risk exposure, and container image usage.

It helps you understand the security posture of your running workloads and which images are high-risk and what their sources are.

<figure><img src="/files/6QgnjqpZy1yapKje8I3L" alt="" width="563"><figcaption></figcaption></figure>

Use this dashboard to:

* Focus on exploitable risks.
* Prioritize high-risk container images for remediation.
* Monitor usage of base and public images across environments.
* Validate that images are sourced from trusted registries.

### Connected Clusters

Displays OX Runtime Sensors on Kubernetes clusters. Clicking **View Health Center** opens the Runtime Sensor Health Center, a dedicated dashboard that provides full visibility into the health and status of all your Runtime Sensors.

<figure><img src="/files/UayX7QCvlyDJB6HJNCU6" alt="" width="563"><figcaption></figcaption></figure>

* **Connected Clusters**: All monitored clusters and their current health status at a glance.
* **Connected Sensors Over Time**: A trend graph showing how many Runtime Sensors have been connected at any given point in time. This view helps you detect unexpected drops, for example, if you normally have 60 Runtime Sensors connected and the count drops to 45, you can identify and investigate the shift immediately.
* **Sensor Health:** The list of all the monitored clusters.

#### Cluster Details

Clicking on a **Cluster Name** within the Health Center opens a detailed view for that specific cluster. The view is divided into two areas, Cluster Info and Nodes.

This per-cluster, per-node breakdown supports a range of use cases, from routine health monitoring to audit and compliance scenarios where you need to demonstrate sensor availability and resource consumption over time.

<figure><img src="/files/rcQw78t2cS23MeI48Tf0" alt="" width="563"><figcaption></figcaption></figure>

**Cluster Info** is a summary of the cluster-level details.

| Field           | Description                                                |
| --------------- | ---------------------------------------------------------- |
| Cluster Name    | The name of the cluster                                    |
| Cloud Type      | The cloud provider the cluster runs on (for example, AWS)  |
| Cloud Account   | The cloud account ID associated with the cluster           |
| Sensor Version  | The version of the Runtime Sensor currently deployed       |
| Cluster Status  | Overall health status of the cluster (Healthy / Unhealthy) |
| Healthy Nodes   | Number of nodes currently in a healthy state               |
| Unhealthy Nodes | Number of nodes currently in an unhealthy state            |

**Nodes** table is a per-node breakdown of all nodes in the cluster.

| Column        | Description                                                         |
| ------------- | ------------------------------------------------------------------- |
| Node Name     | The name of the node                                                |
| Last Activity | When the node last reported activity, including the exact timestamp |
| Sensor Memory | Memory currently consumed by the Runtime Sensor on that node        |
| Sensor CPU    | CPU currently consumed by the Runtime Sensor on that node           |
| Sensor Status | Health status of the sensor on that node (for example, Healthy)     |

## Open Source Issues Funnel

Visualizes how open source risks are distributed and prioritized. This funnel helps you focus on the issues most likely to be exploited in runtime.

| Metric                                 | Description                                                                                  |
| -------------------------------------- | -------------------------------------------------------------------------------------------- |
| All issues                             | Total number of detected open source issues                                                  |
| Packages loaded                        | Issues in packages that are actively used in runtime                                         |
| Known exploit                          | Issues with publicly known exploits                                                          |
| EPSS/AI-simulation prioritized         | Issues with a higher likelihood of exploitation based on scoring and simulation              |
| KEV / malicious dependency prioritized | Issues linked to known exploited vulnerabilities or malicious dependencies loaded in runtime |

## Top Risk Images

Lists container images with the highest risk across your clusters. Use this table to prioritize remediation for the most critical runtime exposures.

| Column      | Description                                                         |
| ----------- | ------------------------------------------------------------------- |
| Image       | Name of the container image                                         |
| Cluster     | Cluster where the image is running                                  |
| Context     | Indicators such as exposure, privilege level, or runtime conditions |
| Image age   | Time since the image was built                                      |
| Application | Associated registry or repository                                   |
| Severity    | Highest detected risk level for the image                           |

## Most Used Base Images

Shows the base images most frequently used across your environment.

* Helps identify standardization patterns
* Highlights widely used images that may introduce systemic risk

Focus on securing commonly used base images to reduce overall exposure.

### Most Used Public Images

Displays the most frequently used public container images.

* Includes images pulled from public registries
* Indicates how widely each image is used

Public images increase supply chain risk, so this view helps identify where to apply stricter controls.

## Image Registry Source

Breaks down image usage by registry source.

* Amazon ECR
* Docker Hub
* Other registries

Use this to understand where your images originate and assess trust levels for each source.


---

# 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.ox.security/get-started/onboarding-to-ox/review-scan-results/runtime-dashboard.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.
