5.1.5 Ensure that default service accounts are not actively used.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version


The default service account should not be used to ensure that rights granted to applications can be more easily audited and reviewed.


Kubernetes provides a default service account which is used by cluster workloads where no specific service account is assigned to the pod.

Where access to the Kubernetes API from a pod is required, a specific service account should be created for that pod, and rights granted to that service account.

The default service account should be configured such that it does not provide a service account token and does not have any explicit rights assignments.


All workloads which require access to the Kubernetes API will require an explicit service account to be created.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.


None required.

Default Value:

By default, in OpenShift 4 every project has its own service accounts. Every service account has an associated user name that can be granted roles, just like a regular user. The user name for each service account is derived from its project and the name of the service account. Service accounts are required in each project to run builds, deployments, and other pods. The default service accounts that are automatically created for each project are isolated by the project namespace.

See Also