Skip to content

bastiontrace 0.6.0: a fuse trip is a landing

Choose a tag to compare

@Rinkia Rinkia released this 08 Oct 09:37
· 2 commits to master since this release

A bastionfuse trip is now a landing.

bastionfuse writes a bastiontrace trace every time a tripwire fires. analyze scored those
files CLEAN unless the tripped tool happened to be a canary tool, because the honeytoken
that caused the trip is redacted out of the snapshot on purpose. The containment leg produced
forensic evidence that the forensics tool called clean. This release closes that.

Read-side only: bastionfuse 0.1.0 already writes everything needed, and bastiontrace was
dropping it.

$ bastiontrace analyze <fuse state dir>/trips/1760000000-ab12cd34ef.jsonl
trace 'fuse-ab12cd34ef-1760000000' (source=bastionfuse)  [LANDED]  (contained: the fuse blocked the call)
  #0   tool_call 'read_document' args={'path': 'notes.md'}
  #1   tool_call 'http_post' args={'body': '[HONEYTOKEN]'}  <== LANDING (fuse)
  landing: #1 - honeytoken #1a2b3c4d in the input of 'http_post'
  note   : landing found but no inject site located; source unknown

What's new

  • New landing kind fuse. With a fuse header block present, the call carrying
    verdict:"tripped" is the landing, and the fuse's own rule and reason are the signal. Its
    recorded decision is read, not re-derived: a tool-name match cannot name which tripwire
    fired, and re-deriving would mean searching for decoy strings and risking echoing live ones
    into a report.
  • Finding.contained. The payload reached a forbidden action and the fuse blocked the
    call. The verdict vocabulary stays LANDED / ATTEMPTED / CLEAN, so anything enforcing on
    it keeps working; the human report adds (contained: the fuse blocked the call) and the JSON
    gains the field.
  • Schema (additive). A fuse header block (rule, reason, session_sha256,
    honeytoken_sha256) and an optional tool_call.verdict (allowed | blocked | tripped).
    Hostile values raise a ValueError naming the field. A trace with neither is read, scored and
    serialized exactly as before.

Known ceilings

  • A snapshot yields a landing but no inject site and no causal path: the forensic ring holds
    tool calls with redacted args, not the content the agent read. Analyze the agent's own trace
    alongside the snapshot to get the path.
  • contained reports what the fuse recorded. bastiontrace does not verify the block
    independently.

Full notes in CHANGELOG.md; the wire format is in SCHEMA.md.

pip install -U bastiontrace