A service account is an account used by an application, script or integration, rather than a person, to access systems. It lets software authenticate and perform actions such as reading data, running jobs or connecting two services. Service accounts are common in cloud platforms, databases and third-party integrations.

They need careful handling because they often differ from user accounts in ways that favor attackers. Their credentials may be long-lived, shared across systems and rarely rotated, and they typically cannot use multi-factor authentication. They are also sometimes granted broad permissions for convenience, and their activity may be monitored less closely than people's.

A service account is not a problem in itself, and most environments need them. The risk depends on what the account can reach, how its credentials are stored and who is responsible for it. Accounts left over from retired projects are a common source of hidden exposure.

To manage them, keep an inventory with a named owner for each one, grant only the permissions needed, store credentials in a secrets manager, rotate them regularly, restrict where they can sign in from and monitor their activity. Remove accounts that are no longer in use.