How a Leading Global Private Equity Firm Went From Zero Approvals to a Secure AI Agent Program In Weeks, not Months

Unlocking new competitive advantages for approximately $150B of assets under management

2,000
Machines covered across full endpoint estate
Months to Weeks
Approval time for new AI agent platforms
3
Major AI agent providers approved
"My leadership team approved these tools because I could show them with Geordie what the agents were doing. Not what the model was doing. Not what the network was logging. What the agent was actually doing, step by step, on their behalf. That's the view that matters."
- Senior Security Engineer, CISSP

Company Background

A leading global private equity firm with approximately $150B assets in management across complex investment portfolios, serving institutional clients across multiple geographies, was navigating one of the most significant technology transformations in their industry's history: the rapid adoption of AI across every function of the business.

With strict regulatory obligations, client data privacy requirements and complex compliance mandates, the firm needed a way to say yes to AI without flying blind, in order to secure a competitive advantage.

The security engineer responsible for making that happen is a CISSP with over a decade of infrastructure and security experience, who is focused specifically on AI agent security in the organization,  

Nobody really knows the rulebook for AI security yet. And that's what makes it exciting. You have to figure it out for yourself, come to your own conclusions, and build something that actually works for your environment.

The Challenges

Before Geordie, the firm had taken the only approach that felt defensible given the tools available: lock everything down. No Copilot. No Claude. No AI tooling of any kind approved for production use. A single internal hackathon had shown what was possible — automated client memo workflows, productivity gains across administrative functions — but there was no safe path to scaling those experiments.

The core problem was not a lack of willingness to adopt AI. It was a fundamental lack of visibility. Without being able to see what agents were doing, where they were connecting and what data was flowing through them, the security team had no basis on which to make an informed recommendation to leadership.

The specific challenges they needed to solve were:

  • No visibility into the agent environment: No inventory of what was running, which models were being called or what tools were being used inside development environments
  • No audit trail for AI approvals: No way to provide leadership with documented evidence of oversight when approving new tools
  • Active compliance exposure: Requirements under financial services regulations and client contracts around data handling, privacy and AI governance that could not be met without visibility
  • Speed of AI adoption outpacing governance: Competitors were moving ahead while the firm waited; they needed a path to approve AI agents in weeks rather than months
  • No solution built for the agent-specific problem: Existing tools either required SSL inspection that conflicted with existing VPN infrastructure, installed persistent agents on machines or focused on LLM-level monitoring rather than agent behaviour

We had AI agents completely locked down. And the reason was simple; we had no way to see what was actually happening. Without visibility, you can't accept risk. You can only block it.

Requirements

Complete visibility

Into AI agent activity across the estate without SSL inspection or persistent endpoint agents

Audit trail

Support executive-level AI approvals and regulatory compliance

Fast time to value

Meaningful results were needed in days, not months

No disruption to existing infrastructure

Support AI agent adoption and end user experience

Compliance mapping

For relevant regulatory and client frameworks

Built to keep pace

A vendor team that could move at the speed the market demanded

Why Geordie

The firm evaluated a competing product before selecting Geordie. The decision came down to two factors: technical fit and team responsiveness.

The competing solution couldn't match the environment.

The competing solution required significant configuration out of the box and could not match the pace at which the firm needed to move. More critically, its architecture required SSL inspection, which was a fundamental problem for an environment already running VPN-based inspection at the network level.

Lightweight, non-intrusive, and compatible by design.

Geordie's approach was different in ways that mattered specifically to this environment. Rather than deploying a persistent agent, Geordie ran as a scheduled task that was lightweight, non-intrusive and compatible with existing infrastructure. No SSL inspection. No endpoint agent. No rearchitecture required.

The team moves at the speed the business needs.

What ultimately sealed the decision was the team's willingness and ability to move fast in response to customer feedback. In his first week with the product, the security engineer sent an extensive feedback document covering every gap and request he could identify.

"Most of the time you submit a feature request and hear back in a quarter. Geordie just got it done. That's a completely different relationship from a vendor who tells you to come back in four months. I can't wait four months. If a new AI tool drops, I need to be ready to approve it in weeks."

Built for this problem from the ground up.

The final piece of the decision was a deliberate choice to back a company built natively for the problem rather than one retrofitting existing technology onto a new challenge.

The competing product needed a lot of work before it could do anything useful. And even then, the architecture would have created conflicts with our existing infrastructure that we couldn't accept.

Geordie doesn't sit on the machine the way a traditional security agent does. That was a big deal for us because it meant one less thing running on endpoints, no SSL inspection conflicts, and no impact on the end user. It just works alongside what we already have.

You don't want an old platform trying to adapt to a new problem. You want something that was built for this from the ground up, that grows with the technology rather than constantly playing catch-up.

The Implementation

Geordie was deployed across close to 2,000 machines at the firm, on every laptop and endpoint in the organisation, with no disruption to end users and no changes to existing infrastructure. The scheduled task architecture meant there was no persistent agent running on machines, and the absence of SSL inspection meant the existing network security stack continued to operate as designed.

The first meaningful finding came almost immediately. During the initial deployment, Geordie surfaced the extent to which developers were using alternative AI providers and sub-models inside their development environments, which is activity the security team had no prior visibility into.

The implementation also established a new AI approval workflow. Rather than reviewing individual agents,which would quickly become unmanageable at scale, the team built a platform-level approval process. For each new AI platform under consideration, the security engineer would review the activity with Geordie, including the prompts, risk flags and connection data, then produce a documented assessment for the CISO and the firm's AI working group.

We knew developers were using AI tools in their IDEs, but we didn't know the full picture. Geordie showed us exactly which models were being invoked and by how many people. It wasn't a security incident,but it was a genuine surprise, and exactly the kind of thing we needed to see.

I go through the platform in Geordie, look at the chats, the prompts, any risk indicators that surface, and I give a clear assessment to my team. Everyone can see that someone has looked at it properly, that we have visibility, and that we're accepting informed risk rather than flying blind.

The Results

Estate Coverage

Close to 2,000 machines instrumented with Geordie, covering the full endpoint estate across the organization.

AI Agent Platforms Approved

Each major platform required its own risk review and sub-product approvals

Shadow Agent Discovery

Immediate and unexpected visibility into developer AI usage inside IDEs

The firm's AI program moved from completely locked down to a running, approved suite of AI tools across the business, bringing what previously would have taken many months down to weeks.

Platforms approved since implementing Geordie:

Three major AI vendors approved, including the full Anthropic suite covering Claude, Claude Code and Claude Cowork, plus OpenAI and Microsoft Copilot,alongside several additional platforms including Azure DevOps, Power Automate and Foundry. Each major platform required its own risk review and sub-product approvals, representing a significant volume of AI governance work completed in a highly compressed timeframe.

Estate coverage:

Close to 2,000 machines instrumented with Geordie, covering the full endpoint estate across the organization.

Discovery:

Immediate and unexpected visibility into developer AI usage inside IDEs, surfacing sub-model and alternative provider usage across the development environment that the security team had no prior insight into.

Speed of approvals:

Go-to-market time for new AI products moved from months to weeks. The Anthropic Compliance API integration that unlocked the full Claude suite enterprise agreement was delivered in four days.

Competitive advantage:

The security engineer articulated the business value of the speed gain directly in competitive terms.

Development productivity:

Coding agents are already compressing development timelines across engineering teams. The return is cumulative rather than singular.

Audit trail and executive confidence:

The most significant operational benefit has been the ability to provide documented evidence of oversight to leadership, enabling approvals that previously had no pathway at all.

The Agent Perspective Is What Matters for Risk

As the firm's AI program has matured and the volume of agent activity across the environment has grown, one conviction has become central to how the security team thinks about risk: the only view that actually tells you what is happening is the view from the agent itself.

The security engineer is clear that this is not a theoretical concern. In practice, the most common source of agent risk is not malicious intent,it is well-intentioned users who are comfortable with the end result and unaware of what the agent did to produce it.

This is the lens through which the firm evaluates every new AI deployment and every new security requirement. Not whether a tool can be blocked at the boundary, but whether the security team can see what the agent is doing once it is inside in terms of how it reasons, what it connects to, how context flows across the workflow and when behaviour moves outside what was originally intended.

"The agent is the unit of risk. Everything else is context. If you're not starting from the agent and working outward from there, you're looking at the wrong thing."

For a firm operating in financial services,where client data, investment information and regulatory obligations are at stake in every workflow, that perspective is not optional. It is the foundation on which every AI approval, every compliance assessment and every executive conversation is built.

The risk isn't the model and it isn't the prompt. It's the agent acting on behalf of a user who isn't watching every step. You give someone a powerful AI tool and they check the output. They're not watching the process. The agent could be doing anything in between, and that's exactly where the security problem lives.

Someone builds a perfectly reasonable workflow, runs it every day, checks that the output looks right, and has no idea that their agent has been quietly doing something they never intended. You can't see that from the network layer. You can't see it from the identity layer. You can only see it if you're watching the agent, from the Geordie perspective.

The Team Behind the Technology

Ask the security engineer what has made the Geordie relationship work and the answer is consistent: the team.

In fifteen years of enterprise security work, he had never described a vendor relationship as a genuine partnership. Most of the time, feedback goes in and nothing comes back. Feature requests are acknowledged and forgotten. Account teams cycle through and institutional knowledge disappears. The relationship with Geordie has been different from the start, and that difference has had a direct impact on what the firm has been able to accomplish.

"I've been in IT for fifteen years and I've never been excited about a vendor. Geordie changed that. It's the combination of people, the way they show up, the fact that they actually listen. It just feels completely different from every other vendor relationship I've had."

Summary of Benefits

This global private equity firm came to Geordie with a clear mandate, to enable AI adoption safely in one of the world's most heavily regulated industries,and no existing tool that could help them do it. In a matter of weeks, Geordie delivered the visibility, audit trail and compliance evidence needed to move from complete AI lockdown to a running, approved AI program covering major vendors and close to 2,000 machines.

The competitive advantage is real and measurable. While other firms in the private equity space are still holding back on AI adoption because they cannot see what their agents are doing, this firm is already running approved coding agents, productivity tools and automation workflows across the business, which compresses development timelines, accelerates go-to-market on AI capabilities and gives leadership the confidence to keep moving forward.

At the heart of it is a simple but powerful insight: the only view of AI risk that actually tells you what is happening is the view from the agent itself. Not the model. Not the network. The agent, in terms of how it reasons, what it connects to, how context flows through its decisions and when behaviour moves outside what was intended. That is the view Geordie provides. And in a market moving as fast as this one, it is the view that makes the difference between saying yes to AI and staying locked down.

"Geordie didn't just give us visibility. It gave us the ability to move. And in this market, the firms that can move on AI first are the ones that win."

Other firms in our space are not enabling AI because they can't see it, which means their developers aren't using it and their go-to-market on new AI capabilities is months behind. Geordie changed that calculation for us. Our approval timeline went from months to weeks. That's a real competitive edge in this market.

The time savings of using AI agents aren't one big shift. It's two days off a project across a hundred people. That's 200 days of saved time and it compounds every single week.

Before Geordie, I couldn't give my leadership team anything concrete. Now I can walk in and say here's what we can see, here are the risks we've identified, here's how we've addressed them, and here's why I'm comfortable giving this the green light. That's a completely different conversation.

Footer graphic with abstract geometric patterns and gradients