> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oasm.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard

> Get an at-a-glance view of your attack surface - key metrics, vulnerability trends, and operational signals in one place

The Dashboard is the landing page you see after signing in to the OASM console. It aggregates live data from your workspace's discovery and scanning pipelines into a single operational view: inventory counts, vulnerability posture, TLS certificate health, asset growth trends, and geographic exposure.

The dashboard is read-only and always reflects the latest state of your workspace. The numbers you see update as new discovery and scan results are added, which makes the dashboard a reliable starting point for daily security reviews.

<Info>
  The console runs locally in development and, when deployed, at your installation's web address (see the Deployment guide). The Dashboard is the first page you see after signing in.
</Info>

## Key concepts

### Widgets as live queries

Each dashboard widget is computed from the current workspace data. Nothing on the page is hard-coded — widget values are recalculated from the latest scan results.

### Data flow

Dashboard data follows a fixed pipeline:

1. **Discovery jobs** run against your targets and groups.
2. New findings are added to your inventory automatically (hosts, ports, services, technologies, TLS certificates, and geographic information).
3. The aggregated metrics that the dashboard widgets show are computed from that inventory.

This means dashboard freshness is tied to discovery cadence: new assets and certificates appear only after the corresponding job results have been added. See [Jobs](/jobs) for how jobs are scheduled.

<Accordion title="Why does the dashboard look stale?">
  If widget values have not changed for a long time, the pipeline is probably not producing new data: discovery jobs may be paused, failing, or not scheduled. Check the **Jobs Registry** first — the dashboard can only display what has been added to the inventory. If jobs are healthy but the numbers are still flat, your coverage is simply stable.
</Accordion>

### Console navigation

The dashboard sits at the top of the console sidebar, which organizes the platform into groups:

| Sidebar group      | Items                                                                                      |
| ------------------ | ------------------------------------------------------------------------------------------ |
| **Overview**       | [Dashboard](/dashboard), [New Chat](/chat-agent)                                           |
| **Admin**          | [Users](/users-and-role)                                                                   |
| **Attack surface** | [Targets](/target), [Groups](/group), [Assets](/asset)                                     |
| **Security**       | [Vulnerabilities](/vulnerability), [Reports](/reports)                                     |
| **Management**     | [Tools](/tools), [Workers](/worker), [Jobs Registry](/jobs), [Integrations](/integrations) |

From the dashboard you can reach any of these modules in one click, which makes it a natural hub for daily operations.

### Workspace scope

The dashboard shows data for the workspace you are currently switched into. Use the workspace switcher to review another tenant's attack surface — targets, assets, and statistics are isolated per workspace.

## Stat cards

Four stat cards at the top of the page summarize the size of your inventory:

| Card             | Meaning                                       | Example value |
| ---------------- | --------------------------------------------- | ------------- |
| **Targets**      | Number of configured targets in the workspace | 6             |
| **Assets**       | Total discovered assets across all targets    | 36            |
| **Services**     | Detected services (host + port combinations)  | 76            |
| **Technologies** | Unique technologies detected across assets    | 38            |

The cards give you a fast health check: if the **Assets** count is flat while you expect growth, discovery may be stalled; if **Services** outgrows **Assets**, many hosts expose multiple ports.

## Vulnerability overview

The vulnerability card summarizes your current finding posture:

* **Score** — Aggregate risk score (for example, 7.6)
* **Issues** — Number of open issues associated with findings (12)
* **Total** — Total vulnerability count (95), broken down by severity:
  * **Critical** (15)
  * **High** (7)
  * **Medium** (4)
  * **Low** (4)
  * **Info** (22)

The card links to the [Vulnerabilities](/vulnerability) page, where you can triage individual findings. Use the **Score** and **Critical/High** counts as your primary escalation signal — a rising score between reviews warrants immediate investigation.

<Info>
  Severity counts are based on the latest scan results added to the workspace. Findings detected by your scanning tools appear here once the analysis completes.
</Info>

## TLS Statistics

The TLS section groups certificates by expiry status, with one button per bucket:

<Table>
  | Bucket                          | Meaning                                            | Example count |
  | ------------------------------- | -------------------------------------------------- | ------------- |
  | **already expired**             | Certificates past their expiry date                | 5             |
  | **expire in a month**           | Certificates expiring within the next month        | 5             |
  | **expire in 3 months**          | Certificates expiring within the next three months | 5             |
  | **won't expire anytime soon**   | Certificates with healthy remaining validity       | 6             |
  | **new certificates discovered** | Certificates first seen by recent discovery runs   | 8             |
</Table>

Click a bucket to drill into the affected assets.

Operationally, this widget drives **certificate renewal planning**: the **already expired** and **expire in a month** buckets are your renewal backlog, while **new certificates discovered** signals fresh TLS coverage added by recent discovery runs.

<Danger>
  Certificates in **already expired** are serving (or about to serve) invalid TLS to visitors. Treat this bucket as an incident queue — renew or replace these certificates before they impact availability and trust.
</Danger>

## Asset trend chart

The trend chart plots how your attack surface evolves over time. Use the series toggles to show or hide individual lines:

* **Assets**
* **Technologies**
* **Ports**
* **Services**
* **Targets**

Compare **Assets** against **Targets**: if assets grow faster than targets, existing targets are yielding more surface (scope expansion); if both are flat, your coverage is stable. The chart is the best tool on the dashboard for spotting slow drift before it becomes a visibility problem.

## Recent hosts

A list of the most recently discovered hosts. It answers "what changed since my last review" and is a good starting point for investigating unexpected new entries on your attack surface. Pair it with the **Asset trend** chart: new hosts are the leading indicator, sustained growth in the chart is the trailing confirmation.

## Top ports

The most common open ports, ranked by asset count:

| Port | Assets |
| ---- | ------ |
| 80   | 22     |
| 443  | 21     |

Standard HTTP/HTTPS ports dominating the list is expected. Unexpected ports in the top ranks (database, management, or remote-access services) are a strong signal to check exposure policy.

## Technologies

Technologies detected most frequently across your assets, with counts:

| Technology | Assets |
| ---------- | ------ |
| Cloudflare | 42     |
| HSTS       | 25     |

Use this list to understand your dependency profile — for example, which CDN, WAF, or security headers are (or are not) in place — and to spot technologies whose presence you did not expect.

## Issues timeline

A chart showing issues over time. It reveals whether new findings are accelerating or slowing, letting you judge whether recent remediation efforts are effective. A downward trend after a remediation sprint is the clearest evidence the sprint worked.

## Top assets with most vulnerabilities

This widget ranks assets by the number of attached vulnerabilities. It is the highest-signal prioritization view on the dashboard: a small set of assets usually carries a disproportionate share of risk.

Prioritize remediation by working down this list from the top — fixing the riskiest assets first reduces the largest share of your exposure per unit of effort.

## Locations

The locations table shows asset distribution by country, derived from automatic lookup of where your assets are located:

| Country       | Assets |
| ------------- | ------ |
| United States | 23     |
| Singapore     | 2      |

Geographic distribution is an operational signal: assets in unexpected jurisdictions can indicate misconfigured routing, shadow infrastructure, or compliance concerns (for example, data residency requirements). Review the list against your expected footprint.

## Reading the dashboard

Each widget answers a specific operational question. Use this mapping to decide what to look at first:

<Table>
  | Widget                               | Operational question it answers                |
  | ------------------------------------ | ---------------------------------------------- |
  | Stat cards                           | How big is my inventory right now?             |
  | Vulnerability overview               | How bad is my current posture?                 |
  | TLS Statistics                       | What is about to break — or already broken?    |
  | Asset trend chart                    | Is my attack surface growing as expected?      |
  | Recent hosts                         | What changed since my last review?             |
  | Top ports                            | Where is my exposure concentrated?             |
  | Technologies                         | What does my dependency profile look like?     |
  | Issues timeline                      | Are new findings accelerating or slowing?      |
  | Top assets with most vulnerabilities | Where should I remediate first?                |
  | Locations                            | Where is my infrastructure physically located? |
</Table>

Everything available in the console is also available through the API — see the API Reference tab.

## Best practices

* Review the **TLS Statistics** widget weekly and treat **already expired** as an incident queue, not a cleanup item.
* Watch the **Asset trend** chart for scope creep — steady asset growth without a corresponding target change suggests discovery is pulling in surface you did not intend.
* Use **Top assets with most vulnerabilities** as your default prioritization order for remediation sprints.
* Check the **Locations** table against your expected footprint; unexpected countries often reveal misconfiguration or shadow infrastructure.
* Start each day with the stat cards and the **Issues timeline**: they tell you whether inventory, posture, and finding velocity are healthy or drifting.
* When counts look stale, verify that discovery jobs are completing and results are being added — see [Jobs](/jobs) for job health.
* Cross-check the **Recent hosts** list weekly — new hosts appearing regularly is a signal to revisit your target and group definitions.
* Combine **Top ports** and **Technologies** when investigating a suspected breach: anomalous ports and unexpected technologies often surface at the same time.

## Related

<Card icon="shield" title="Vulnerabilities" horizontal href="/vulnerability">
  Triage and manage the findings that feed the vulnerability overview card
</Card>

<Card icon="network" title="Assets" horizontal href="/asset">
  Explore the inventory behind the stat cards and trend charts
</Card>

<Card icon="search" title="Search" horizontal href="/search">
  Find specific assets, targets, and vulnerabilities across the workspace
</Card>

<Card icon="file-text" title="Reports" horizontal href="/reports">
  Export dashboard-level insight into structured reports
</Card>