> 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-azure-37.md).

# Azure Activity Log retention should not be set to less than 365 days misconfiguration detected in co

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_37                     |
| Category - Subcategory | Logging - Retention                   |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |
| Mapped CSPM/KSPM Rule  | 700e9da9-b460-41f7-a4c6-b38cc9fcf588  |

## Impact

A log profile controls how the activity log is exported and retained. Since the average time to detect a breach is 210 days, the activity log should be retained for 365 days or more, providing time to respond to any incidents. We recommend you set activity log retention for 365 days or greater.

## How to Fix

*Resource:* azurerm\_monitor\_log\_profile

* *Arguments:* retention policy

*Option 1*

## *Option 2* \[source,go]

resource "azurerm\_monitor\_log\_profile" "example" { name = "default" categories = \[ "Action", "Delete", "Write", ] locations = \[ "westus", "global", ]

* retention\_policy {
* enabled = true
* days = 365 } }

***

resource "azurerm\_monitor\_log\_profile" "example" { name = "default" categories = \[ "Action", "Delete", "Write", ] locations = \[ "westus", "global", ]

* retention\_policy {
* enabled = false
* days = 0 } }

***


---

# 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-azure-37.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.