Brig — audit report

source: brig demo session · 11 record(s)

#time (UTC)tooldecisionoutcomereasonhash
12026-06-18 12:08:15Zread_fileallowexecuted2d086fa365ae…
22026-06-18 12:08:15Zwrite_fileallowexecuted7c38f0eeba35…
32026-06-18 12:08:15Zwrite_fileallowcontainedd4e09c914e22…
42026-06-18 12:08:15Zhttp_fetchallowexecutedd6c623d9c61d…
52026-06-18 12:08:15Zhttp_fetchallowcontained6306be16e746…
62026-06-18 12:08:15Zread_fileallowexecuted419b38800234…
72026-06-18 12:08:15Zhttp_fetchallowcontainedtaint_block:exfilc1802d8c0531…
82026-06-18 12:08:15Zrun_codeallowexecuted189d721b0600…
92026-06-18 12:08:15Zrun_codeallowcontained8d82478b37e9…
102026-06-18 12:08:15Zrun_commandallowexecutedapproved_by:preapproveda3cda9ca2355…
112026-06-18 12:08:15Zrun_commandallowcontainedapproval_denied:preapproved6f5e7f66cbcb…

Each record's hash is SHA-256 over its contents and the previous record's hash, forming a chain: altering or removing any record breaks every later hash, which brig verify detects. This file is a static, self-contained snapshot — re-run brig verify against the database to check the live chain.