> 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-5.md).

# IBM Cloud Service ID creation is not restricted in account settings in Terraform misconfiguration de

## Rule Details

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

## Impact

This rule detects whether Service ID creation is unrestricted in account settings. Service IDs are used to identify and authenticate services or applications, allowing them to interact with other services or resources. Unrestricted creation can increase the risk of unauthorized access and mismanagement of service identities. By restricting creation, you can enhance account security and mitigate potential breaches or misconfigurations.

## How to Fix

*Resource:* ibm\_iam\_account\_settings

* *Arguments:* restrict\_create\_service\_id

Ensure that only authorized users or services can create new service IDs by setting the `restrict_create_service_id` attribute to `RESTRICTED` in the IBM IAM account settings.

## In this example, the `restrict_create_service_id` attribute is set to `RESTRICTED` in the `ibm_iam_account_settings` resource to restrict the creation of service IDs. \[source,go]

resource "ibm\_iam\_account\_settings" "example" { ...

* restrict\_create\_service\_id = "RESTRICTED" }

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/iam/appsec2-ibm-5.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.