Contact Open demo
Solutions / By identity

Service accounts

Agents borrow service accounts built for something else, and inherit every permission the account ever collected. nerl0 shows which ones they reuse and what those accounts open.

One key, three callers

A service account was made for one job. Then a script used it, then an agent. The account never changed, but who it works for did.

Who uses the key. CI pipelinedeploy.ymlNightly scriptsync.shAI agentcoding agent, uses the same key svc-deployBuilt for one job Read all repositoriesDeploy to productionWrite storage bucketsRead the secrets managerManage the database

Why a service account turns risky

It takes three habits that look harmless one at a time.

Read the Academy
01
It is shared

One account was created for a pipeline. A script borrowed it, then an agent. Now nobody can say who actually used a call.

02
Its key is old

The key was made once and never rotated. Everyone who ever saw it can still use it, and it works from anywhere.

03
Its role is wide

Each new job added a permission and none was removed. The account holds the union of everything it was ever used for.

See every account an agent reuses

nerl0 reads service accounts from your cloud and identity platforms, and marks the ones an AI agent has been seen using. You see who shares a key, how old it is and what it reaches.

  • SharedAccounts used by more than one caller, with the agent called out.
  • AgingKeys that have never been rotated, sorted to the top.
  • ReachingThe crown-jewel data each account can get to.
IdentitiesService accountsUsed by agents
AccountUsed byKeyReaches
svc-deployPipelineScriptAgentNever rotated2 crown jewels
svc-reportingScriptRotated1 crown jewel
svc-syncPipelineAgentNever rotated1 crown jewel
svc-backupScriptRotatedNo crown jewel
svc-ci-buildPipelineRotatedNo crown jewel
AI agentcoding agentsvc-deployservice account deploy-adminrolestorage-writerrolesecrets-readerrole Prod DBcrown jewel Backupsbucket API keyscrown jewel Breakpoint

Follow the account to the data

The account itself is not the problem. The path is: an agent holds the key, the key assumes a role, and the role reaches data nobody meant the agent to touch. nerl0 draws that path and marks the one hand-over to cut.

  • Authority pathEvery step is a configured relationship, not a guess.
  • BreakpointThe single change that closes the most paths.
  • ProvenThe next scan checks that the path is gone.

Give each caller its own identity

The fix is not a new tool. It is splitting one account into narrow ones, each with an owner.

BeforeOne account, everything it ever collected
PipelineScriptAI agent svc-deployone shared key ReposDeploy prodBucketsSecretsDatabase
AfterOne identity per caller, only what it needs
PipelineScriptAI agent ci-deployown key, own ownersync-readerown key, own owneragent-codeown key, own owner Deploy prodRead storageRead repos

Rotate, assign, verify

Narrowing an account is a small change with a clear owner. nerl0 turns it into an issue, and the next scan shows whether it held.

  • Assign an ownerEvery service account gets a person who answers for it.
  • Rotate the keyOld keys are rotated or retired, not left to age.
  • Check on the next scanThe path is gone, or the issue stays open.

Activity

Every event on this issue's paths, one lane per entity · newest first
ops-automation-agentDecisionDev Patel assigned an issue on ops-automation-agent
ops-automation-agentDecisionDev Patel opened an issue on ops-automation-agent
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent read prod/payments/stripe-key
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
nerl0Reproduced
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts

Questions to ask

These come straight from the Question Library. Activate them in your own workspace.

Browse all questions

More solutions

Other ways into the same map of authority.

Browse the Academy

See which accounts your agents reuse.