<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Identity on Thinx-Tank</title><link>https://blog.thinxai.net/tags/identity/</link><description>Recent content in Identity on Thinx-Tank</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 03 Nov 2026 07:22:00 -0600</lastBuildDate><atom:link href="https://blog.thinxai.net/tags/identity/index.xml" rel="self" type="application/rss+xml"/><item><title>Govern the Door, Not the Agent You Do Not Own</title><link>https://blog.thinxai.net/posts/govern-the-door/</link><pubDate>Tue, 03 Nov 2026 07:22:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/govern-the-door/</guid><description>&lt;p&gt;Most of my recent posts have been about agents inside the enterprise: the ones you buy, build, or approve. This one is about the agents you did none of those things for. They belong to your customers. You did not select them, you cannot patch them, and you will never see their release notes. They arrive at your portal with your customer&amp;rsquo;s password, and from your authentication logs they look exactly like your customer.&lt;/p&gt;</description></item><item><title>The Agent Wore a Contractor's Login</title><link>https://blog.thinxai.net/posts/agent-wore-a-contractors-login/</link><pubDate>Mon, 02 Nov 2026 07:20:00 -0600</pubDate><guid>https://blog.thinxai.net/posts/agent-wore-a-contractors-login/</guid><description>&lt;p&gt;On October 29, &lt;a href="https://www.cdomagazine.tech/us-federal-news-bureau/defense-contractor-gave-personal-ai-agent-access-to-pentagon-system"&gt;CDO Magazine summarized a WIRED investigation&lt;/a&gt; that every enterprise IT shop should read slowly. According to WIRED&amp;rsquo;s sources, an Accenture contractor connected a personal Claude Code account to a production system on NIPRNet, the Defense Department network for unclassified work. The system held controlled unclassified information and served multiple intelligence agencies. To get help writing code and standing up cloud servers, the contractor reportedly handed the agent his own login credentials.&lt;/p&gt;</description></item><item><title>Give the Agent a Role, Not Your Login</title><link>https://blog.thinxai.net/posts/give-the-agent-a-role/</link><pubDate>Sat, 31 Oct 2026 07:20:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/give-the-agent-a-role/</guid><description>&lt;p&gt;In &lt;a href="https://blog.thinxai.net/posts/browser-is-an-agent-surface/"&gt;yesterday&amp;rsquo;s post&lt;/a&gt; I worked through a design problem that Island&amp;rsquo;s governed browser exposed without naming. The agent does its work inside a person&amp;rsquo;s session, under that person&amp;rsquo;s identity, with that person&amp;rsquo;s full reach. The vendor can split the record afterward and show which actions the person took and which the agent took. That helps the investigation. It does not fix the grant. The agent still started the day holding everything the person holds.&lt;/p&gt;</description></item><item><title>The Browser Is an Agent Surface Now</title><link>https://blog.thinxai.net/posts/browser-is-an-agent-surface/</link><pubDate>Fri, 30 Oct 2026 07:21:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/browser-is-an-agent-surface/</guid><description>&lt;p&gt;Most enterprise work still happens in a browser. The CRM, the ERP, the HR system, the invoice queue: all of them are web applications behind a login form. An agent that cannot use a browser cannot do that work. An agent that can use a browser, on a consumer setup with saved passwords and a person&amp;rsquo;s full session, can do far more than that work.&lt;/p&gt;&#10;&lt;p&gt;Island made that problem a product category on October 29. In &lt;a href="https://www.globenewswire.com/news-release/2026/10/29/3391421/0/en/island-brings-the-enterprise-browser-to-ai-agents.html"&gt;Island&amp;rsquo;s announcement of its Enterprise Browser for Agents&lt;/a&gt;, the company describes a browser built for agents to access, read, and act on SaaS applications, internal applications, and public websites under the same enterprise controls and policies the company already applies to people. Sales agents update CRM records after calls. HR agents help onboard new hires. Finance agents process invoices. Island&amp;rsquo;s stated examples are ordinary back-office work, which is the point. The browser is not a side channel for agents. For a large share of enterprise tasks, it is the workplace.&lt;/p&gt;</description></item><item><title>Govern the Agents You Did Not Build</title><link>https://blog.thinxai.net/posts/govern-the-agents-you-did-not-build/</link><pubDate>Tue, 27 Oct 2026 07:21:00 -0500</pubDate><guid>https://blog.thinxai.net/posts/govern-the-agents-you-did-not-build/</guid><description>&lt;p&gt;IBM made the most honest admission in agent governance today, and it came inside a product announcement. At TechXchange 2026 in Atlanta, &lt;a href="https://www.morningstar.com/news/pr-newswire/20261027ny81742/ibm-introduces-identity-and-control-for-ai-agents-securing-frontier-intelligence-for-the-enterprise"&gt;IBM announced&lt;/a&gt; that watsonx Orchestrate will discover, contain, and evaluate agents built on other vendors&amp;rsquo; platforms, and that HashiCorp Vault will issue those agents governed identities and short-lived credentials. In &lt;a href="https://www.ibm.com/new/announcements/ibm-watsonx-orchestrate-advances-enterprise-ai-agent-management-with-new-capabilities-at-techxchange-2026"&gt;IBM&amp;rsquo;s own write-up&lt;/a&gt;, the pitch is explicit: manage agents &amp;ldquo;regardless of where those agents were built or run.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;That is the right problem. It is not the problem most control planes were built to solve. A control plane that only governs agents built on its own platform governs the demo estate, not the real one.&lt;/p&gt;</description></item><item><title>The Passport Is Not the Decision</title><link>https://blog.thinxai.net/posts/passport-is-not-the-decision/</link><pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/passport-is-not-the-decision/</guid><description>&lt;p&gt;On October 15, ServiceNow announced AI Passport in &lt;a href="https://www.hpcwire.com/bigdatawire/this-just-in/servicenow-unveils-ai-passport-to-control-ai-agent-permissions/"&gt;ServiceNow&amp;rsquo;s October 15 announcement&lt;/a&gt;. The idea is plain. Each agent and each Model Context Protocol server gets a cryptographically signed credential that states its authorized scope. Enforcement points check that credential at runtime, at each step of a multi-agent workflow. Inside scope, the agent works freely. Outside scope, the response can be graduated: redirect, restrict, reconnect with proper context, or terminate with a kill switch at machine speed.&lt;/p&gt;</description></item><item><title>There Is No Device to Enroll</title><link>https://blog.thinxai.net/posts/bring-your-own-agent/</link><pubDate>Thu, 15 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/bring-your-own-agent/</guid><description>&lt;p&gt;On October 12, &lt;a href="https://thehackernews.com/2026/10/bring-your-own-agent-your-employees.html"&gt;The Hacker News published a contributed piece from Token Security&lt;/a&gt; with a plain title: bring your own agent. Employees are connecting personal AI assistants to work systems, and the assistants are already logged in. Not pasting text into a chatbot. Acting, with permission, inside email, calendars, file stores, and code repositories.&lt;/p&gt;&#10;&lt;p&gt;I have spent a month writing about agents the enterprise deploys on purpose. This is the other fleet. Nobody procured it, nobody provisioned it, and in most tenants nobody can list it.&lt;/p&gt;</description></item><item><title>Delegation Is Not Inheritance</title><link>https://blog.thinxai.net/posts/delegation-is-not-inheritance/</link><pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/delegation-is-not-inheritance/</guid><description>&lt;p&gt;On October 8, at Gemini at Work 2026, Google introduced a single Gemini agent for work. Most of the coverage went to the front door: one agent across Workspace, Microsoft 365, and Slack, with persistent coworker agents that hold their own email address, storage, and Workspace account. The line I keep coming back to is smaller. Per &lt;a href="https://futurumgroup.com/insights/google-collapses-enterprise-ai-into-a-single-gemini-agent-at-gemini-at-work-2026/"&gt;Futurum&amp;rsquo;s report on the announcement&lt;/a&gt;, the agent &amp;ldquo;spins up temporary sub-agents for individual jobs.&amp;rdquo;&lt;/p&gt;</description></item><item><title>Your Newest Coworker Has an Email Address</title><link>https://blog.thinxai.net/posts/your-newest-coworker-has-an-email-address/</link><pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/your-newest-coworker-has-an-email-address/</guid><description>&lt;p&gt;On October 8, Google Cloud announced a universal &lt;a href="https://www.pymnts.com/news/artificial-intelligence/2026/google-cloud-targets-enterprise-market-with-universal-agent-work/"&gt;Gemini agent for work&lt;/a&gt;, adapted from CEO Thomas Kurian&amp;rsquo;s keynote at Gemini at Work 2026. The agent answers questions, writes and runs code, and works inside Gmail, Drive, Docs, Slides, Sheets, Chat, and Calendar, from any device and any channel, carrying the same memory, skills, and controls with it everywhere. Industry-specific agents for financial services and legal are already in preview; government, healthcare, and retail are coming. The release note is explicit: it learns from each interaction with the user.&lt;/p&gt;</description></item><item><title>Standing Privilege Is Dead</title><link>https://blog.thinxai.net/posts/standing-privilege-is-dead/</link><pubDate>Wed, 07 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/standing-privilege-is-dead/</guid><description>&lt;p&gt;&amp;ldquo;Standing privilege is dead.&amp;rdquo; That is SailPoint CTO Chandra Gnanasambandam, speaking at the company&amp;rsquo;s Navigate 2026 conference in Austin yesterday. The occasion was a launch called Zero Standing Privilege: just-in-time provisioning, with conditions, replacing always-on access for people, service accounts, and AI agents alike. (&lt;a href="https://www.sailpoint.com/press-releases/sailpoint-unlocks-a-secure-agentic-era-with-autonomous-identity-security"&gt;SailPoint press release&lt;/a&gt;)&lt;/p&gt;&#10;&lt;p&gt;The stat behind the launch comes from SailPoint&amp;rsquo;s Horizons of Identity Security report: 79% of enterprises already run AI agents in production, but only 2% have deployed identity security tools built to govern them. Sit with those two numbers for a moment. Four out of five enterprises have a production agent fleet. One in fifty has the tooling to govern what the fleet touches. The gap between the fleet and the governance is the whole problem in one number.&lt;/p&gt;</description></item><item><title>Every Agent Needs an Identity</title><link>https://blog.thinxai.net/posts/every-agent-needs-an-identity/</link><pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate><guid>https://blog.thinxai.net/posts/every-agent-needs-an-identity/</guid><description>&lt;p&gt;On September 9, 2026, SpyCloud released its annual Identity Threat Report, and the headline finding should make every CIO put down their coffee: non-human identities (NHIs) are now the most common route attackers take into the enterprise. Compromised NHIs were named the primary entry point by 31% of respondents, nearly twice phishing and social engineering at 17%. NHI-related misuse was also the most commonly reported identity-based event type, at 42%. (&lt;a href="https://spycloud.com/newsroom/spycloud-2026-identity-threat-report-finds-non-human-identities/"&gt;SpyCloud press release&lt;/a&gt;)&lt;/p&gt;</description></item></channel></rss>