Opsidian

Workflows

Response, investigations, and exposure in one operating loop.

Opsidian keeps incidents, entities, sources, tasks, signals, and risk context moving between teams without rebuilding the file at every handoff.

Workflows

Three operating workflows. One live risk picture.

Response, investigations, and exposure assessment each stand on their own. Together, they keep evidence, ownership, signals, and risk decisions in sync.

Workflow 01

Incident response

Queue
Opsidian incident response queue view showing severity, location, owner, and action

Declare incidents, triage severity and ownership, escalate actions, and launch investigations directly from the incident workspace.

DeclarationTriageEscalationInvestigation launchRisk profile

Workflow 02

Case intelligence & investigations

Network
Opsidian case network showing entities, relationships, and source packs

Investigate people, organizations, and attributes through your methodology while analysts follow one repeatable workflow.

CookbookCross-matchSource provenanceEvidenceFindings

Workflow 03

Exposure assessment

Footprint
Opsidian operating footprint inventory with sites, routes, third parties, and exposure

Maintain the footprint, activate scenarios, monitor operating signals, score exposure, and track mitigations from the same workspace.

FootprintThreat scenariosSignalsResidual riskMitigations

How it works together

No handoffs. The context moves.

A reported event can trigger casework. Case findings update exposure. Monitoring and risk profile views tell teams what to prioritize next.

1

Report

The event is logged, classified, and assigned.

2

Investigate

The case carries the entities, sources, tasks, and findings.

3

Assess

Exposure updates by site, route, third party, asset, or country.

4

Decision

Teams act from the same evidence, not a recap deck.

Opsidian

Move from alert to action with confidence.

Replace fragmented notes, static trackers, and disconnected evidence folders with one governed operating system.

Login