Service account management means keeping a living inventory of every non-human login in your company, giving each one a named owner and a documented purpose, limiting what it can do, and reviewing it on a schedule. If you do only four things, do those: inventory, owner, least privilege, quarterly review. The rest of this guide shows how to do them without an enterprise identity team.
It is written for operations and IT managers at small and midsized companies, where service accounts tend to pile up in someone’s head or in a spreadsheet nobody has opened since the person who created them left.
Table of Contents
What a service account is, and why it gets neglected
A service account is an identity used by an application, script, integration or scheduled job rather than by a person. Think of the account your backup tool uses to read file storage, the login a billing integration uses to talk to your accounting system, or the credential a deployment script uses in your cloud provider.
Three things make them risky in a small company:
They often run without a person watching. Review service activity and alerts so unexpected use is noticed.
They are often over-permissioned. Someone granted broad rights to get an integration working at 5 p.m. on a Friday, and the rights stayed.
They outlive their creators. The employee who set one up changes roles or leaves, and the account becomes an orphan.
Each service identity needs an accountable owner or team and a documented purpose. Review identities throughout their lifecycle, from creation through access review and retirement.
Step 1: Build the inventory
You cannot govern what you cannot see. Start with a single register, one row per service account. Discovery usually means checking four places:
Your identity provider and directory. Filter for accounts that never receive a person’s email, have names like
svc-orbackup, or have passwords set to never expire.Cloud consoles. Service accounts, service principals, API keys and access tokens in each cloud and SaaS admin panel.
Integrations. Every connected app in your accounting, CRM, HR and ticketing tools usually runs under some account or token.
Scripts and scheduled jobs. Ask whoever has ever written automation. Check cron jobs, task schedulers and CI/CD settings.
What each record should hold
CIS Control 5 asks for an inventory that, at minimum, includes the department owner, the review date and the purpose of every account. Its guidance also treats the inventory as stale if the last review is more than three months old. A practical register looks like this:
| Field | Example | Why it matters |
|---|---|---|
| Account name and system | svc-backup, file storage |
Findability |
| Purpose | Nightly backup of shared drive | Lets a reviewer judge whether access is still needed |
| Owner (a person) and backup owner | Operations lead, IT manager | Accountability when the owner leaves |
| Permissions granted | Read-only on one share | Basis for the least-privilege check |
| Credential type and rotation date | Password, rotated 2026-09-01 | Shows credential age |
| Last review date | 2026-10-15 | Proves the review happened |
| Last used | 2026-10-21 | Finds dormant accounts |
| Shared with interactive use? | No | Flags a policy violation |
If a spreadsheet is where you start, fine. The IDPro paper is blunt that manual spreadsheets are where this goes wrong at scale, because they drift away from what is actually running. The fix is to reconcile the register against your systems on a schedule and keep it in the same place you track your other people, device and access records.
Step 2: Assign an owner to every account
An owner is a named person, not a shared mailbox and not “IT.” The owner answers three questions on request: why does this account exist, what does it need, and can it be switched off?
Tie ownership to your people processes:
Offboarding: when someone leaves, the checklist includes “list service accounts you own and reassign them.” NIST’s account management control (AC-2) asks organizations to align account management with personnel termination and transfer.
Role changes: the same check when someone moves teams.
Creation: no account is created without an owner and purpose filled in. A request with a blank owner field is not approved.
If you already run offboarding as a checklist, adding this line costs nothing. Our guide to user provisioning automation covers how to run the people side of this reliably.
Step 3: Apply least privilege and one account per job
Most service account compromises become serious because of excess permission. Security practitioners at Specops stress that these accounts are prime targets because they are often highly privileged and lack MFA, and that granting something like Domain Admin to a service account can give an attacker persistent control of the whole domain.
Rules that hold up in practice:
Grant the narrowest permission that works. Specops recommends applying very granular permissions to the specific resources needed instead of risky group memberships.
One account per service. Sharing an identity across unrelated jobs can broaden the damage from a compromise and make activity harder to attribute.
No interactive logins. If a human signs in with the account, it is a user account in disguise. Block interactive logon where your platform allows it.
Group them. In Active Directory, a dedicated organizational unit for service accounts makes it much simpler to apply policies consistently.
Review the permissions granted to every integration separately from employee sign in. Authentication, application access and account provisioning are different functions, and each needs its own access review.
Prefer managed identities where you can
In supported Windows environments, group Managed Service Accounts automate password management and can be used by services on multiple servers. Check application compatibility and permissions before adopting them. Microsoft Entra workloads should use managed identities or service principals where supported, rather than ordinary employee accounts.
Step 4: Rotate and shorten credentials
Long lived credentials increase the time an exposed secret can be misused. Where managed identities are unavailable, store secrets in a secrets manager, define a rotation schedule suited to the service, and replace credentials promptly after suspected exposure. Test dependent applications during rotation.
For cloud workloads, the better answer is to avoid long-lived keys altogether. Google’s engineering team describes workload identity as a way to authenticate without static service account keys, which shrinks the damage if a credential is exposed.
For Google Cloud, removing a service account key does not invalidate access tokens already issued. Follow Google’s compromised credential response guidance: block the affected identity, replace exposed keys and remove unauthorized impersonation rights. Before restoring the account, allow outstanding tokens to expire. The usual lifetime is up to 60 minutes, but an extended lifetime policy can allow up to 12 hours. Account disablement can interrupt dependent workloads.
Step 5: Review on a schedule and retire what is dormant
This is where most programs quietly die. Set two recurring jobs.
Quarterly access review. CIS recommends reviewing service accounts at least quarterly to confirm they remain authorized. At each review, the owner confirms purpose, permissions and credential age, and the reviewer signs off. Anything the owner cannot justify gets disabled. This is the same exercise as a privileged access review for people, with a few extra columns.

Dormancy sweep. CIS Controls v8.1 Safeguard 5.3 calls for disabling or deleting dormant accounts after 45 days where supported. For service identities, check scheduled workloads and business dependencies before taking action. A quarterly or annual job may be legitimate even if it has not run recently. Document approved exceptions. Disabling first allows a reversible check; retain logs separately under your retention policy.
A simple review calendar
| Cadence | Task | Who |
|---|---|---|
| Every creation | Owner, purpose and permissions recorded before approval | Requester and IT |
| Monthly | Check last-used dates, disable accounts past your dormancy threshold | IT manager |
| Quarterly | Full owner attestation and permission review | Account owners, ops lead |
| At every departure | Reassign accounts owned by the leaver | HR and IT |
| Per rotation policy | Rotate passwords and keys | Account owner |
Recurring work like this is easy to promise and easy to forget. Our recurring task management audit shows how to make sure the reviews are scheduled, assigned and visibly done.
Writing a service account policy that people follow
A policy for a small company fits on one page. Include:
Definition and scope: what counts as a service account, including API keys and integration tokens.
Creation rule: an owner, a backup owner and a documented purpose before approval.
Permission rule: least privilege, one account per service, no interactive logon, no shared use.
Credential rule: managed identities first, otherwise stored in a secrets manager and rotated on a set schedule.
Review rule: quarterly owner review, plus a documented dormancy threshold and approved exceptions for infrequent workloads.
Exit rule: accounts are disabled first, deleted later, and every change is logged.
NIST’s AC-2 control covers the same ground: define the account types allowed, assign account managers, and review accounts for compliance. If you answer to auditors or customers who ask for evidence, a policy plus dated review records is what they usually want to see.
Common mistakes to avoid
Using a former employee’s personal account as the service account. It breaks when they are offboarded, and it hides the real owner.
Granting admin “temporarily.” Add a removal date to the ticket or the task, or it will not happen.
Treating SaaS integrations as out of scope. Connected apps hold tokens that behave like service accounts.
Deleting before checking dependencies. Disable first where practical, confirm dependent services still work, and preserve the required logs before deletion.
Running the review only once. The first inventory is a snapshot. The value comes from repeating it.
Our perspective: ownership beats tooling
We build CentriOps to help small and midsized companies keep people, device, application and operations records together. Clear ownership and a documented review process make it easier to follow up on work that would otherwise sit in separate tools.

Service accounts connect technical work to people processes. Record their owners in an appropriate account register, include ownership checks in offboarding, and assign review work to a named person. These steps complement the security controls in your identity and cloud platforms.
To be clear about scope, CentriOps is an operations platform, not a secrets vault or a privileged access management product. Keep credentials in a proper secrets manager. Use the operations layer to hold the process around them: who owns what, what access was granted, what has been reviewed and what has to happen when someone leaves.
— CentriOps Team
Keep the process in one place with CentriOps
CentriOps helps teams maintain People, Devices and Apps records and coordinate Requests, Tasks and Checklists. Use it to assign review work and document completion. Administrators manage Contracts & Subscriptions and the searchable Audit Trail on Team and Business; activity logs in included modules are available on every plan. Google and Microsoft sign in are supported. Account discovery, permission changes, credential rotation and access removal happen in your identity, cloud or application admin tools. See the features and pricing pages for current plan details.
If you are also tightening the way people get and lose access, our software access management playbook is the companion read.
FAQ
What is the difference between a service account and a user account?
A user account belongs to a person and is used for interactive sign-in. A service account belongs to an application, script or process and authenticates automatically. Because nobody watches it sign in, it needs an explicit owner and regular review.
How often should service accounts be reviewed?
At least quarterly. CIS Control 5 treats an inventory as out of date when the last review is older than three months. Add a monthly check of last-used dates to catch dormant accounts sooner.
Should I delete unused service accounts?
Disable unused service accounts first where the platform supports it, after checking with the owner and reviewing dependencies. Delete after your approved holding period. Preserve the logs and review evidence your retention policy requires; disabling an account alone does not guarantee log retention.
What is a group Managed Service Account?
A group Managed Service Account is an Active Directory identity with automatic password management that can support services on multiple servers. It reduces manual password handling, but application compatibility and correct permissions still need to be checked.
Sources
Non-Human Identity Management: Designing and Governing Machine Actors, IDPro
Non-Human Identities: The Next Big Challenge for Organizations, ISACA
10 security best practices for Active Directory service accounts, Specops
Best practices for mitigating gcloud OAuth token risk, Google Cloud