> 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-ali-23.md).

# Alibaba Cloud RAM password policy maximal login attempts is more than 4 misconfiguration detected in

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_ALI\_23               |
| Category - Subcategory | IAM - Authentication Policies |
| Provider               | ALIBABA\_CLOUD                |
| Severity               | MEDIUM                        |
| Framework              | Terraform                     |

## Impact

This rule ensures that the maximum login attempts in the RAM (Resource Access Management) account password policy are set to no more than 5. Limiting login attempts helps protect accounts from brute-force attacks and unauthorized access attempts. It enforces stricter security controls, ensuring better protection for sensitive resources.

Failing to limit the maximum login attempts can increase the risk of successful brute-force attacks, potentially leading to account compromise.

## How to Fix

*Resource:* alicloud\_ram\_account\_password\_policy

* *Arguments:* max\_login\_attempts

To mitigate this issue, ensure the `max_login_attempts` attribute in the `alicloud_ram_account_password_policy` resource is set to a value no greater than 5.

## Example: \[source,go]

resource "alicloud\_ram\_account\_password\_policy" "example" { ...

* max\_login\_attempts = 7
* max\_login\_attempts = 3 }

***


---

# 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-ali-23.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.