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

# IBM Cloud API key creation is not restricted in account settings in Terraform misconfiguration detec

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_IBM\_3           |
| Category - Subcategory | IAM - Overly Permissive   |
| Provider               | IBM                       |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule detects whether API key creation is unrestricted in account settings. Unrestricted API key creation can increase the risk of unauthorized access. By restricting creation, you can better control who has access to your resources, minimizing the potential for keys to be created without oversight, and mitigate the risk of malicious use.

## How to Fix

*Resource:* ibm\_iam\_account\_settings

* *Arguments:* restrict\_create\_platform\_apikey

Ensure that API key creation is restricted to authorized processes and users by setting the `restrict_create_platform_apikey` attribute to `RESTRICTED` in account settings. This helps prevent unauthorized access to IBM Cloud resources.

## In this example, the `restrict_create_platform_apikey` attribute is set to `RESTRICTED` in the `ibm_iam_account_settings` resource to restrict API key creation. \[source,go]

## resource "ibm\_iam\_account\_settings" "example" { ... restrict\_create\_platform\_apikey = "RESTRICTED" # Restricts API key creation }


---

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