Dashboard
Purpose
The Dashboard is the first place anyone — analyst, manager, or executive — should look. It answers three questions at a glance:
- How exposed are we right now? (current score, open threat count)
- Is it getting better or worse? (trend over time)
- Where should we focus? (category breakdown, recent high-severity activity)
What you see
| Widget | What it tells you | Why it matters |
|---|---|---|
| Brand Protection Score | A composite 0–100 style rating of overall exposure. | Single number for stakeholders; easy to track over time and compare across brands/business units. |
| Score trend chart | Historical score movement (daily/weekly/monthly snapshots). | Shows whether monitoring + takedown effort is actually reducing risk, not just generating activity. |
| Threat volume by category | Counts across Website & Domains, Social Media, Mobile Apps, Dark Web, Scams, Counterfeit, Advertisement, Data Exposure. | Identifies which channel is producing the most abuse so you can prioritize resources or policy changes (e.g., stricter marketplace enforcement). |
| Open vs. resolved counts | How many detections/incidents are New, In Progress, or Closed. | Tracks backlog health — a growing "open" count without matching growth in "resolved" signals a bottleneck. |
| Recent activity feed | Latest detections, status changes, takedown updates. | Lets you spot anything urgent without navigating away. |
| Impact / exposure metrics | Estimated reach of active threats (traffic, followers, downloads) where available. | Helps prioritize by actual harm, not just count — a phishing page with 10,000 hits/day outranks one with none. |
Example: category breakdown
pie showData
title Open Threats by Category (Example)
"Website & Domains" : 34
"Social Media" : 22
"Mobile Apps" : 8
"Dark Web" : 6
"Scams" : 15
"Counterfeit" : 10
"Advertisement" : 3
"Data Exposure" : 2Example: score trend over a quarter
xychart-beta
title "Brand Protection Score — Last 6 Months"
x-axis [Apr, May, Jun, Jul, Aug, Sep]
y-axis "Score (0-100)" 0 --> 100
line [62, 58, 65, 71, 76, 82]A rising score (as configured here, higher = better/less exposed) indicates that new threats are being caught and mitigated faster than new ones appear. If your instance uses "higher = more risk," the interpretation flips — check the legend on your Dashboard.
How the score is calculated
The score is produced by a scheduled scoring pipeline that inspects every open and recently-resolved ticket (detection/incident), weighs it by severity, category, and how long it has been open, and stores a snapshot so trends can be plotted over time.
sequenceDiagram
participant S as Scheduler
participant C as Data Collector
participant T as Tickets (Detections/Incidents)
participant Sc as Scoring Engine
participant D as Dashboard
S->>C: Trigger scoring run (on schedule)
C->>T: Pull open/resolved tickets + severity + age
C->>Sc: Aggregate signals
Sc->>Sc: Compute weighted score
Sc->>D: Store score snapshot (for trend chart)
D-->>D: Render current score + trendFactors that typically move the score:
- Number of open, unresolved threats — more open items generally lowers (worsens) the score.
- Severity mix — a handful of Critical items can outweigh dozens of Low ones.
- Age of open items — threats open far longer than your SLA drag the score down more than fresh ones.
- Resolution velocity — how quickly incidents move from Promoted to Resolved.
- Category weighting — some categories (e.g. active phishing) are weighted more heavily than others (e.g. a stale dark web mention) because they carry more immediate customer risk.
Typical use
- Start your day on the Dashboard to see if anything new or high-severity appeared overnight.
- Use the trend chart in reviews and board reports to demonstrate risk reduction to stakeholders.
- Click into any category widget to jump straight to a filtered view in Detections.
- Watch the open-vs-resolved ratio weekly — a widening gap is an early warning that Intelligence or Mitigation is under-resourced.