> 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-aws-325.md).

# RDS Cluster audit logging for MySQL engine is disabled misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AWS\_325              |
| Category - Subcategory | Logging - Disabled or missing |
| Provider               | AWS                           |
| Severity               | LOW                           |
| Framework              | Terraform, Terraform Plan     |

## Impact

This rule verifies if audit logging is enabled for RDS Clusters running the MySQL engine in AWS (Amazon Web Services). Audit logging is vital because it helps in tracking and examining activities within the database. If audit logging is not enabled, it could lead to a lack of visibility which is crucial for identifying suspicious activities or understanding the cause of unexpected changes or errors. Consequently, it can pose serious risks, including data breaches and hinder compliance-related responsibilities.

## How to Fix

*Resource:* aws\_rds\_cluster

* *Arguments:* enabled\_cloudwatch\_logs\_exports

## To fix this issue, you should enable audit logging for your RDS Cluster which is using the MySQL engine. Audit logging helps in recording actions and events that are happening in the AWS environment and reviewing these logs enables identification of patterns and spotting unusual activities. \[source,go]

resource "aws\_rds\_cluster" "pass" { master\_username = "username" master\_password = "password"

* enabled\_cloudwatch\_logs\_exports = \["audit"] iam\_database\_authentication\_enabled = true }

***


---

# 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/logging/appsec-aws-325.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.