Glossary
Service account
Definition
A service account gives an application or automated process its own identity and permissions.
It is an identity for an application or automated task. It needs an owner and limited permissions even though no employee signs in with it.
A customer may include “Service account” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
A service account represents software rather than an employee. It lets an application, scheduled task or integration authenticate and perform agreed actions, such as reading stock levels or creating a backup. It may use a password, certificate, token or managed identity instead of an interactive sign-in.
Keeping automation separate from personal accounts makes its purpose and access easier to control. If a process runs through an employee's account, that person's departure or password change can break it. The process may also inherit more permissions than it needs.
For example, a small online retailer could give its stock synchronisation tool a dedicated identity allowed to update inventory, with no access to payroll. Someone still needs to own that account, document its purpose and review whether it remains necessary.
Service accounts are easy to forget because nobody uses them at a keyboard. Long-lived credentials and excessive permissions can give an attacker persistent access. Where supported, managed identities or short-lived credentials reduce the need to store reusable secrets. Inventory each automated identity, assign an owner, limit permissions and remove unused accounts. Prefer managed identities or short-lived credentials where supported, and rotate stored secrets when exposure or ownership changes.