Browser Rules blocks dangerous downloads, even hidden inside ZIPs, warns about or blocks websites, and keeps malicious commands out of the clipboard. Every check happens in the browser; you set the rules from one console.
Google Chrome
Microsoft EdgeEach protection has its own policies, checked from the top: the first that matches decides whether to allow, record, warn or block.
Programs, scripts and risky file types are stopped before they reach the disk, whatever they are named.
Block websites outright, or show a warning people must acknowledge before they carry on.
Keeps malicious commands out of the clipboard, so there is nothing dangerous to paste and run.
Every message shows your organisation's name, your wording and who to contact.
Fake CAPTCHA and "fix this error" pages copy a command to the clipboard and talk people into running it.
An "invoice" or "photos" ZIP holds a program, sometimes inside another ZIP, named to look like a document.
File sharing, personal webmail or tools that aren't approved: some need blocking, others just a reminder.
Sensible defaults protect everyone from the first minute. Add your own policies when you're ready.
Choose how you manage your computers and download a ready-made file with your enrolment key in it. Browsers connect by themselves.
Start from the built-in defaults, then add policies for everyone, for groups or for named people. The first match wins, so exceptions are easy.
Every block, warning and override lands in the audit log, with the file's fingerprint and a one-click lookup. Browsers pick up changes within minutes.
ChromeEdgeWho, what, whereTarget policies at groups or named people, recognised from the browser's signed-in account.
Templates with your wording, colours and a contact, shown as a banner, overlay or full page.
Who, what and where, with the file's SHA-256 and the link it came from.
Let someone pause protection on one website for a while, with a reason that's recorded.
Owners, admins and read-only members. Two-factor or passkeys for everyone.
Policies are versioned, so you can see what changed and when.
The extension protects people the moment it's installed. Enrol it in the admin console to make the policies your own.
Install it from the Chrome Web Store, or force-install it with your device management, and the default policies protect straight away.
Your device management adds one enrolment key, and the admin console takes over.
Already installed? Enrol it at any time: nothing needs reinstalling.
Browser Rules inspects downloads and pages inside the browser itself. Your files and what people type stay where they are.
Downloads, ZIPs and clipboard text are checked in the browser. No cloud scanning.
Send full addresses or just the website, with or without who it was, from the Privacy settings.
Every organisation's data is kept apart. Our support team can only look in when you allow it, for a set time.
If the console can't be reached, browsers keep enforcing the last policies they received.
Users are the people whose browsers are enrolled. Console admins don't count.
For small teams, or a trial before you roll it out.
For organisations with more than 100 users.
Prices exclude VAT. Managing several organisations as an IT provider? Get in touch.
Yes. Once installed, its default policies block programs and risky file types (even inside ZIPs), ZIPs within ZIPs and malicious commands on the clipboard. To set your own policies, enrol it in the admin console, which is free for up to 100 users.
Because security shouldn't be expensive. Small organisations are targeted by the same tricks as large ones, and usually have the least to spend on protection. The Free plan has every protection; larger organisations will pay for more users, a year of audit history and priority support.
No. It's an extra layer in the place many attacks begin: it stops risky downloads and websites, and keeps malicious commands out of the clipboard. Keep your antivirus, email filtering and updates.
No. Downloads and ZIPs are checked inside the browser on each computer. Only audit events (what was blocked, warned or recorded) go to the console, and the Privacy settings decide how much detail they carry.
Google Chrome and Microsoft Edge on Windows, macOS and Linux. Both install it from the Chrome Web Store, so one extension covers both.
From the account signed in to Chrome or Edge, so no per-person setup is needed. You can also set the user by policy.
Not when it's installed by policy. If you allow it, people can pause protection on one website for a short time, with a reason that goes in the audit log.
They're protected once the extension is allowed in them. The setup guide shows how, or you can turn private windows off by policy.
Browsers keep enforcing the last policies they received, and send their audit events when they're back online.