Skip to content
shadowiq
Use case · Incident response

Forensic replay in minutes. Not weeks.

Every AI decision already lives in a signed ledger. Pulling the timeline of an incident becomes a query — not a manual archaeology project.

What this is

Summary

ShadowIQ AI incident response reconstructs signed, timestamped forensic timelines of AI incidents in minutes from the cryptographic evidence ledger, with OCSF event export to SIEM and chain-of-custody preservation acceptable to regulators.

How it fits · explainer

The before / after, in one picture.

PROBLEM · BEFORE SHADOWIQ
Stitching AI incident timelines from logs that don't agree.
siqSOLUTION · WITH SHADOWIQ
siq timeline --user alex --from '2026-03-10T14:00Z' returns a signed, ordered list of every AI decision, every policy hit, every model call.
PILLARS ENGAGEDEvidence
Where it hurts

You've heard this one before.

  • Stitching AI incident timelines from logs that don't agree.
  • No tamper-evident record to show regulators after an incident.
  • Weeks between detection and a defensible narrative.
  • Chain-of-custody concerns when evidence lives in editable systems.
What we do about it

Three moves.

  1. 1
    Timeline by query.

    siq timeline --user alex --from '2026-03-10T14:00Z' returns a signed, ordered list of every AI decision, every policy hit, every model call.

  2. 2
    Chain-of-custody preserved.

    Evidence is append-only, Merkle-rolled-up, and Sigstore-anchored. A regulator verifying your timeline doesn't need your systems — only your public key.

  3. 3
    SIEM-ready events.

    OCSF event format flows into Splunk, Sentinel, Chronicle, or a custom SIEM. Analysts never leave their queue to close a case.

Outcomes

Numbers, not adjectives.

< 3 min
forensic timeline reconstruction
100%
tamper-evident
OCSF
SIEM-ready events
Frequently asked

Asked, answered, sourced.

Evidence is append-only; every write is Ed25519-signed with a key you control (HSM-backed in Enterprise). Roots anchor externally to Sigstore or your chosen transparency log.

Yes. The verifier CLI (siq verify) confirms inclusion and integrity with the public key alone — no ShadowIQ credentials needed. That independence is usually the feature regulators react to.

Per-tenant signing keys and isolated anchors. Cross-tenant correlation requires explicit authorization; evidence from Tenant A cannot be derived from Tenant B's keys.

Ready to see the signet in motion?

Your 30-minute demo. A signed audit trail by the end of it.

We'll wire ShadowIQ into one live workload, block a prompt injection in real time, and hand you a cryptographic receipt — before the meeting ends.