Service Account
Also called Machine identity, Non-human identity.
A non-human identity used by an application or workload, not a person.
What it is
An identity created for software, automation, or a workload to authenticate and act on its own, rather than for a human user. It carries its own permissions and credentials and frequently runs unattended.
Why it matters
Service accounts are often over-permissioned, rarely rotated, and lightly monitored, which makes them attractive footholds and an easy way for attackers to blend into expected automation.
In practice
An investigator flags after-hours activity from a deployment service account that normally only runs during business-hour pipelines.
What to look for
- Service accounts logging in interactively or from user devices.
- Keys or tokens for service accounts created outside automation.
- Service accounts holding owner or admin rights.
Common mistake
Treating them as low risk because no person uses them. They often have broad rights and nobody watching their logins.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Microsoft Entra ID Protection Commercial
Scores sign-in and user risk in Microsoft Entra ID and can force MFA or a reset.
-
Okta Identity Threat Protection Commercial
Evaluates session risk continuously and can end sessions when it changes.
-
BloodHound Open source
Maps attack paths through Entra ID and Active Directory relationships.
Read next
- Workload Identity: Giving running workloads short-lived identity without embedded static secrets.
- Over-Permissioned Role: An identity granted far more access than its actual job requires.
- Secrets Management: Centralized, controlled storage and delivery of credentials and keys.