Skip to content

Using the console

The console at app.sheersight.io is where you see what your dedicated instance has found, connect your tools, and check what has happened in your account. This page walks through every screen, in the order it appears in the left-hand menu.

Signing in and out

Open app.sheersight.io. You sign in through Zero-Trust access, with your organization's Google or Microsoft account or a one-time PIN sent to your work email. Only emails that SheerSight has added to your organization can get in. See Signing in, team and roles for inviting colleagues and choosing their roles.

To sign out, open the account menu (your initials, top right) and choose Log out.

Finding your way around

The left-hand menu has three groups:

Group Pages
Connect Integrate
Monitor Overview, Alerts, Incidents, Triage KPIs
Manage Audit

Your organization's name is shown in the top bar as tenant <name>. Settings lives in the account menu. Knowledge base at the bottom of the menu opens these docs. On a small screen, the menu folds into a Menu button.

Top bar controls

Control What it does
24h / 7d / 30d The time range for charts and counts. Defaults to 7d.
30s Turns on auto-refresh every 30 seconds. Off by default.
refresh Reloads the data now.
Health label connected when the console is reachable, otherwise error, offline or checking…

The time range and auto-refresh reset when you reload the page.

Light and dark mode

Account menu, Appearance, then Light or Dark. Your choice is remembered in this browser. Until you pick one, the console follows your computer's setting.

Overview

Your at-a-glance view.

  • sources up: how many of your sources are reporting, out of the total.
  • open incidents: incidents in the selected time range.
  • alerts: alert count for the selected time range.
  • last seen: when your instance last reported in. never means it has not reported yet.
  • alert volume: a chart of alerts over the time range.
  • incidents by source: which tools the incidents came from.

If nothing is connected yet, start with Integrate.

Alerts

An alert is a single detection from one of your sources.

  • alert volume: alerts over time.
  • disposition breakdown: how alerts were judged: true positive, false positive or benign.
  • top rules and top entities: the detections and the users, hosts or IP addresses that fire most often.
  • recent alerts: the latest 100 alerts with rule, entity, disposition and time. Alerts not yet judged show undisposed.

Click a column heading to sort. Use ‹ › to page through.

Where dispositions come from

When Slack triage is enabled, your SheerSight analysts and trusted channel members classify individual bot alerts with reactions. The console shows the result. In record mode, alerts remain undisposed without that reaction path. You can't change a disposition from the console today. For bot setup and the reaction mapping, see Slack triage.

Incidents

An incident groups related alerts, for example several alerts about the same user within a short window.

  • incident timeline: incidents over time.
  • cross-source ratio: how many incidents span more than one tool (cross-source) versus one tool (single). Cross-source incidents are usually the ones worth looking at first.
  • incidents: the latest 100, with the entity involved, number of alerts, which sources they came from, and time.

Triage KPIs

How well the monitoring is working for you. Each card shows a measure from your instance's triage loop: its current value, the change since the last report, and a small trend line. Examples are alerts surfaced to people, alerts suppressed as known noise, and active suppressions.

A card labelled safety gate tracks real threats that were wrongly suppressed. It should stay at zero. If it ever rises, SheerSight reviews and tightens the suppression rules.

Integrate

Connect the tools you want monitored. Full per-tool steps are in Connecting sources; this section explains the screen.

Status at the top

The how integration works panel shows where your setup is:

Badge Meaning
Awaiting instance Your dedicated instance is still being set up. You can browse sources but not connect yet.
Ready to connect Your instance is online and can receive credentials.
Live At least one source is collecting.

Source cards

Each tool has a card with a status badge:

Badge Meaning
not connected Nothing set up for this source.
activating Credentials received; waiting for the first successful collection.
live Collecting normally.
partial Collecting, but some parts are switched off on the vendor side (for example an AWS service not enabled).
not enabled Connected, but the data it needs is turned off on the vendor side.
stalled Was collecting, but has gone quiet.
error Collection is failing. Open the card to see why.
on your instance A sensor (Suricata, Wazuh) that already runs on your instance. Nothing to connect.
not available yet Not self-serve yet. You can request it.

Connecting a source

  1. Click the source's card.
  2. Follow the steps shown to create a read-only credential in that tool.
  3. Fill in the fields. Secret fields are marked · encrypted.
  4. Press Connect.

Your credential is encrypted in your browser before it is sent. You'll see "Encrypted in your browser and relayed. Activating this source on your instance now." and the badge moves to activating, then live.

AWS works differently: you create a read-only role in your own AWS account with a four-step guide on the card. See AWS.

If you see "credential relayed, but forbidden"

Your credential was encrypted and delivered safely, but the step that starts the source didn't run. This is a known issue we're fixing. You don't need to paste it again: contact support and we'll start the source for you. The same applies if Connect on the AWS card or Disconnect shows forbidden.

When a source shows an error

Open its card. You'll see Problem (what went wrong), Fix (what to change in the vendor), a link to the right documentation page, and an expandable Raw error with secrets removed.

Disconnecting a source

Open the card and press Disconnect & scrub credential. Your instance stops collecting and deletes the stored credential. Disconnecting does not revoke the credential at the vendor, so also delete the token or role there.

Slack triage app

Customer admins see a Slack card with Change connection and Disconnect Slack once the instance is enrolled. Analysts and viewers see status only. Operators have the detailed Slack triage panel. Connection changes use the bot token, app-level token and channel ID, protected by an authenticator check; disconnect needs confirmation and waits for record-mode health. Follow the detailed Slack triage guide for creating the app, enabling it, interpreting its health status, testing reactions and switching back to record mode.

Relayed credentials

This panel lists each credential you've sent, with the time and its status: pending until your instance picks it up, then applied. Credentials are never shown back to you or to us.

Requesting an integration

Don't see your tool, or it says not available yet? Use Request an integration: enter the tool name and, optionally, what you'd like it to watch, then press Send request. SheerSight gets the request straight away.

Audit

A tamper-evident log of everything that happens in your account: credentials relayed and applied, instructions sent to your instance and their results, your instance enrolling, and data arriving. Each entry shows the time, who or what did it (a person's email, console, agent, or operator), the action and its target.

Press verify chain to check the log hasn't been altered. Each entry is linked to the one before it with a cryptographic hash, so changing or removing any entry breaks the chain. You'll see ✓ chain intact or ✗ TAMPERED.

Settings

Open from the account menu.

  • Team: who is in your organization and their roles. Admins invite, change roles and remove people here. See Signing in, team and roles.
  • Profile: the email you're signed in with, your role, and your authenticator app (set up or replace it here).
  • defaults: time range and auto-refresh for this session.
  • notifications: alert routing is set up with SheerSight during onboarding. Per-person notification settings are coming.
  • integration status: whether your instance's signing key is published.

Responding safely

When SheerSight takes an action on your instance, the console sends a signed, allow-listed instruction, never an arbitrary command and never shell access. Every instruction and its result appears in Audit. See Security & trust.