What left the building, in one list.
Sooner or later somebody asks: a client in a security review, an auditor, your own board, or you at the end of the trial. One row per match — when, what happened, which site, whose browser, which rule — and an answer you can send in a minute.
- time
- 14:22, today
- action
- block
- trigger
- paste
- rule
- [AWS_KEY]
- site
- chat.example.com
- actor
- dana@yourcompany.com
- matchCount
- 1
Send the answer, not a screenshot
Narrow it to a day, an action or a person, and the view you are looking at becomes a link you can forward — they see exactly what you see. Search covers the site, the person, the rule and the file name.
In the format they asked for
CSV or JSON, filtered the way you filtered the screen. The full organization export carries your rules, your whitelist, your admins and your events — which is also how you walk away, if it ever comes to that.
Worth knowing
- A row holds the shape of what happened: the rule, the action, the site, the browser, how many times it matched, how large the file was.
- It never holds the text that matched or the file that was stopped — they never left the device. There is nothing in this log to leak, and nothing to explain to a regulator.
The rest of the console
Stop the next leak before it leaves the browser.
Try it free for 14 days, no card needed. Start with one team and see what Capsulla catches in the first week.