Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Service accounts run applications and scheduled tasks. They are over-privileged, rarely rotated, exempt from multi-factor authentication, and owned by nobody in particular.

What Is Service Account Security?
Ask who owns svc-backup-sql and the answer is usually a pause. It was created during a migration, it has had Domain Admin since because that was what made the job work, its password was set in 2019 and documented in a runbook, and the engineer who configured it left in 2022. It is also excluded from multi-factor authentication, because it is not a person.
That combination—standing privilege, a static credential, no second factor, and no owner—is why service accounts appear in so many intrusion reports. They are the quietest way to hold access in a domain.
A human account has a person behind it who notices an unexpected prompt, a password reset they did not request, or a sign-in from another country. A service account has nobody. It authenticates from predictable infrastructure at predictable times, so the usual behavioural signals are weak, and the account cannot be improved by awareness training.
Worse, service accounts resist the controls that work elsewhere. Multi-factor authentication does not apply. Conditional access policies that require a compliant device usually have to exempt them. Password rotation breaks the application unless the change is coordinated, so it does not happen. Each of those is a reasonable operational decision, and together they produce an account that is easier to use than any human one.
You cannot secure what you have not listed, and service accounts are deliberately inconspicuous. Look in several places: directory accounts with a service principal name, accounts with password-never-expires set, accounts in an organisational unit named after an application, the identities configured in Windows services and scheduled tasks across the estate, database logins, and the application identities registered in your cloud tenant.
Record for each one: what runs under it, which systems it reaches, what privileges it holds, when the credential last changed, and—most importantly—a named owning team. An account with no identifiable owner should be a candidate for disablement rather than indefinite renewal, and disabling it in a controlled window is a far better way to discover what it does than reading documentation that does not exist.
Service accounts are predictable, and predictability is the detection opportunity. Baseline where each one authenticates from, what it accesses, and when. Then alert on departures from that baseline: authentication from a new host, access to a system outside its normal set, activity outside its scheduled window, interactive logon, and group membership changes. These are high-signal because the legitimate behaviour is so repetitive.
Finally, include service accounts in access reviews. They are routinely excluded because they have no line manager, which is precisely why their privileges accumulate unchallenged. Review them quarterly with the named technical owner, confirm the credential has rotated, and confirm the account is still needed—then follow the same discipline across the wider machine identity estate.
At Privia Security, we hunt for over-privileged service accounts and exposed credentials in our infrastructure security testing services.
Not in the interactive sense, because no one is present to respond to a prompt. The equivalent protection comes from a different direction: platform-issued workload identities that are short-lived and bound to where the workload runs, certificate-based authentication, source address restrictions, and conditional access policies that limit which networks and devices the identity may authenticate from.
An Active Directory account type where Windows generates and rotates a 240-character password automatically, typically every 30 days, and distributes it to authorised hosts. No human ever knows the password, so it cannot be documented, pasted into a script, or cracked from a Kerberos ticket in practical time. It is the single best fix for Windows service account credentials.
Combine several sources: directory accounts with service principal names or password-never-expires set, the identities configured in Windows services and scheduled tasks across the estate, database logins, and application registrations in the cloud tenant. Then correlate with authentication logs to see which are genuinely active. Accounts with no identifiable owner should be disabled in a controlled window.
Departures from a narrow baseline, because legitimate service account behaviour is highly repetitive. Alert on interactive or remote desktop logon, authentication from an unfamiliar host, access to systems outside the normal set, activity outside the usual schedule, and any change to group membership or credentials. These produce very few false positives compared with equivalent rules for people.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.