> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/iam/appsec-k8s-38.md).

# Service account tokens are not mounted where necessary misconfiguration detected in code

## Rule Details

|                        |                             |
| ---------------------- | --------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_K8S\_38             |
| Category - Subcategory | Kubernetes - Access Control |
| Provider               | OTHER                       |
| Severity               | LOW                         |
| Framework              | Helm, Kubernetes, Kustomize |

## Impact

One way to authenticate the API is by using the Service Account token. *ServiceAccount* is an object managed by Kubernetes and used to provide an identity for processes that run in a pod. Every service account has a secret related to it, this secret contains a bearer token. This is a JSON Web Token (JWT), a method for representing claims securely between two parties. This Service Account token is being used during the authentication stage and can become useful for attackers if the service account is privileged and they have access to such a token. With this token an attacker can easily impersonate the service account and use REST APIs.

## How to Fix

*Resource:* Pod / Deployment / DaemonSet / StatefulSet / ReplicaSet / ReplicationController / Job / CronJob

* *Arguments:* automountServiceAccountToken (Optional) When set to false, you can opt out of automating API credentials for a service account. \[source,go]

***

apiVersion: v1 kind: Pod metadata: name: spec:

* automountServiceAccountToken: false

***

apiVersion: batch/v1beta1 kind: CronJob metadata: name: spec: schedule: <> jobTemplate: spec: template: spec:

* automountServiceAccountToken: false

***

apiVersion: <> kind: metadata: name: spec: template: spec:

* automountServiceAccountToken: false

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/iam/appsec-k8s-38.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.