Blog

C1's Field CISO on the ADAPT phase — the one honest executive meeting that starts an agentic AI program, the failure graveyard worth naming out loud, the permanent tension between control and reuse, and the four written outputs including kill criteria for the program itself.

SAML vs OAuth: how each protocol works, where SAML 2.0 and OAuth 2.0 fit, and how to choose the right one for SSO, APIs, and AI agents.

C1's Field CISO on the five-rung agentic AI maturity ladder — shadow AI, tracked AI, governed AI, federated reuse, and compounding — plus the four diagnostic questions that tell you which rung you are actually on.

AI agents broke the unwritten assumption behind zero trust: that a human with judgment sits behind every credential. Why authorization has to move to the moment of action.

Learn how the MCP authorization spec uses OAuth 2.1 to control what AI agents can access, and where identity governance closes the gaps it leaves open.

Gateway proxy or standards-based token exchange? The two credible models for authorizing AI agents at runtime have complementary strengths, and no enterprise environment is uniform enough for one to cover everything. Why the right question is whether your platform supports both.

C1's Field CISO on the seven failure patterns that kill enterprise AI programs — shadow tool sprawl, SSO mistaken for authorization, shared service accounts, policy nobody reads, and the review board reborn as an AI Council — and how to convert a gating function into an enabling one.

A recap of C1 Launch Week: shadow AI discovery, Agentic Vault, agent runtime governance, and agentic security and intelligence. Four launches, one control plane for governing every AI agent, secret, and non-human identity.

C1's agentic security and intelligence detects identity risk across people, service accounts, workloads, and AI agents, then routes every finding through governed remediation or the tools your team already uses.