AI browsers at work
How to Block the Dia AI Browser at Work
Dia puts an AI assistant beside every tab and can now act on pages and connected apps. When staff install it on their own, page content and work accounts end up in a tool you never approved.
Next step
AI Agent Blocklist
A daily list of AI browsers, browser agents and agent extensions, with domains for your firewall and DNS filter and device identifiers for Jamf and Intune.
From $99 a month for one organisation
The problem
Is Dia browser safe for company data? Start with what it can see
Dia is a Chromium browser built around an assistant. Its value comes from reading what you read. That is also why it matters who installed it and which account it runs under.
Open tabs and pages
When a user includes a page in a request, the prompt and the relevant page content go to a cloud AI model. A tab with a customer record is just another tab to the assistant.
Leaves the devicePages already viewed
Proactive features such as a morning summary work from pages the user has viewed. Dia tries to keep sensitive sites out of that, but it is not a control you can set or audit.
Leaves the deviceMail and calendar
Dia added tools for Gmail and Google Calendar in 2025, and its assistant chooses when to use tools such as mail, calendar, Slack and tabs. Drafts and events wait for the user to confirm.
Acts with the user's loginConnected apps and MCP
Release notes from November 2026 cover MCP connections and an upgraded Atlassian integration. Each connection extends the assistant's reach past the browser into work systems.
Acts with the user's loginSkills
Skills are saved prompts that run on demand, built in plain language or taken from a gallery. Since 2025 they can draw on browsing history, so one shortcut can pull in many past pages.
Runs on requestFiles people attach
Users can attach documents to the chat. Dia offers an MDM key to block file types from its AI. A PDF or DOCX export from a work system is often the most sensitive thing in reach.
Leaves the deviceHow Dia changed in a year
- October 2025Dia 1.0 opens to everyone on Mac with no waitlist. Gmail and Google Calendar tools follow a week later.
- August 2026Release notes describe upgraded agent systems, with more reliable agent sessions in September.
- September 2026Dia retires its Memory feature and says the stored data is deleted.
- October 2026Dia 1.0 for Windows ships, with Skills on Windows the week after.
- November 2026Updates to MCP connections and the Atlassian integration on Mac and Windows.
A browser that changes this fast needs a rule that does not depend on any one feature. Blocking by app and by domain holds even when the feature list moves.
How it goes wrong
What happens when Dia runs unmanaged
Most Dia installs at work start the same way: a user downloads it, signs in with a personal Atlassian account and imports bookmarks from Chrome. From there, four things slip out of your view.
User asks
"Summarise this ticket and draft a reply to the customer."
Dia gathers
The prompt plus the page content it needs, sometimes from several tabs.
Gateway
The request passes through the vendor's AI gateway to a third party model provider.
Outside your logs
Your proxy sees encrypted traffic to an AI service. It does not see which customer record was in it.
Personal accounts hold work context
Content data that is not tied to an account is kept for 30 days, and content data improves Dia by default until the user turns it off. Under a personal account that choice sits with the user, not with you.
Agent actions in logged in sessions
Dia's agent works inside pages the user approved and cannot open other sites on its own. It still acts with whatever sessions are open, which can include admin consoles and finance tools.
Hidden instructions in pages
Researchers showed in 2025 that text hidden in web pages can steer AI browsers. Dia lists layered defences and says no defence is perfect. Read the full picture on our AI browser prompt injection page.
Regulated data with no agreement
Dia states that it is not HIPAA compliant and does not sign a Business Associate Agreement. Health, legal and finance teams need that answer before anyone opens a case file in it.
Signs Dia is already in use
- Dia appears in Mac or Windows app inventory in your MDM
- DNS or proxy logs show requests to diabrowser.com
- New Atlassian account sign-ups with work email addresses that IT did not request
- Help desk tickets about bookmarks or passwords moving from Chrome
- Your managed browser's usage drops on a team while web app use stays flat
- Sign-ins to work SaaS from a browser your access policy does not list
Gartner's December 2025 advice, "Cybersecurity Must Block AI Browsers for Now", covers this whole class of browser. Our summary of what it means for IT teams is on the Gartner block AI browsers page.
Dia's own controls
Dia browser enterprise controls and their limits
Dia now publishes device controls for macOS through MDM and server-side controls for organisations on its Enterprise plan. They help if you decide to allow Dia. They do not replace a block if you decide not to.
| MDM key (macOS) | What it does | Use it when |
|---|---|---|
| DiaAIRestrictedDomains | Turns off AI features, including chat and Ask on Page, on the domains you list and their subdomains | You allow Dia but want AI off on finance, HR and admin sites |
| DiaAIRestrictedDomainsExceptions | Keeps AI on for listed domains even when a broader entry would turn it off | One internal site should keep the assistant |
| DiaAIRestrictedFileTypes | Stops users attaching the listed file types to Dia's AI; each entry starts with a dot | You want no PDF, DOCX or XLSX uploads into chat |
| DiaRestrictLoginDomains | Allows sign-in only with email addresses on your domains | You want work use under work accounts only |
| DiaMinimumVersion | Blocks use until Dia is updated to at least that version | A version you have reviewed must be in place before anyone browses |
| DiaEnforceAutomaticUpdates | Keeps automatic updates on and locks the toggle | Always, if Dia is allowed at all |
Dia reads policies at launch. On a test Mac, open dia://policy to confirm what arrived. Key names come from Dia's enterprise controls page; check it for changes before you deploy.
What you can control
- AI on or off per domain, with exceptions
- File types that can be attached to the AI
- Which email domains can sign in
- Minimum version and forced updates
- Content sharing for the whole organisation
- Enrolment in Chrome cloud management, since Dia supports standard Chromium enterprise policies
What the published controls do not list
- One switch that turns every AI feature off everywhere
- A separate switch for agent sessions
- A switch for Skills
- A way to stop an unmanaged copy on a device you do not manage
Server-side controls on the Enterprise plan, enforced at sign-in for every member:
Dia browser disable AI, user side: a user can switch off content sharing under Settings, Privacy, Share content data. That limits product improvement use. It does not stop prompts and page context going to the AI when the user asks.
How we solve it
Decide first: block, fence or allow for a named group
Pick one path per group of users. Most organisations block Dia for everyone and make exceptions only where a team has a reason and an owner.
For most staff, contractors and shared Macs.
- App rule in Jamf or Intune
- Domain rule on DNS and firewall
- Inventory alert if it reappears
For a team that uses Atlassian tools daily and wants Dia's integration.
- Work accounts only, SSO
- AI off on sensitive domains
- No file uploads to chat
For a small group with a time limit and a review date.
- Separate device group in MDM
- Enterprise plan logging on
- Block for everyone else
Block Dia on Macs first
Dia started on the Mac and most installs at work are still there. Use an app rule so the browser cannot run, then a domain rule so it cannot be fetched again.
Jamf Pro: Restricted Software
- Go to Computers, then Restricted Software, then New.
- Enter a Display Name such as "AI browser: Dia".
- In Process Name, enter the exact name of the app bundle. Jamf recommends the full bundle name, as it appears in Applications.
- Select Kill Process, and Send email notification on violation if you want an alert.
- On the Scope tab, target all managed Macs and exclude any named group.
- Click Save. The rule applies at each Mac's next check-in.
To read a process name on a test Mac, open the app and run ps -acx in Terminal. More Jamf rules for agent extensions are on our Jamf extension blocking page.
Intune on macOS: script and report
- Go to Devices, By platform, macOS, Manage devices, Scripts, Add.
- Upload a shell script that quits Dia and moves the app out of Applications if found.
- Leave Run script as signed-in user at No, so it runs as root.
- Set Script frequency so it runs again on a schedule, and set a retry count.
- Add a custom attribute under Organize devices, Custom attributes for macOS that reports whether Dia is present.
- Assign both to your Mac device groups and check the device status report.
On Intune, a scheduled script does the job of a restricted software rule. Wider Intune rules for AI tools are on block AI with Intune.
Windows: App Control for Business
- In the Intune admin center, go to Endpoint security, App Control for Business, Create Policy.
- Choose Enter xml data and upload a policy with a deny rule built from the signature of Dia's installed files.
- Start in Audit only mode on a test group and read the local event logs.
- Switch to enforce and assign to device groups. App Control policies are device scoped.
Paths in the Intune admin center change from time to time. Check the current admin console before you write a runbook.
Network: DNS and firewall
- Add diabrowser.com and its subdomains to your DNS filter's block list.
- Load the AI browser list from the AI Agent Blocklist as a custom or external list on the firewall.
- Log blocked lookups so you can see which devices still try to reach Dia.
- Treat the network rule as the second layer. A copy already installed may keep running until the app rule lands.
Step by step DNS setups for common filters are on block AI with DNS.
Fencing instead of blocking? In Jamf, send Dia's keys in a configuration profile with the Application and Custom Settings payload. In Intune, use Configuration, New policy, macOS, Templates, Preference file, with the preference domain from Dia's enterprise controls page.
The list behind the rules
Block Dia, then the next AI browser your staff try
Users who lose Dia often try another AI browser the same week. A rule for one product leaves the gap open. The AI Agent Blocklist covers the AI browsers and agents around it and grows every day.
Block
- AI browsers by domain, for DNS and firewall
- AI browsers by bundle ID, package ID and process name, for Jamf and Intune
- Agent extensions by Chrome, Edge and Firefox ID
Monitor
- Lower risk grades in log only mode first
- Inventory matches against the identifier file
- New entries each day, so last week's gap closes
Allow
- Your managed browser and approved assistants
- A fenced Dia group, if you chose one
- Exceptions kept in your own allowlist, not ours
What an entry looks like
| Tool | Identifier type | Identifier | Risk grade |
|---|---|---|---|
| Comet | macOS bundle ID | ai.perplexity.comet | Graded |
| Comet | Windows package ID | Perplexity.Comet | Graded |
| BrowserOS | Windows package ID | BrowserOS.BrowserOS | Graded |
| Manus AI Browser Operator | Chrome extension ID | cecngibhkljoiafhjfmcgbmikfogdiko | Graded |
Every entry carries the tool name, category, identifier type and risk grade, so you can block all agents or only the higher grades. The browsers covered are listed on our list of AI browsers; the wider rollout plan is on how to block AI browsers.
Dia browser MCP connections reach tools outside the browser. If you fence Dia, use its allowed apps control and pair it with your MCP rules on blocking MCP servers.
The product
One list for the AI browsers staff try after Dia
The AI Agent Blocklist holds 2,600+ AI agent domains and 5,300+ agent identifiers on devices. Every entry is checked before it enters the list, and the lists update every day.
After an order we set up your download access within one business day. Plans start from $99 a month for one organisation.
- Plain domain list, hosts file and PAC file
- Firewall external list format for firewalls that read a URL list
- DNS filter import files
- CSV and JSON with tool name, category, identifier type and risk grade
- macOS and Windows identifiers for Jamf and Intune
- Chrome and Edge extension block lists for Group Policy, Intune and the Google Admin console
Ask us or order a plan
Tell us what you need to block and where your rules live. We reply within one business day.
- Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
- Updated every day as new AI browsers, agents and extensions appear
- Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you
FAQ
Questions admins ask about Dia
Is Dia browser safe for work?
Dia lists layered protections: its agent cannot open sites on its own, form fills and emails wait for approval, and passwords are hidden from it. It also says no defence is perfect. For a company the bigger issue is an unmanaged copy sending page content to cloud AI under a personal account.
Can you disable AI in Dia browser?
Not with one switch. Dia's published controls let an admin turn AI off on a list of domains, block file types from the AI and turn off content sharing. Users can turn off content sharing in Settings, Privacy. If you want no AI at all, block Dia and keep a managed browser.
Is there a Dia browser enterprise version?
Dia offers device controls through MDM on macOS and server-side controls on an Enterprise plan, such as mandatory single sign-on, session revocation, activity logs sent to your own storage and allowlists of connected apps. Check Dia's current enterprise documentation for the full list and price.
Does Dia browser support MCP?
Yes. Dia's release notes from November 2026 mention MCP connections and an Atlassian integration that moved to a newer MCP version. Connected apps give Dia's assistant reach into tools beyond the browser, so treat them like any other MCP connection and allow only the ones you approve.
How do I uninstall Dia browser?
On a Mac, quit Dia and move it from Applications to the Bin. On Windows 11, open Settings, Apps, Installed apps, find Dia and choose Uninstall. On managed fleets, use your MDM so the removal is logged and the app cannot come back. Fleet removal is covered on remove AI browsers from managed devices.
Does blocking diabrowser.com stop Dia?
It stops new downloads and the website, but a copy that is already installed may keep working. Pair the DNS or firewall rule with an app rule in Jamf or Intune so Dia cannot launch, and with inventory so you can see where it is installed.
Dia and Arc are trademarks of The Browser Company of New York, Inc. Atlassian is a trademark of Atlassian. Perplexity and Comet are trademarks of Perplexity AI, Inc. Manus and BrowserOS are trademarks of their owners.
Chrome, Gmail and Google Calendar are trademarks of Google LLC. Slack is a trademark of Slack Technologies, LLC. Microsoft, Windows and Intune are trademarks of Microsoft Corporation.
Mac and macOS are trademarks of Apple Inc. Jamf and Jamf Pro are trademarks of Jamf. Gartner is a trademark of Gartner, Inc.
Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.