Introduction

If you've been following my articles, you know I'm a bit of a skeptic when it comes to technology hype, especially AI. It seems like every vendor has an AI story these days. AI in your applications, AI managing your endpoints, AI answering your questions, and now AI agents that are supposedly going to do everyone's jobs for them.

Don't get me wrong. I believe AI is going to have a significant impact on how we work. In many ways, it already has. But after spending more than three decades in IT, I've learned that there's a pretty big difference between what technology vendors tell us is possible and what we can successfully deploy, secure, and manage in an enterprise environment.

Earlier this year, I wrote about how Island was bringing AI directly into its Enterprise Browser. What interested me at the time was the simplicity of the idea. Rather than forcing employees to open another application or browser tab to interact with AI, why not put AI directly into the environment where they're already working?

Since then, Island has continued expanding its AI capabilities, and after digging through the latest technical documentation and management console, there's quite a bit more going on than simply adding an AI assistant to a browser.

Island is building out capabilities that address AI security, agent discovery, application development, and automation. And perhaps most interestingly, some of these capabilities extend beyond Island's own browser into third-party applications, cloud services, and AI platforms.

So, let's take a closer look at what Island has been up to, how these technologies fit together, and what they could mean for enterprises looking to move beyond simply experimenting with AI.

The Problem: AI Is Moving from Answering Questions to Taking Action

Before getting into the technology, let's talk about the problem Island is trying to solve.

Imagine you're an account manager preparing for a customer renewal. You need to review the account in Salesforce, look through recent support tickets in ServiceNow, examine previous proposals, and put together a summary of where things stand.

Today, you could use AI to help with much of this work, although you might spend a fair amount of time gathering information and copying it between systems.

Now imagine you tell an AI agent to do all of that for you.

The agent accesses Salesforce, checks ServiceNow, reviews relevant documents, builds a summary, and drafts an email with recommended next steps.

Pretty cool, right?

But let's take it one step further. What happens when the agent decides to update the Salesforce opportunity or send that email without asking you first?

That's where things get interesting, especially for the security and IT teams.

Who authorized the agent to access those systems? Does it have the same permissions as the employee? Can it retrieve sensitive information? What happens if the agent is tricked into executing an action it shouldn't?

And if something goes wrong, can we determine exactly what happened?

These aren't hypothetical security concerns. They are the types of questions organizations need to answer as AI becomes more autonomous.

The challenge isn't just protecting the data anymore. It's governing what AI is allowed to do with that data and which actions it can perform.

Island's Approach: Five AI Capabilities, One Broader Strategy

Island has organized much of its AI portfolio around five capabilities:

Agentic Endpoint Posture: Discover AI technologies and assess the risks they introduce.

AI Protect: Monitor, secure, and govern AI usage and interactions.

AI Browser: Bring AI directly into the employee's browsing experience.

AI Publish: Provide a managed environment for publishing AI-created applications.

AI Automate: Allow users to build and execute governed AI agents and workflows.

At first glance, these might seem like separate products addressing different problems.

But what stands out to me is how they fit together. An organization needs to know which AI technologies are being used, protect the information those technologies access, provide employees with approved AI capabilities, and manage the applications and automations users create.

Island enterprise AI capabilities extend beyond the browser, bringing together AI enablement, runtime enforcement and visibility across supported enterprise systems and AI platforms.

Let's look at each one.

Agentic Endpoint Posture: What's Actually Running on Your Endpoints?

For years, those of us in end-user computing have worked to maintain visibility into the applications installed on our endpoints.

We've used UEM, endpoint detection and response (EDR), software inventory, vulnerability management, and plenty of other tools to understand what is installed and whether it poses a risk.

Now throw AI agents into the mix.

Employees are installing AI-enabled development environments, browser extensions, coding assistants, and tools that leverage Model Context Protocol (MCP) servers. Some of these components may have access to local files, enterprise applications, or external services.

And it's not always obvious what they've installed or what those components can do.

Island's Agentic Endpoint Posture module is intended to help answer those questions.

From the management console, administrators can inventory AI applications, MCP servers, AI skills, hooks, code packages, IDE extensions, and browser extensions.

Island also identifies findings associated with misconfigurations, potential information disclosure, risky behavior, code execution, and other security concerns.

Island's Agentic Endpoint Posture dashboard highlights security findings and provides visibility into the AI-related components that make up an organization's attack surface.

What I like about this approach is that it recognizes AI security isn't limited to monitoring which chatbots employees visit.

An AI coding assistant with access to local files and external tools introduces a different set of risks than someone asking ChatGPT to summarize a public article.

Of course, detecting a potential risk doesn't necessarily mean the component is malicious or actively being exploited. Administrators still need to investigate the finding and determine what action, if any, is appropriate.

But as more AI capabilities find their way onto corporate endpoints, having this visibility is going to become increasingly important.

AI Protect: Let Employees Use AI Without Giving Away the Farm

This is probably the area that will get the most attention from CISOs and security teams.

Organizations generally want their employees to use AI, but they also have a responsibility to protect corporate information.

Consider an employee who copies a confidential financial report into a public AI application and asks for a summary. The employee may have perfectly good intentions, but that doesn't mean the organization wants that information leaving its control.

Island AI Protect addresses this problem by extending familiar enterprise security controls into AI usage.

It provides visibility into AI applications, users, prompts, models, and data movement. Administrators can configure policies governing approved applications, sensitive data, AI extensions, and supported AI interactions.

Island also provides DLP capabilities that can detect and restrict the movement of certain types of information, such as personally identifiable information, financial data, and source code.

But here's where things get more interesting.

Island isn't limiting AI Protect to its own browser.

The platform's AI Runtime capabilities extend to multiple control points, including browser extensions, secure web gateways, MCP integrations, supported AI hooks, and third-party API integrations.

For example, Island documents integrations with platforms such as Microsoft Copilot Studio, Salesforce Agentforce, Amazon Bedrock, Anthropic, OpenAI, Snowflake Cortex, Databricks, and ServiceNow.

That is a much broader approach than simply controlling access to public AI websites.

There is, however, an important distinction worth understanding.

Some integrations allow Island to retrieve activity and provide visibility after an AI interaction has occurred. Others support inline inspection, where a request can be evaluated before it proceeds.

If you're responsible for security architecture, this is something I'd pay close attention to.

Being able to tell me an agent performed an unauthorized action is useful. Being able to stop that action before it happens is an entirely different level of protection.

Both have value, but they shouldn't be confused with one another.

AI Browser: Putting AI Where People Already Work

I covered AI Browser in more detail in my earlier article, so I won't rehash everything here.

The concept is straightforward: instead of making employees leave their work to use AI, Island brings AI into the browser.

Administrators can configure supported AI providers and models, while employees can interact with an AI assistant directly from their browser experience.

One thing I didn't get into as much in my earlier article was the flexibility Island provides in choosing the AI models and services available to employees.

Island gives administrators a choice of AI providers, including OpenAI, Anthropic, Google, and others, rather than tying the browser to a single model.

What makes this interesting is the ability to use context from the environment.

For example, imagine our account manager reviewing a customer record in Salesforce. Instead of copying information into a separate AI chat window, they can potentially ask the embedded assistant to help analyze what's on the page, subject to the permissions and policies configured by the organization.

Island also supports assistants, skills, contextual suggestions, and integrations with approved enterprise knowledge and tools.

This is where I think AI can have a real impact on the end-user experience.

I've spent a significant portion of my career helping organizations improve the digital workspace. One thing I've learned is that adding more applications, more authentication prompts, and more complicated workflows rarely makes employees more productive.

If AI can help people accomplish what they're already trying to do without adding unnecessary steps, that's a benefit worth pursuing.

The other side of the equation is governance.

IT needs to determine which AI providers are approved, what information can be shared, and which capabilities employees can access.

Island's approach combines that administrative control with the actual employee experience.

That combination is what makes AI Browser interesting to me.

AI Publish: What Happens When Everyone Can Build an Application?

Here's another area where AI is changing the traditional IT model.

We're increasingly seeing employees use AI to create applications without having to become professional software developers.

Call it vibe coding, low-code development, or whatever term comes next. The fact is that creating software is getting easier.

That's a good thing, right?

Well, potentially. But imagine an organization where every department starts building its own applications without any oversight.

Where are those applications hosted? Who can access them? What corporate information do they use? Who maintains them when something breaks?

Sound familiar? We've been dealing with shadow IT for years, and AI could make the problem considerably bigger.

Island AI Publish is intended to help organizations address this new generation of employee-created applications.

What I found interesting is that Island isn't trying to replace the tools employees use to create these applications. Instead, it provides a way to upload, publish, and manage them within the enterprise, including version history and connections to approved business systems.

Island AI Publish provides a way to upload AI-created applications, track versions, and configure integrations with enterprise services.

The opportunity is to allow employees to create useful business applications while providing IT with a more structured way to manage how those applications are distributed and used.

For example, a sales team might build a small application that analyzes customer renewal data and presents recommended actions.

Rather than everyone running their own version from an unmanaged service, the organization could potentially make that application available through a centrally managed environment.

I find this area particularly interesting, although I would want to spend more time validating the complete application lifecycle before drawing conclusions about how well it addresses traditional application management requirements.

The concept makes sense. The details around deployment, security, updates, and lifecycle management are what I'd want to examine next.

AI Automate: Now We're Letting AI Do the Work

This is where Island's approach moves from assisting employees to allowing AI to take action.

AI Automate provides a no-code environment for creating agents, skills, and repeatable workflows.

These automations can interact with enterprise systems using supported browser actions and MCP integrations.

Going back to our account manager, imagine an agent that gathers customer information, reviews support activity, and prepares a renewal briefing.

Rather than just producing a summary, the agent could potentially carry out approved follow-up actions across the applications involved.

Now the question becomes: how do we keep that agent from doing something it shouldn't?

Island provides policy controls for determining who can create automations, who can use shared workflows, which models are approved, and which tools are available.

Administrators can assign users different roles, such as Automation Creator or Consumer. They can also control workflow sharing and audit agent activity.

Island AI Automate provides granular administrative controls over agent enablement, user roles, browser automation, and auditing.

Island documents human-in-the-loop capabilities for actions that require oversight.

That's important because not every automated task should have the same level of independence.

I might be perfectly comfortable with an agent gathering information and creating a draft. I would be considerably less comfortable allowing it to update financial records or send sensitive communications without appropriate authorization.

Another feature worth mentioning is the operational reporting.

AI Automate includes metrics such as workflow adoption, execution success, failures, runtime, and estimated time savings.

For those of us trying to justify technology investments, these are the kinds of measurements that matter.

It's one thing to tell management that employees are using AI. It's another to demonstrate that an automation is completing useful work consistently and reducing the effort required to perform a business process.

That doesn't automatically prove a financial return on investment, but it provides information organizations can use to evaluate one.

Under the Hood: AI Runtime and MCP Gateway

Now let's get into some of the technology that I think makes Island's broader approach particularly interesting.

Two components worth understanding are AI Runtime and MCP Gateway.

If you're not familiar with MCP, think of it as a standardized way for AI applications and agents to communicate with external tools and services.

An AI agent might use MCP to access Salesforce, retrieve information from Google Drive, interact with Jira, or perform actions through another enterprise application.

That's useful, but there's an obvious security concern.

If an AI agent can access all those systems, what prevents it from performing an action the organization never intended?

Island's MCP Gateway is designed to give organizations a governed point of access to approved tools and services.

Rather than allowing agents to establish independently managed connections to numerous MCP servers, supported clients can connect through a centralized gateway.

The gateway handles several important functions.

First, it identifies who or what is making the request. That might be an employee authenticated through the organization's identity provider or an unattended agent with its own identity and API key.

Second, Island applies a Tools Policy to determine which integrations and actions that identity is permitted to use.

For example, an agent might be allowed to read Salesforce records but not modify them.

Third, supported tool calls pass through AI Runtime inspection, where configured policies can evaluate the request and potentially allow, redact, or block it.

Finally, Island brokers the credentials needed to access the upstream service and records the interaction for auditing.

One detail that caught my attention is that Island's Tools Policy is enforced when tools are presented to an agent and again when the agent attempts to invoke them.

In other words, simply attempting to call a tool directly doesn't bypass the authorization policy.

Another interesting feature is how Island handles non-human identities.

An unattended agent can have its own identity rather than simply operating as another employee. This allows administrators to assign permissions and attribute activity to the agent.

The documentation does identify some constraints. For example, headless MCP Gateway agents currently use supported integrations with admin-managed static credentials rather than an employee's personal OAuth connections.

There are also different behaviors when services or inspection mechanisms fail.

By default, the MCP Gateway documentation says a runtime inspection failure allows an otherwise authorized tool call to proceed without inspection. Administrators can change that behavior to fail closed. The gateway itself is designed to deny access when unavailable.

Why does any of this matter?

Because giving an AI agent access to an application isn't the same as authorizing every possible action it might perform.

As organizations begin using agents for more consequential tasks, that distinction becomes critical.

The MCP Gateway and AI Runtime architecture represents Island's effort to bring identity, tool authorization, data protection, and auditing together around those actions.

Does Everything Have to Run Through Island Browser?

This was one of my first questions when looking at Island's expanded AI capabilities.

After all, Island built its reputation around the Enterprise Browser. But organizations already have significant investments in endpoint management, network security, identity, and cloud infrastructure.

Are they expected to replace all of that to take advantage of Island's AI security capabilities?

Based on the documentation and conversations I've had with them, the answer is no, although the available protections depend on how the technology is deployed.

Island supports different control points, including its browser, extensions, desktop components, API integrations, and network-based inspection.

There are even documented integrations that allow selected traffic from Zscaler Internet Access, Netskope, and Palo Alto Prisma Access to be forwarded to Island's Explicit Proxy.

That means organizations can potentially add Island inspection and policy enforcement to selected traffic flows without replacing their existing primary security service edge platform.

I think this is an important development.

Most large enterprises aren't interested in ripping out an established security architecture just because another vendor introduces new AI functionality.

They want to understand how the new capabilities fit into what they already own.

However, there are tradeoffs.

A browser-based control point may provide information that isn't available through an API integration. Likewise, a cloud-hosted agent may expose telemetry that a browser-based security control never sees.

Island makes clear that support varies across control points.

For example, the AI Runtime support documentation identifies file attachments as a limitation for runtime inspection, even though separate file movement and DLP capabilities exist elsewhere in the platform.

The documentation also contains differing release-status descriptions for certain specialized AI security and content-moderation guardrails.

So while the architecture is expanding, I'd encourage anyone evaluating these capabilities to look closely at what is supported in their specific environment.

The important question isn't simply whether Island integrates with a particular product.

It's what Island can see, what it can control, and what happens when something goes wrong.

What Would I Want to See in a Customer Evaluation?

If I were evaluating Island's AI capabilities for an enterprise deployment, I wouldn't stop at the feature list.

I'd want to see the technology in action.

For example, I'd want to take an approved AI agent and give it access to a business application through MCP. Let it perform an authorized read operation, then attempt an action the security policy doesn't permit.

Does Island block the action? What does the employee or agent see? What does the administrator see in the audit trail?

I'd also want to test sensitive data handling, verify which control points can prevent an action versus simply report it, and understand the operational impact of inspection failures.

Then I'd look at the employee experience.

Can a user build a useful automation without spending days learning the platform? Can another employee consume that workflow without needing unnecessary permissions? And does the automation actually save enough time to justify its use?

These are the kinds of questions that move us beyond a marketing demonstration and into a meaningful technical evaluation.

Island has documented a considerable amount of functionality. The next step for any enterprise considering deployment should be validating those capabilities against its actual workflows and requirements.

Final Thoughts: Island Is Thinking Beyond the Browser

When I first started looking at Island, I was interested in the Enterprise Browser and its ability to provide a more secure, controlled environment for accessing business applications.

When Island introduced its AI capabilities, I was intrigued by the idea of putting an assistant directly into the browser.

Now, looking at the broader portfolio, I think there's a bigger story developing.

Island is bringing together capabilities that address several challenges organizations are going to face as AI adoption increases.

How do we know what AI technologies employees are using? How do we protect corporate information? How do we make AI easier to use? How do we manage employee-created applications? And how do we govern agents that are increasingly capable of acting on their own?

Island's five AI capabilities are intended to address those questions.

What's particularly interesting to me is that the company isn't limiting this strategy to browser-based AI usage. Its investments in AI Runtime, MCP Gateway, and third-party integrations suggest that Island sees an opportunity to provide governance across a much broader enterprise AI environment.

Does that mean Island has solved every AI security and governance challenge?

Of course not.

There are areas that need further validation, some capabilities are still evolving, and organizations will need to understand the differences between visibility and enforcement across the available integrations.

But I think Island is moving in an interesting direction.

For years, we've focused on securing the employee, the endpoint, the network, and the applications employees use.

Now we're introducing AI agents that can interact with many of those same systems, sometimes without a human directly involved in every action.

That's going to require us to rethink some of our traditional approaches to security and management.

And while there's no shortage of companies promising that AI is going to transform the enterprise, I'm more interested in the ones developing practical ways for organizations to actually deploy and manage it.

Island is making a serious effort in that direction.

To me, that's the real story here. Island isn't simply putting AI into the browser anymore. It's working to make AI something enterprise IT can enable, manage, secure, and hold accountable.

And if we're going to let AI agents start doing real work, I'd say that's a pretty important place to start.

Technologies