Invisible By Design: What a Successful Browser Deployment Actually Looks Like

A successful browser rollout is the one nobody notices. Andrew Rollo, Senior Customer Engineer at Google Chrome Enterprise, has led deployments across organizations with 10,000-plus endpoints, and his benchmark for success has nothing to do with features. It is silence.

The Browser Is the New Endpoint

Rollo has led browser deployments for organizations with 10,000-plus endpoints, with a dedicated focus on healthcare. His starting point is a reframe: most health systems are still managing the browser the way they always have, and that is no longer enough. For years, a GPO on Windows or a plist on a Mac was considered sufficient. Rollo compares this moment to the early days of antivirus software, when a handful of scattered tools eventually gave way to dedicated protection because organizations realized how much sensitive data lived on internet-connected machines. "All of that data that's sensitive is in the browser, and the browser is the thing that needs to be secured," he said. The tool clinicians and staff use to get their work done all day is the same tool attackers are most interested in.

Update Cadence Is the Real Security Control

If there is one thing Rollo wants CIOs to internalize, it is this: how a health system updates its browser matters as much as how it manages it. He draws a direct line between browser updates and vulnerability remediation. "It's our frequent updates of the browser that prevent the browser from being hacked," he said. Skipping or delaying updates is not a minor operational gap. It is the equivalent of ignoring a known vulnerability.

Extensions Need a Policy, Not a Switch

Shadow IT shows up in the browser through extensions, and Rollo argues most organizations handle it wrong in one of two directions: blocking everything or allowing everything. Neither works. Extensions can add real functionality, a calculator, a PDF reader, tools staff actually need, but unmanaged access opens the door to data loss or system instability. His fix is governance with a feedback loop rather than a blanket policy. "It's a conversation that you have to have with users, not just block all or allow all," he said. Health systems need a defined process for staff to request and justify the extensions they need.

AI Belongs in the Browser, With Guardrails

Rollo sees the instinct to block AI entirely as a short-term fix with a long-term cost. He is candid that early tools left something to be desired, in his words, and many organizations responded by shutting AI access down completely. He argues that posture will not hold. Organizations that block AI outright will lose the productivity gains their peers are already capturing. His recommended approach mirrors his extension advice: standardize on a single sanctioned AI tool, restrict the browser to that tool, and control what data can be entered into it. That means actively preventing staff from pasting medical record numbers or other protected information into an AI prompt, while still giving them a sanctioned way to use the technology for their actual work.

A Good Rollout Feels Like Nothing Happened

Asked what success looks like for clinical staff on day one, Rollo's answer is deliberately unglamorous: invisible. Not literally unnoticed, since some change is expected, but frictionless enough that nobody is flooding the help desk. He points to persona-based design as the mechanism. Google Chrome Enterprise deployments are built around what Rollo calls customer user journeys: a nurse and a pharmacist both need a browser, but they need different things inside it. "A pharmacist would see inventory, a nurse might see a different set of scheduling functions," he said. Each identity opens to the tabs, bookmarks, and tools relevant to that role, with safe browsing protections working quietly in the background. If a user clicks something risky, the system should catch it cleanly, not disruptively. The only comments a CIO should hear afterward, in Rollo's view, are good ones.

What to Ask Before Committing to a Deployment

Rollo's checklist for CIOs evaluating a new enterprise browser starts with identity. Every user needs credentials, whether a smart card, badge tap, or username and password, and that identity system has to function cleanly inside the browser. Identity is what makes both access control and after-the-fact auditing possible. From there, the priority shifts to the electronic health record. Rollo advises confirming whether the EHR runs natively in the browser or whether legacy components will require a virtualization layer through vendors like Citrix, VMware, or Cameo. The final piece is network throughput. Telehealth and video conferencing already strain healthcare bandwidth, and browser update cycles add to that load. Rollo recommends mapping network usage across the day so updates can run without disrupting EHR access or care delivery, particularly as HIPAA requirements around encryption continue to tighten.

The Takeaway

For CIOs weighing a browser strategy, Rollo's framework offers a clear starting order: lock down identity, confirm the EHR works in the browser, manage extensions and AI access with policy instead of blanket rules, and use update cadence as a live security control rather than a maintenance afterthought. Done well, none of it should be visible to the people using it every day.

Andrew Rollo is Senior Customer Engineer at Google Chrome Enterprise.