> 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/public-exposure/appsec2-ibm-7.md).

# IBM Cloud Kubernetes clusters are accessible by using public endpoint in Terraform misconfiguration

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_IBM\_7                      |
| Category - Subcategory | Public Exposure - Database Endpoints |
| Provider               | IBM                                  |
| Severity               | MEDIUM                               |
| Framework              | Terraform, Terraform Plan            |

## Impact

This rule detects whether Kubernetes clusters are accessible via public endpoints rather than private endpoints. Exposing clusters through public endpoints increases the risk of unauthorized access and potential vulnerabilities being exploited. By restricting access to private endpoints, sensitive workloads and data are protected from external threats, thereby enhancing the overall security of the Kubernetes environment.

## How to Fix

*Resource:* ibm\_container\_cluster

* *Arguments:* private\_service\_endpoint, public\_service\_endpoint

Ensure the IBM Kubernetes cluster is only accessible via a private endpoint by setting the `private_service_endpoint` to `true`, and either omitting the `public_service_endpoint` attribute, or setting it to `false`.

## In this example, the `public_service_endpoint` attribute is set to `false` and the `private_service_endpoint` attribute is set to `true` in the `ibm_container_cluster` resource to configure access to the Kubernetes cluster via a private endpoint only. \[source,go]

resource "ibm\_container\_cluster" "secure\_cluster" { ...

* public\_service\_endpoint = false
* private\_service\_endpoint = true }

***


---

# 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/public-exposure/appsec2-ibm-7.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.