Anexet blocks outbound data transfers the moment a rule matches — before the file leaves the endpoint. It covers HTTP uploads, SMTP and MAPI email, FTP, XMPP, USB and removable drives, printers, clipboard, messenger file transfers, and screenshot capture. Blocking Policies are available from the Advanced plan. Anexet is deployed on-premise; the vendor has no access to your data.
Schedule a Demo
Every data leak starts with a transfer — and Blocking Policies stop it mid-flight, before the file reaches its destination.
Every data leak starts with a transfer: an attachment sent to a personal inbox, a file dropped onto a USB drive, a screenshot uploaded to a cloud service. By the time your team notices, the data is already outside the perimeter. Blocking Policies in Anexet stop that transfer mid-flight — the send is cancelled, the event is logged, and the security officer receives an alert.
Unlike monitoring-only tools, Blocking Policies move from visibility to enforcement. You configure a rule — for a protocol, device, or content type — and the endpoint agent enforces it silently in the background. Employees see nothing unusual until a blocked action triggers a notification. The incident record in the Client Console shows exactly who tried to send what, over which channel, and at what time.
Because Anexet runs entirely on-premise, the blocking engine operates inside your network without routing traffic through any external service. The vendor has no visibility into your rules, your data, or your blocked events.
The send is cancelled before the file reaches its destination — not logged after the fact.
HTTP, email, USB, printers, clipboard, messengers, and screenshots are all covered by a single policy engine.
Every blocked event is recorded as an incident; blocked emails enter Mail Quarantine for review and release.
All Blocking Policies capabilities below are confirmed on the Advanced plan (and carried into Premium). None are available on Standard.
Block outbound file and form submissions to any web destination, including cloud storage portals, webmail, and file-sharing sites.
Outbound messages are stopped at the agent before delivery; blocked emails move to Mail Quarantine for review and release.
Internal and Microsoft Exchange email is covered alongside SMTP, closing the gap for corporate mail environments.
Block file transfers over FTP regardless of destination.
Block file and message transfers over Jabber-based messaging protocols.
Any attempt to copy a file to a USB stick, external drive, or removable storage device can be blocked by policy.
Block print jobs on both local and network printers; the job is stopped before it prints.
Block copy-paste transfers of sensitive content between applications or to external destinations.
Block outbound network connections for specific processes, preventing an application from sending data regardless of the protocol it uses.
Block file attachments sent through desktop messenger clients — WhatsApp, Telegram, Teams, Slack, and others — without disabling the messenger itself.
Prevent the creation of screenshots on the endpoint, removing a frequent data-exfiltration workaround.
Premium extends blocking with content-aware matching by digital fingerprint, hash, or sensitivity label — blocking by document identity, regardless of which channel an employee tries to use.
The Anexet endpoint agent runs on each monitored workstation. When a user initiates a transfer that matches an active Blocking Policy — whether that is an HTTP upload, an email with an attachment, a USB copy, or a print job — the agent intercepts it before the data leaves the device. The send is cancelled in real time, an incident record is created, and the security officer is notified immediately.
Because Anexet is deployed entirely on-premise, the blocking engine operates inside your network without routing traffic through any external service. All incident records, Mail Quarantine contents, and policy configurations remain within your infrastructure. The vendor has no access to your data, your rules, or your blocked events.
Four steps from a policy rule to a cancelled transfer and a closed incident.
Configure a Blocking Policy in the Client Console — choose the channel or protocol, set the scope to the relevant user group, and assign a risk level.
1
The endpoint agent enforces the rule in real time: when a user initiates a matching transfer, the send is cancelled before the data leaves the device.
2
Every blocked transfer creates an incident record — user, timestamp, channel, file details — and for SMTP blocks the full message enters Mail Quarantine.
3
The security officer reviews the incident in the Client Console, releases or deletes quarantined mail, and closes or escalates the case.
4
Configure a Blocking Policy in the Client Console — choose the channel or protocol, set the scope to the relevant user group, and assign a risk level.
1
The endpoint agent enforces the rule in real time: when a user initiates a matching transfer, the send is cancelled before the data leaves the device.
2
Every blocked transfer creates an incident record — user, timestamp, channel, file details — and for SMTP blocks the full message enters Mail Quarantine.
3
The security officer reviews the incident in the Client Console, releases or deletes quarantined mail, and closes or escalates the case.
4
Common questions about how Anexet Blocking Policies stop outbound data transfers.
Yes. The endpoint agent intercepts the transfer at the moment of action — when the file is being sent, copied, or printed — before it reaches the destination. The send is cancelled; the data does not leave the device.
HTTP, SMTP, MAPI, FTP, and XMPP for network transfers; USB and removable drives; local and network printers; clipboard; process-level network traffic; desktop messenger file transfers (WhatsApp, Telegram, Teams, Slack, and others); and screenshot capture. All are available on the Advanced plan.
Anexet is deployed on-premise; the vendor has no access to your data. The blocking engine, all incident records, Mail Quarantine contents, and policy configurations remain entirely within your network.
Blocking Policies are available from the Advanced plan. Standard includes interception and monitoring but does not block transfers. Premium extends blocking with content-aware matching by digital fingerprints, hash, and sensitivity labels.
No. When an SMTP rule blocks an outbound message, it moves into Mail Quarantine inside the Client Console. The security officer can review the message and its attachments, release it to the original recipient if it is legitimate, or delete it. The email is not silently dropped.
Yes. Blocking rules are applied through agent profiles, which map to user groups, departments, or individual workstations. You can run strict blocking policies for high-risk roles while applying lighter monitoring-only rules elsewhere.
Endpoint agents are supported on Windows, Linux, and macOS ARM64. Specific channel coverage varies by operating system; your implementation team will confirm the exact matrix for your environment during the demo.
Tell us which channels you need to control and what data you are protecting — we will map it to the right plan and arrange a demo or a free trial of Anexet Ultimate.
