Platform

Everything you need to make a decision.

ShadowThreat brings together security alerts, affected systems, evidence and actions. For every case, it shows what happened, who needs to act and which organization or environment it belongs to.

Cases requiring review in ShadowThreat, prioritized by risk and linked to supporting evidence
Cases prioritized by risk, with supporting evidence and affected systems.

Operational capabilities

The right information, when it is needed.

Every screen clearly shows which customer or environment the data belongs to. Available views and features vary according to the user’s role and selected configuration.

01

Operational overview

Open alerts, active incidents, monitored systems and integrations available for the selected customer or environment.

02

Security alerts

Search, priority, status and source help the team quickly identify alerts that require attention.

03

Cases requiring review

Findings—cases requiring further review—bring together evidence, affected systems, risk and the assessment’s confidence level.

04

Incidents

A reviewed case can become an incident with evidence, owners and required actions kept together.

05

Systems and assets

Inventory, vulnerabilities and system information. A tenant is the separate environment assigned to the selected customer or business unit.

06

Detection rules

Rules, thresholds and threat indicators are prepared, approved and released through a controlled process.

07

Threat intelligence

Indicators, sources and supporting information help analysts validate a signal and look for related suspicious activity.

08

Log search

Technical log searches remain limited to the selected customer or environment, preventing data from different organizations from being mixed.

ShadowThreat operational overview for the selected customer or environment
Overview of key operational indicators for the selected customer or environment. Sample SLA values.

Operational overview

Context first, numbers second.

The overview brings together the indicators that guide the team’s work. The operational scope—the selected customer, public body or environment—gives each figure meaning and leads the analyst to the relevant details.

  • Open alerts and active incidents in the selected context
  • Monitored systems and integrations available in the selected context
  • Access queued work without switching organization or environment

How context is built

Each piece of information makes the case clearer.

From the selected environment to the operational decision, each step adds information while keeping data and ownership clear.

01

Operational scope

The selected partner, customer and environment always show which data and systems the analyst is working with.

02

Signal

Source, priority, status and event sequence describe where the analysis begins.

03

Context

Systems, vulnerabilities, threat indicators and evidence help explain what was observed.

04

Decision

The case, incident and assigned actions preserve every step from review to response.

From volume to priority

Alerts become a clear workflow.

Search and filters help identify the most important signals. From each alert, the analyst can review details, the event sequence, affected systems and available actions while keeping the relevant customer or environment visible.

  • Priority, status, source and technology that generated the signal
  • Event sequence, observed systems and inventory information
  • Open an incident with the supporting evidence already linked
Incoming security alerts in ShadowThreat
Security alerts with filters, priorities and available actions.

Detection and threat intelligence

From detection rule to validated signal, with clear control points.

Technical capabilities connect detection rules, indicators of compromise (IOCs), keywords and threat sources to the review process. Statuses and approvals make the path clear before release.

01

Sigma rules

Sigma-format detection rules managed according to the environment’s configuration.

02

Threshold rules

Threshold-based conditions for use cases supported within the scope.

03

Indicators and keywords

Indicators of compromise and operational terms organized by status and context.

04

Approval and release

Control steps before availability in the intended environment.

Actual availability of rules, integrations and workflows depends on the selected environment’s configuration and release plan.

FAQ

Where do I find what I need?

At the start of my shift, where can I see what’s still open?

Open the overview and check which environment is selected. You’ll see open alerts and ongoing incidents. To see what’s behind a count, go to the corresponding list and open the item you want to look at.

I have a server name. Where can I check which vulnerabilities affect it?

Start with the inventory for the server’s environment. On the asset, you can see the details available, such as its operating system, detected software and vulnerabilities reported by connected sources. If something you expected is missing, check what the source is sending.

We’ve prepared a detection rule. How can I tell if it’s in use yet?

Check the rule’s status in the environment where you want to use it. Preparing, approving and publishing a rule are separate steps. To see whether your team can use it, check that it has been published for that environment.

See ShadowThreat in your environment

See how ShadowThreat fits your environment.

We start with your organization, systems and team responsibilities, then walk through the path from alert to decision together.