INTEL_REPORT
Trail of Bits — Security engineering · published 3/31/2026, 11:00:00 AM · TLP amber
Summary
Ingested excerpt (first ~500 chars of normalized text).
How we made Trail of Bits AI-native (so far) This post is adapted from a talk I gave at [un]prompted , the AI security practitioner conference. Thanks to Gadi Evron for inviting me to speak. You can watch the recorded presentation below or download the slides . Most companies hand out ChatGPT licenses and wait for the productivity numbers to move. We built a system instead. A year ago, about 5% of Trail of Bits was on board with our AI initiative. The other 95% ranged from p…
https://blog.trailofbits.com/2026/03/31/how-we-made-trail-of-bits-ai-native-so-far
sha256:d53978a24c803a20224be726cac96799d509a22dd80bae01d764dd75915f38f9
What we pulled out
Deterministic extractor (IOC + allowlisted tokens + ATT&CK IDs present in DB).
Indicators
Linked with report → mentions → indicator. Values open the indicator workspace.
Malware families
Allowlist token matches only.
Threat actors mentioned
Allowlist mentions — not a formal attribution verdict.
ATT&CK techniques
MITRE IDs referenced in text and present in local technique table.
CONTINUE INVESTIGATION
High-signal pivots without leaving the thread you started in search.
Browse the report corpus.
Neighborhood from the first linked indicator.