SignTrail
Request Threat Brief

Demo

See SignTrail in Action

A short walkthrough of how SignTrail decides ALLOW / HOLD / REJECT before a signature. Demo video coming soon.

SignTrail Demo v0 — the end-to-end walkthrough (silent screen recording).

End to end, in one run

  1. Signing Request
  2. Runtime Evidence (eBPF)
  3. Policy Decision
  4. Gateway Allow / Block
  5. Audit · Evidence Pack

Four live scenarios

  • Normal request

    ALLOW

    Trusted runtime path and a valid decision — the signer runs, and the result is recorded.

  • Abnormal runtime path

    REJECT

    The request was created on an unverified execution path — blocked before signing.

  • Decision replay

    REJECT

    A previously used decision artifact is reused — replay is detected and blocked.

  • Key verification failure

    REJECT

    Unknown / revoked / expired decision key — fail-closed, the signer never runs.

Every scenario is verified in real time from eBPF runtime evidence, and each allow/block decision is captured as a reproducible Evidence Pack.