A few months ago, ServiceNow's acquisition of Veza sent a clear signal: identity is becoming foundational to the enterprise platform. We said so at the time, and we still believe it.
What's changed since is that the picture has come into focus. The early question was "what does this mean?" Now there's enough on the table to answer a more useful one: where does each piece of identity actually fit?
Because the acquisition didn't just validate that identity matters. It clarified something subtler — that "identity" is really two different jobs, and they don't get solved the same way.
The first job is understanding access at scale. Which identities — human, machine, and increasingly AI agents — can reach what, what they can do with it, and how those relationships shift as systems and agents multiply. This is the mapping-and-analysis layer: continuous visibility into permissions across a sprawling environment.
It's where ServiceNow and Veza have pointed their energy, and for good reason. As enterprises deploy AI agents that act on behalf of employees, governing non-human identity at scale becomes urgent. Veza operates as its own platform that integrates with ServiceNow, feeding that access intelligence into the broader system — a strong fit for the "AI control tower" ambition of governing every agent, model, and identity.
That's real, and it's valuable. But it's one job.
The second job is operating the workforce identity lifecycle — the day-to-day machinery that touches nearly every employee and application: access requests, certifications and reviews, joiner/mover/leaver lifecycle, separation of duties, and audit evidence.
This isn't about mapping access; it's about running it. And it's relentlessly operational — approvals, workflows, exceptions, evidence — the unglamorous work that keeps an organization both productive and compliant.
Access intelligence tells you what's true about access. Human IGA is how the work of granting, reviewing, and revoking it actually gets done. A map of the terrain is not the same as the vehicle that drives it.
Here's where the two jobs meet. Human IGA works best when it runs natively inside the platform your organization already lives in.
Access decisions are never isolated. They connect to employee lifecycle events, service catalog requests, security policy, and compliance workflows. When identity governance operates directly on ServiceNow — the same data model, the same workflow engine, the same interface people already use — you get workflow continuity that disconnected tools struggle to match. And you get something just as important: adoption. In identity, adoption is a security control. A process people actually follow protects you better than a more sophisticated one they route around.
More than a decade ago, Clear Skye set out to build human IGA natively on ServiceNow — not an external tool bolted on through integrations, but governance operating directly inside the workflows organizations already rely on.
That's the job we do, and it's a different job from access intelligence. The two are complementary, not competing. As the intelligence layer grows — mapping human, machine, and AI identity across the enterprise — the operational human layer still has to run somewhere. We believe it should run where the work happens: on the platform.
The Veza acquisition confirmed that identity belongs at the center of the enterprise platform. Months in, it's also clarified how identity divides: intelligence and operations, non-human and human, mapping and running.
Both jobs are getting more important, and both are converging on the platforms where work actually happens. Clear Skye runs the human IGA job there today — natively on ServiceNow. And we're glad to see the rest of identity moving in the same direction.
