Executive Dashboard

Purpose

The Executive Dashboard is a stakeholder-friendly summary of the scan, focused on KPIs and high-signal charts to guide prioritization discussions (without the depth of the technical Action Plan).

Output

• Per scan: output/<scan_name>/executive.html

• Entry point (recommended): output/<scan_name>/index.html (landing page links to all reports)

How to generate

CLI

miyabi-qualys-ai-triage-pack run --config config/config.yaml

Automatic mode (repo root)

Configuration

Enable/disable:

• reports.executive.enabled: true|false

Branding (logo in header):

• rendering.branding.enabled

• rendering.branding.logo_filename

• rendering.branding.logo_alt

Data sources (Qualys CSV fields)

This dashboard is derived from the same ingested dataset as the technical report, using:

• Scan metadata (when present in pre-header lines): Scan Title, Launch Date, Option Profile, Active Hosts, Total Hosts

• Row-level findings: QID, Title, Severity, Category

• Asset identifiers (best-effort): IP, DNS, NetBIOS, FQDN

What you should use it for

• “How big is this?” (coverage, totals, unique vulns)

• “What is the posture?” (severity distribution by rows)

• “What is systemic?” (top vulnerabilities by affected hosts)

• “Where is it concentrated?” (most affected assets, best-effort)

Limitations

• It is a summary view. Use action_plan.html for evidence, remediation steps, and technical details per selected finding.

• Coverage metrics depend on scan metadata being present; if metadata is missing, the dashboard falls back to what can be inferred from findings.