Dashboard¶

The Dashboard is the first page operators see after logging in. It provides a real-time operational summary of the C2 infrastructure -- active beacons, running listeners, sessions, campaigns -- alongside charts and an activity feed that aggregate data from multiple sources.

Overview¶

The dashboard is composed of four sections:

1. Stat cards -- animated counters showing active beacons, running listeners, sessions, and campaigns
2. Charts row -- beacon status distribution (donut), OS distribution (donut), and a 24-hour check-in timeline (area chart)
3. Activity feed -- a unified timeline merging beacon check-ins, listener state changes, and campaign updates
4. Quick actions -- shortcut buttons for common operator tasks

graph TB
    subgraph Dashboard
        A[Stat Cards Row]
        B[Charts Row]
        C[Activity Feed]
        D[Quick Actions]
    end

    subgraph "Data Sources"
        E[Beacons API]
        F[Listeners API]
        G[Sessions API]
        H[Campaigns API]
        I[Stats API]
    end

    E --> A
    E --> B
    E --> C
    F --> A
    F --> C
    G --> A
    H --> A
    H --> C
    I --> A

Stat Cards¶

The top row displays four animated stat cards with live counters. Each card links to its respective management page.

Cards use staggered entrance animations on page load and animated number transitions when values change. A card turns green when its primary metric is non-zero (e.g., at least one active beacon or running listener).

Charts¶

The charts row displays three visualizations side by side, each with a freshness indicator showing when the underlying data was last refreshed.

Beacon Status Distribution¶

A donut chart showing the count of beacons in each status category:

The center of the donut displays the total beacon count. When no beacons exist, a placeholder message is shown instead.

OS Distribution¶

A donut chart breaking down beacons by operating system. OS names are normalized for clarity:

• windows (amd64) becomes Windows
• OS strings containing server become Windows Server
• linux variants become Linux
• darwin / macos variants become macOS

When only a single OS is present, the chart displays a large numeric count instead of a donut.

Check-in Timeline (24h)¶

An area chart showing beacon check-in activity over the last 24 hours, bucketed by hour. The chart includes:

• Hourly check-in counts along the Y axis
• Hour labels (HH:00) along the X axis
• A gradient fill under the area line
• A peak count summary below the chart

Activity Feed¶

The activity feed merges events from three sources into a single reverse-chronological timeline (newest first), displaying the 30 most recent events.

Each event shows:

• A color-coded status dot (green for active/running, yellow for dormant/paused, red for dead/error, gray for stopped/archived)
• An icon indicating the event type (signal for beacons, radio for listeners, target for campaigns)
• A relative timestamp (e.g., "3 minutes ago")
• A status badge

Freshness Indicator¶

Both the charts and the activity feed display a freshness indicator showing when the underlying data was last fetched. This helps operators distinguish between stale data and a genuinely quiet engagement.

Quick Actions¶

The quick actions panel on the right side of the dashboard provides one-click navigation to common tasks:

Stats API¶

The dashboard stat cards are powered by a consolidated stats endpoint that returns all sidebar badge counts in a single response. This avoids N+1 API calls when rendering the sidebar and dashboard simultaneously.

curl -s https://stentor.app/api/v1/stats/counts \
  -H "Authorization: Bearer $TOKEN" | jq

{
  "active_beacons": 3,
  "running_listeners": 2,
  "targets": 47,
  "services": 156,
  "credentials": 12,
  "downloads": 8,
  "keystrokes": 3,
  "screenshots": 5
}

Response fields:

Data Refresh¶

Dashboard data refreshes automatically through React Query's polling mechanism:

Beacon data refreshes most frequently (every 10 seconds) because check-in recency is critical for operational awareness. Other data sources refresh on window focus or navigation, which is sufficient for less volatile data.

Next Steps¶

• UI Walkthrough -- learn how to navigate the full operator interface
• Core Concepts -- understand beacons, listeners, and the C2 lifecycle