Skip to main content
Threatstealth
Login
// CLIENT.CONSOLE

One console, every signal, your tenant only

Per-organization KPIs, threat queue, incident view, compliance posture, and module access — strictly scoped to your tenant data.

Reviewed by Threatstealth Security Architects·Aligned to SOC 2 · ISO 27001 · NIST CSF · PCI DSS V 4.0.1
// DEFINITION

What is Client Dashboard — Tenant-Scoped Security Console?

The Client Dashboard is the per-tenant view of Threatstealth: every security signal — alerts, incidents, identity hits, KEV exposures, compliance coverage, phishing-resilience, endpoint health — surfaced in one console scoped to a single organization. It's what your team logs into every day.

// THE.PROBLEM

Why security teams need a single pane

  • Operators jump between 6+ tools to triage one incident
  • KPIs that the board cares about live in spreadsheets, not the SIEM
  • Per-tenant dashboards in MSSP setups are usually fragile workarounds
  • Auditors want a clean per-org view; ops want a fleet view — most tools force a choice
// HOW.IT.WORKS

A four-step operational model

1

Sign in

Tenant users see only their organization. Cross-tenant access is reserved for super-admins.

  • Per-org RBAC
  • MFA enforced
  • SSO ready
2

Read the headline

Top of dashboard = TS-RISK INDEX, open criticals, MTTR trend, KEV exposures, compliance coverage.

  • TS-RISK INDEX
  • Open criticals
  • MTTR + coverage
3

Drill into modules

Threats, Incidents, Identity, Compliance, Endpoint, MDM, IAM, Network — each one a click away.

  • 20+ modules
  • Per-org telemetry
  • Audit trail per action
4

Talk to the assistant

The in-app AI assistant explains alerts, MITRE ATT&CK techniques, and recommended next steps — grounded in your tenant data.

  • MITRE-aware
  • Site-aware
  • Streamed responses
20+
Modules in one console
TS-RISK
Composite 0–100 index
Per-org
RBAC + audit
AI
MITRE-aware assistant
// WHY.IT.MATTERS

Outcomes for security teams

One pane, not seven

Every signal lives next to every other signal — incidents are triaged faster because context is one click away.

Per-tenant by design

Data isolation is enforced at the database layer, not at the UI.

Built for daily ops

Designed around the 08:30 → 17:30 super-admin runbook documented in our SOPs.

// FAQ

Direct answers

Is data scoped to the tenant?+

Yes — every query is org-scoped at the database layer; no application-side filter to bypass.

Can clients have read-only users?+

Yes. The viewer / editor / admin roles are configurable per-org.

What does the AI assistant know?+

Site map, MITRE ATT&CK knowledge base (auto-refreshed every 6 h), and — for admins — the full SOP.

How fresh is the dashboard?+

KPIs refresh continuously; the TS-RISK INDEX recalculates as new findings land.

// RELATED.READING

Continue exploring

Closed · Expert Access

Ready to see it in your environment?

Request a private security demo from the Threatstealth team.