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

# Amazon MSK cluster logging is not enabled misconfiguration detected in code

## Rule Details

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

## Impact

Amazon MSK enables you to build and run applications that use Apache Kafka to process streaming data. It also provides a control-plane for advanced operations, for example, creating, updating, and deleting clusters. Consistent cluster logging helps you determine if a request was made with root or AWS Identity and Access Management (IAM) user credentials and whether the request was made with temporary security credentials for a role or federated user.

## How to Fix

*Resource:* AWS::MSK::Cluster

* *Argument:* LoggingInfo. Configure your MSK cluster to send broker logs to different destination types. This is a container for the configuration details related to broker logs. \[source,go]

***

{ "Type" : "AWS::MSK::Cluster", "Properties" : { ...

* "LoggingInfo" : {
* "BrokerLogs" : {
* "CloudWatchLogs" : CloudWatchLogs,
* "Firehose" : Firehose,
* "S3" : S3 } } } }

***


---

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