Skip to main content

The Account Nobody Owns - AI Security Briefing #4

  • Nov 18, 2026 10:09 PM UTC
  • 0 replies
  • 1 view

Forum|alt.badge.img+3

Here’s a quick summary of the key points from our second live virtual security briefing. Sign up for upcoming sessions in the series here, and find the full recordings from all sessions here.

 

Briefing Recap

The problem

Machine identities already outnumber people 82 to 1 in the typical enterprise, and 78% of organizations have no documented policy for creating or removing AI identities.

Three kinds of accounts carry real privilege and answer to nobody:

  • A local admin account: five people know the password, and the log names the account, not the person.
  • A service account: created for a project years ago, never rotated, its creator long gone.
  • An AI agent: running all night on a developer's token or an unreviewed OAuth grant, with nobody who decided when it should stop. 

Ownership is two different questions: 

  1. Attribution asks who acted, and on whose behalf, answered per action.
  2. Sponsorship asks who decided this identity should exist and hold this much access, answered once for its whole life: who approves it, justifies its scope, and retires it when the time comes.

Most programs answer the first question and never ask the second, which is why service accounts almost never get retired: nobody wants to own the outage. 

Where each one actually breaks: 

  • A local admin account’s problem is attribution. The log names “Administrator,” not a person, so even perfect vaulting won't tell you who did what. 
  • A service account’s problem is sponsorship. Nobody re-approves its scope once its creator leaves, so it only ever grows, and nobody wants to be the one who retires it. 
  • An AI agent’s problem is both. It runs on someone else's credential, which breaks attribution, and nobody decided it should exist or when it should stop, which breaks sponsorship too. 

 

Where to start 

Start in this order. First, inventory every local admin, service, and agent identity, and assign a sponsor: no owner, no access. Second, vault and rotate every credential, and make every local admin password unique per host. Third, stop the sharing, check-out with rotate-on-return now, brokered access next. Fourth, retire the secret entirely where you can. 

Sources: Delinea Identity Security Report, Spring Edition 2026, Microsoft State of Multicloud Security Risk Report (via Delinea blog); Cloud Security Alliance research note on NIST IR 8587 (Sept 2026); Delinea blog, discovery and service account governance onboarding.