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

# IBM Cloud Multi-Factor Authentication (MFA) not enabled at the account level in Terraform misconfigu

## Rule Details

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

## Impact

This rule detects whether Multi-Factor Authentication (MFA) is disabled at the account level within an Identity and Access Management (IAM) framework. Disabled MFA increases vulnerability to attacks such as phishing, credential stuffing, and brute force. MFA requires users to provide multiple forms of verification, helping to protect sensitive data and resources by preventing unauthorized access, even if passwords are compromised.

## How to Fix

*Resource:* ibm\_iam\_account\_settings

* *Arguments:* mfa

Ensure that (MFA) is enabled at the account level by setting up the required IAM policy within your Terraform configuration with MFA configured to one of the supported values other than NONE.

## In this example, the 'mfa attribute' within the 'ibm\_iam\_account\_settings' resource is used to enable MFA configuration at the account level. \[source,go]

resource "ibm\_iam\_account\_settings" "account\_settings" { account\_id = var.account\_id

* mfa = "LEVEL3" // or you can specify the types like TOTP, LEVEL1, etc. }

***


---

# 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-4.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.