
Ideas that shape the future of identity
Expert perspectives on identity security, AI agent authorization, zero-trust patterns, and the infrastructure powering autonomous systems.

Showing 9 of 10 articles

We Built a Firewall for AI Agents. Here's What Happened When Claude Code Tried to Delete Our Files.
You give Claude Code your terminal. You give Codex your codebase. You give OpenClaw your entire machine — and they can rm -rf your home directory or git push --force to production before you know it. AuthSec Agent Shield stops that at the OS level. Here's what happened when we put it head-to-head with Claude Code.

AuthSec for AI: Your Organization's Kill Switch for AI Agent Actions
AI agents can delete files, push code, query databases, scale infrastructure, and send customer emails with a single prompt. AuthSec adds a human approval layer before risky actions execute.

Building an Authenticated AI Gateway: How We Put OpenClaw Behind Enterprise SSO
AI assistants are powerful, but deploying one inside an organization without authentication is like leaving the front door wide open. Here's how we built authsec-openclaw — a Go reverse proxy that wraps OpenClaw with enterprise-grade SSO and gives every chat session a verified identity.

SCIM: The Enterprise Gateway Your AuthSec Deployment Needs
Enterprise customers won't buy your SaaS if they have to manually provision users. Every new hire means a ticket. Every termination means a security gap. AuthSec SCIM fixes this by automating user sync from Okta, Entra ID, and Google Workspace.

AuthSec: Open-Source Identity for AI Agents
Most identity products were designed around a very specific assumption—there's a human sitting in front of a browser. That model breaks down fast once you start shipping agents. AuthSec was built to fix that.

Why AuthSec Is Built for Agents, Not Browsers
Most identity products were designed around a specific assumption: there's a human sitting in front of a browser. That model works well for web apps but breaks down fast once you start shipping agents.

MCP server: The Protocol Your Service Mesh Has Been Missing
Every component in your service mesh watches the same Kubernetes API. This creates a thundering herd problem at scale. MCP is the distributed configuration layer that solves this.

The Cryptographic Identity Your Infrastructure Is Missing
Microservices don't have passports—they have IP addresses and shared secrets. This falls apart at scale. SPIFFE/SPIRE gives every verified workload a cryptographic identity.

The Authentication Problem Nobody Told You About
Your AI agent can't click a login button. Yet every identity platform assumes that's exactly what will happen. AuthSec fixes this.
Stay in the loop
Get the latest articles on identity security and AI authorization delivered to your inbox.