> 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/logging/appsec-ali-5.md).

# Alibaba Cloud Action Trail Logging is not enabled for all events misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_ALI\_5                |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | ALIBABA\_CLOUD                |
| Severity               | MEDIUM                        |
| Framework              | Terraform                     |

## Impact

This rule ensures that Action Trail in Alibaba Cloud is configured to log all events. Action Trail allows for governance, compliance, and auditing over your Alibaba Cloud account by recording the actions taken on your account. Logging all events ensures that all user and API actions are recorded, providing a comprehensive history of activity for security analysis.

Failing to log all events can result in incomplete logging data, which could obscure the audit trail and hinder investigations and compliance efforts.

## How to Fix

*Resource:* alicloud\_actiontrail\_trail

* *Arguments:* event\_rw

To mitigate this issue, ensure the `event_rw` attribute in the `alicloud_actiontrail_trail` resource is set to `All`.

## Example: \[source,go]

resource "alicloud\_actiontrail\_trail" "example" { ...

* event\_rw = "All" }

***


---

# 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/logging/appsec-ali-5.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.