Sales: +91 9600 70 3224
- Support
Inline inspection at the mail-transfer hook, attachments read through, and chat monitored as it happens.
Email is the channel most data leaves through, and a delivered message cannot be recalled in any way that matters. Akku inspects at the mail-transfer hook, while the message is still yours, and decides there: block it, hold it in quarantine, or let it through.
Every outbound message and attachment is inspected in real time, inline at the mail-transfer hook, then blocked, quarantined or allowed before delivery according to your policy. And if the inspection service is unavailable, mail flows rather than queuing behind it, so a data control does not become a mail outage.
Attachments are opened and read rather than judged by file type or name, with text inside images extracted by OCR, which covers the screenshot of a contract as well as the contract. The same detection engine runs here as everywhere else, so the customer records you have indexed are recognised in an attachment exactly as they are on a laptop. There is no separate policy to write for email and no separate set of things it can find.
Slack, Google Chat and Microsoft Teams messages and shared files are monitored. Detection is event-driven through webhooks, so an incident is raised as the message happens rather than waiting for a scheduled scan to come round. This is monitoring rather than inline blocking: the message is detected and raised, not held before it appears. For history rather than live traffic, a scheduled batch import through Google Vault brings Chat and Teams archives in to be scanned.
Run a policy in audit-only mode and it inspects real outbound traffic, records what it would have blocked, and holds nothing. That gives you the false-positive rate on your own mail rather than a vendor's estimate of it, and it is the difference between a policy you switch on and a policy you switch on twice. When the numbers look right, move it to enforce.
