How to build CrowdStrike dashboards in Metabase

CrowdStrike is an endpoint security platform whose Falcon sensor detects, investigates, and responds to threats across endpoints, identities, and cloud workloads. Metabase is where you turn those security signals into shared, trustworthy dashboards. This guide covers two complementary paths: a lightweight MCP + CLI route that pulls live data with the Falcon MCP Server and loads a CSV into Metabase with the Metabase CLI, and a durable pipeline route that syncs CrowdStrike findings into a database so you can build dashboards anyone can read.

How do you connect CrowdStrike to Metabase?

Most teams combine both routes: use MCP and CLI uploads for a fast first pass, then move recurring security reporting to a warehouse-backed model.

What can you analyze from CrowdStrike data in Metabase?

• Detection volume by severity and tactic — built from detections (alerts) and the related incidents, hosts and sensors, Spotlight vulnerabilities data your sync exposes.
• Median time to triage — built from detections (alerts) and the related incidents, hosts and sensors, Spotlight vulnerabilities data your sync exposes.
• Sensor coverage and health — built from detections (alerts) and the related incidents, hosts and sensors, Spotlight vulnerabilities data your sync exposes.
• Incident trends — built from detections (alerts) and the related incidents, hosts and sensors, Spotlight vulnerabilities data your sync exposes.
• Spotlight vulnerability exposure — built from detections (alerts) and the related incidents, hosts and sensors, Spotlight vulnerabilities data your sync exposes.

Which CrowdStrike dashboards should you build in Metabase?

How do you use the Falcon MCP Server with the Metabase CLI?

Pair the Falcon MCP Server with the Metabase CLI for fast, hands-on analysis. MCP is useful for scoped lookups and summarized exports; the Metabase CLI's upload command loads CSV data into Metabase and creates a ready-to-query table and model.

Example workflow

• Ask the MCP server for recent detections (alerts) with severity, status, and detection timestamps.
• Export the result as CSV, keeping stable IDs, severities, statuses, owners, and timestamps.
• Run mb upload csv to load it into Metabase as a table and model, then build questions and dashboards on top.

Be honest about the limits

• MCP lookups are excellent for exploration, not scheduled reporting.
• A CSV upload is a snapshot; refresh it with mb upload replace or move to the pipeline for real history.
• Detection and triage timestamps are required for MTTD and time-to-triage; a single export can't show trend lines.
• mb upload csv needs an uploads database configured under Admin → Settings → Uploads.

How do you set up CrowdStrike MCP and the Metabase CLI?

{
  "mcpServers": {
    "falcon": {
      "command": "falcon-mcp",
      "env": {
        "FALCON_CLIENT_ID": "your-client-id",
        "FALCON_CLIENT_SECRET": "your-client-secret",
        "FALCON_BASE_URL": "https://api.crowdstrike.com"
      }
    }
  }
}

Install with pip install falcon-mcp, or run the container image from quay.io. Public preview — CrowdStrike maintains the repo but labels it pre-GA. Create a dedicated API client with read-only scopes for the modules you need.

# Install the Metabase CLI
npm install -g @metabase/cli

# Log in (opens your browser; requires Metabase v62+)
mb auth login --url https://your-metabase.example.com

# Load a detections-(alerts) export — creates a table AND a model
mb upload csv --file crowdstrike-detections-(alerts).csv --collection root

# Refresh that same table later from a new export
mb upload replace <table-id> --file crowdstrike-detections-(alerts).csv

Can you generate a CrowdStrike dashboard with AI?

Yes. Use the prompt below with any assistant that can run the Falcon MCP Server and the Metabase CLI. It works end to end: if CrowdStrike tables already exist in Metabase it analyzes those; otherwise it pulls scoped, summarized data over MCP, loads it with mb upload csv, then builds the dashboard and caveats any metric that needs missing history.

Create a polished Metabase dashboard for CrowdStrike detection & response analytics.
Work end to end: get the data into Metabase if it isn't there yet, then build.

Goal: Help security and engineering leaders understand detection volume, triage speed, sensor coverage, and response trends from CrowdStrike data.

Step 1 — Find or load the data:
- First, check what already exists in Metabase (search for crowdstrike tables and
  models). If durable CrowdStrike data is already present — synced from a warehouse
  or uploaded earlier — use it and skip to Step 2.
- If nothing is there, pull a scoped, summarized export with the Falcon MCP Server:
  detections (alerts), plus incidents, hosts and sensors, Spotlight vulnerabilities.
  Prefer aggregated or entity-grain views over raw events. Write each result to a
  CSV, then load it with the Metabase CLI — run "mb upload csv --file <export>.csv"
  so each upload creates a table and a ready-to-query model. Use "mb upload replace
  <table-id> --file <export>.csv" to refresh an existing table instead of creating
  duplicates.

Step 2 — Inspect before querying:
Do not assume exact table or column names. Inspect available fields, severities,
statuses, timestamps, and whether snapshots or history exist before creating
duration or trend cards.

Important:
- Build on whatever data is present; don't claim Metabase connects natively to
  CrowdStrike — it reads a database or CLI-uploaded tables.
- Never try to load raw security telemetry or event firehoses into Metabase; use
  findings, detections, entities, and daily rollups.
- Only compute durations (time to remediate, time to triage, time to detect)
  when the required timestamps exist.
- Exclude test environments and suppressed or accepted-risk items from headline
  cards, and keep them visible in a labeled register instead.
- A single CSV is a point-in-time snapshot: only build trend cards if there is a
  usable date column or multiple periods have been uploaded.

Dashboard title: CrowdStrike Detection & Response Overview

Sections:
1. Executive summary: Detections last 30 days; Open now; Median time to triage;
   False-positive rate; Sensor coverage.
2. Volume: Detections by week, severity, and tactic; repeat-offender hosts.
3. Triage: Untriaged by age; time-to-triage trend; auto-resolved share.
4. Coverage: Sensors vs. inventory; outdated or offline agents.
5. Response: Median time to detect; time to contain; incidents opened.

Filters: Date range, Severity, Status, Team or owner, Environment or asset group.

Output: Build the dashboard if you have permission; otherwise provide the exact
questions, SQL, model definitions, and layout. Include caveats for any metric
that cannot be calculated from the available data.

How do you sync CrowdStrike data into a database or warehouse?

For dashboards that need history and reliability, land CrowdStrike findings and metadata in a database first, then connect Metabase to that database.

Connector options

• Managed ETL — use a connector when one covers the objects you need.
• Custom pipeline — use the CrowdStrike Falcon APIs for control over fields, snapshot cadence, and refresh schedule.
• MCP + CSV — use this for quick exploration and one-off slices.

No managed ELT connector exists. Falcon Data Replicator (an add-on SKU) streams raw sensor telemetry to S3 — that firehose belongs in a security data lake, not a BI warehouse. For Metabase, land detections, incidents, and host inventory at alert grain via the Falcon APIs.

Notes

• Decide the snapshot cadence first (daily is the norm for security data) — posture trends only exist if you build the history.
• Land raw entity tables first, then build clean Metabase models on top.
• Normalize host, severity, tactic, status, detected-at, and triaged-at fields.

How should you model CrowdStrike data in Metabase?

Core tables

Modeling advice

• Build a clean detections model with common columns across tools, so multi-source dashboards don't fork definitions.
• Separate entity tables (assets, users, controls) from findings, events, and daily snapshot tables.
• Exclude test environments and suppressed or accepted-risk items from headline metrics; keep them in a labeled register instead.
• Use stable IDs for asset, user, and finding joins; display names change.

Which CrowdStrike metrics should you track in Metabase?

What SQL powers CrowdStrike dashboards in Metabase?

These assume a cleaned analytical model in a warehouse (PostgreSQL dialect). Adjust table and column names to match your pipeline.

SELECT
  date_trunc('week', detected_at) AS week,
  severity,
  COUNT(*) AS detections,
  percentile_cont(0.5) WITHIN GROUP (
    ORDER BY EXTRACT(EPOCH FROM (triaged_at - detected_at)) / 3600
  ) FILTER (WHERE triaged_at IS NOT NULL) AS median_triage_hours
FROM detections
GROUP BY 1, 2
ORDER BY 1, 2;

SELECT
  date_trunc('month', detected_at) AS month,
  percentile_cont(0.5) WITHIN GROUP (
    ORDER BY EXTRACT(EPOCH FROM (detected_at - first_activity_at)) / 3600
  ) AS median_detect_hours,
  percentile_cont(0.9) WITHIN GROUP (
    ORDER BY EXTRACT(EPOCH FROM (detected_at - first_activity_at)) / 3600
  ) AS p90_detect_hours
FROM detections
WHERE first_activity_at IS NOT NULL
GROUP BY 1
ORDER BY 1;

SELECT
  a.platform,
  COUNT(*) AS inventory_assets,
  COUNT(s.asset_id) AS assets_with_sensor,
  ROUND(
    100.0 * COUNT(s.asset_id) / NULLIF(COUNT(*), 0), 1
  ) AS coverage_pct
FROM assets a
LEFT JOIN sensor_inventory s
  ON s.asset_id = a.id
  AND s.last_seen_at >= CURRENT_DATE - INTERVAL '7 days'
GROUP BY a.platform
ORDER BY coverage_pct ASC;

What are common mistakes when analyzing CrowdStrike in Metabase?

Related

Related analytics

Related dashboards

Related integrations

FAQ