# Dashboards

## What these dashboards are for

The dashboards complement the technical deliverable (`action_plan.html`) by providing:

* **Executive visibility** (KPIs and posture summaries)
* **Risk and governance views** (risk register, tiers, treatment guidance)
* **Exposure lenses** (attack surface, TLS/ports, hotspots)
* **Modernization drivers** (lifecycle / obsolescence)
* **Compliance lenses** (PCI and framework crosswalk suggestions)
* **Time series tracking** (historical trends across scans)
* **Scenario-based narratives** (probable attack paths, MITRE mapping, ransomware susceptibility)

All dashboards are designed to be **offline-friendly** (no CDN required) and to remain **auditable**:

* Deterministic core logic is always preferred for scoring/metrics.
* Optional LLM blocks (when enabled) are constrained (JSON-only guardrails) and must not be interpreted as proof of exploitation, internet exposure, or control presence.

## Dashboards catalog (quick links)

<table data-view="cards"><thead><tr><th>Dashboard</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Executive Dashboard</td><td><a href="/pages/24fda1e97e69ac6643444672a934a04ce85e06c7">/pages/24fda1e97e69ac6643444672a934a04ce85e06c7</a></td></tr><tr><td>Risk Report (GRC-style)</td><td><a href="/pages/33f6803d9e32753ba2f788d8054d9c5bad538f52">/pages/33f6803d9e32753ba2f788d8054d9c5bad538f52</a></td></tr><tr><td>Attack Surface Snapshot</td><td><a href="/pages/d61a2012ada6d0f96414d254217aea8ce65bba86">/pages/d61a2012ada6d0f96414d254217aea8ce65bba86</a></td></tr><tr><td>Lifecycle &#x26; Obsolescence</td><td><a href="/pages/83c2ed451b3d516e96c06bcf5bf880ff1631f364">/pages/83c2ed451b3d516e96c06bcf5bf880ff1631f364</a></td></tr><tr><td>Compliance / Control Mapping</td><td><a href="/pages/c26a297ddbe82e21ef4e35ab8d6be1dfe7d39dc9">/pages/c26a297ddbe82e21ef4e35ab8d6be1dfe7d39dc9</a></td></tr><tr><td>Trend Dashboard</td><td><a href="/pages/d08a75ef9d229b4ef4b8f5652a8da66a44146819">/pages/d08a75ef9d229b4ef4b8f5652a8da66a44146819</a></td></tr><tr><td>Probable Attack Paths</td><td><a href="/pages/1a491434ead1c18e8f0904f22e68158f316bd56b">/pages/1a491434ead1c18e8f0904f22e68158f316bd56b</a></td></tr><tr><td>Vulnerabilities × MITRE ATT&#x26;CK</td><td><a href="/pages/23e1d4021a576fc46bf8fdea23b628c8ef6d1b26">/pages/23e1d4021a576fc46bf8fdea23b628c8ef6d1b26</a></td></tr><tr><td>Ransomware Assessment &#x26; “Probability”</td><td><a href="/pages/e7fc3b4b5b042f7b90a0310fb46957ec0067d0b9">/pages/e7fc3b4b5b042f7b90a0310fb46957ec0067d0b9</a></td></tr></tbody></table>


---

# 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://miyabi-threatworks.gitbook.io/miyabi-threatworks-docs/qualys-ai-triage-pack/user-guide/dashboards.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.