Cookie settings

Necessary, always on: they keep the site working and remember your cookie choice.

Skip to content
Skip to content

Blog. Access governance.

Service accounts are the identities access reviews miss

Dipal Panchal

Co-founder and CEO · November 6, 2026 · 4 min read

On this page

Access reviews are built around people. Someone joins, changes teams or leaves, and each event prompts a check. A service account never joins, moves or leaves. It is created when a system needs it and stays until someone remembers to remove it, so it is the identity an access review is most likely to miss.

The people process never reaches them

The IDPro Body of Knowledge is a reference for identity and access management practitioners. Its article on non-human accounts says auditors often overlook the accounts automated processes use, because users do not sign in to them interactively.

Its article on privileged access management adds the lifecycle point. Non-human accounts are not managed through joiner, mover and leaver processes. A change management process triggers their lifecycle events instead. The last step, removing access when a component is decommissioned, is one the article says practitioners often forget.

A retired job leaves its account behind

In a constructed example, a nightly job copies customer records from the production database into a reporting store. It signs in as svc_export, an account created for the job with read rights on the whole customer schema.

Two years later the reporting store is replaced and the job is switched off. Nobody removes svc_export. Its password still sits in an old configuration file, and it can still read every customer table. No person’s access review would show it, because nobody joined, moved or left. The job ended, and the access stayed.

A list of non-human access is the first control

The account management checks in NIST SP 800-53A apply to service accounts as much as to people. Account types are “defined and documented,” account managers are assigned and accounts are reviewed. For service accounts, that starts with a list.

Records
AccountPurposeAccountable ownerReachLast usedDecision
svc_exportNightly export to the old reporting storeHead of data platformRead on the whole customer schemaTwo years agoRevoke; rotate the exposed secret
svc_billing_syncSyncs invoices to the finance systemFinance systems leadRead and write on three billing tablesLast nightKeep; downgrade write to the one table it updates
svc_backupDatabase backupsInfrastructure managerRead on all databasesLast nightKeep; time-limit and review each quarter
svc_report_appReporting application reads on behalf of analystsHead of customer analyticsRead on the customer schema, including national ID numbersTodayDowngrade to the reporting views
svc_legacy_crmUnknownNot foundNot available: the source does not expose permissionsNot availableExcluded from the list; owner search opened

The columns carry the questions an owner must answer: what the account is for, who is accountable, what sensitive data it can read or change, how it signs in and when its secret last changed. IDPro’s account management guidance puts the first of these plainly: “Assign an account owner to be accountable for the use of the account.”

The owner of the job reviews the account

A manager can’t certify a service account the way they certify a team member. The right reviewer is whoever is accountable for the job the account does. For scripts, macros and automation, IDPro’s privileged access article names the change requester or requirements owner as the accountable party.

For each account, the owner answers five questions.

  • Does the job still run? If not, why does the account exist?
  • Does it need write or admin rights, or only read?
  • Does it need the whole schema, or named tables?
  • Is anyone signing in with it by hand? That should not happen.
  • Who would notice if its secret leaked?

NIST’s Cybersecurity Framework 2.0 expects access permissions to be reviewed and to incorporate least privilege (PR.AA-05). A service account with schema-wide rights serving a job that reads one table fails that test, whoever approved it. NIST’s zero trust architecture, SP 800-207 section 5.7, adds a warning about software agents: they may meet a lower authentication bar, such as an API key where a person would need multi-factor authentication.

With IRIS

Where a source exposes permission data, IRIS maps who can reach sensitive datasets and flags excessive access, such as admin, owner or write rights and service accounts that can change those tables.

Where a source keeps an audit log, IRIS reads it and shows who accessed sensitive data and when, which answers the “last used” column.

Reviewers can keep, revoke, downgrade or time-limit a grant, with a reason; a second approver signs off each follow-up task. The change is made in the source system. Capabilities vary by edition.

See the access mapping page and access review with IRIS.

Tie removal to the change that retires the job

Retirement is the step that slips. A reporting job is switched off, a vendor integration ends or a migration finishes, and the account and its grants stay behind. Add an access-removal task to every change that retires a job, and record the date, who removed the access and who checked that it was gone.

Start this week with the accounts whose jobs you know ended. The database access review guide has the queries to list them, and the glossary entry on least privilege defines the standard each account is held to.

Sources

Share this article

Protect your brand. Start with your data.

Book a demo, or start with a free assessment of one database.