Skip to content
Back to skills

Cis Oke V180 5.2.1

ASecurity

Prefer using dedicated Service Accounts (Automated)

  • 3,518 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 3, 2026
securitygobashnodekubernetesapi

Works with

  • api

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-oke-v180-5.2.1 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis Oke V180 5.2.1?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis Oke V180 5.2.1
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-oke-v180-5-2-1/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-oke-v180-5-2-1)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-oke-v180-5.2.1
description: "Prefer using dedicated Service Accounts (Automated)"
category: cis-oke
version: "1.8.0"
author: cyberstrike-official
tags: [cis, oke, kubernetes, oci, managed-services, iam, identity, service-accounts, workload-identity]
cis_id: "5.2.1"
cis_benchmark: "CIS Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) Benchmark v1.8.0"
tech_stack: [kubernetes, oci, oke]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---

# 5.2.1 Prefer using dedicated Service Accounts (Automated)

## Profile Applicability

- Level 1

## Description

Kubernetes workloads should not use cluster node service accounts to authenticate to Oracle Cloud APIs. Each Kubernetes Workload that needs to authenticate to other Oracle services using Cloud IAM should be provisioned a dedicated Service account.

## Rationale

Manual approaches for authenticating Kubernetes workloads running on OKE against Oracle Cloud APIs are: storing service account keys as a Kubernetes secret (which introduces manual key rotation and potential for key compromise); or use of the underlying nodes' IAM Service account, which violates the principle of least privilege on a multitenanted node, when one pod needs to have access to a service, but every other pod on the node that uses the Service account does not.

## Audit

For each namespace in the cluster, review the rights assigned to the default service account and ensure that it has no roles or cluster roles bound to it apart from the defaults.

```bash
kubectl get serviceaccounts/default -o yaml
```

Additionally ensure that the `automountServiceAccountToken: false` setting is in place for each default service account.

## Remediation

When you create a pod, if you do not specify a service account, it is automatically assigned the default service account in the same namespace. If you get the raw json or yaml for a pod you have created (`for example, kubectl get pods/<podname> -o yaml`), you can see the spec.serviceAccountName field has been automatically set.

See Configure Service Accounts for Pods.

## References

1. https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/

## CIS Controls

| Controls Version | Control                                                     | IG 1 | IG 2 | IG 3 |
| ---------------- | ----------------------------------------------------------- | ---- | ---- | ---- |
| v8               | 5.5 Establish and Maintain an Inventory of Service Accounts |      | x    | x    |
| v7               | 4.3 Ensure the Use of Dedicated Administrative Accounts     | x    | x    | x    |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in security →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.