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

# Azure MariaDB database server not using latest TLS version misconfiguration detected in code

## Rule Details

|                        |                                            |
| ---------------------- | ------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_AZURE\_37                         |
| Category - Subcategory | Public Exposure - Encryption And Protocols |
| Provider               | AZURE                                      |
| Severity               | LOW                                        |
| Framework              | Terraform, Terraform Plan                  |
| Mapped CSPM/KSPM Rule  | b131d726-d82a-4cbd-9f29-68e3ac2ed8a4       |

## Impact

This rule is checking to ensure that the Azure MariaDB server is using the latest version of TLS (Transport Layer Security), which is version 1.2. This is important because using outdated versions can expose the server to known vulnerabilities and security threats. TLS is a protocol used for securing communication over a network by encrypting the data sent between two systems to prevent potential eavesdropping, tampering, or message forgery. If an older version of TLS is used, it could lead to compromised data and impact the privacy and integrity of data transmission. Therefore, it is vital to guarantee the usage of the most recent version.

## How to Fix

*Resource:* azurerm\_mariadb\_server

* *Arguments:* ssl\_enforcement\_enabled, ssl\_minimal\_tls\_version\_enforced

To fix this issue, you should ensure that the 'ssl\_enforcement' option is set to "Enabled" and the 'ssl\_minimal\_tls\_version\_enforced' option is set to "TLS1\_2" in the Azure MariaDB server block.

## The above code is secure because it enforces SSL/TLS by making sure that all data flowing between the client and the server is encrypted. Furthermore, it enforces the server to use the latest and most secure version of TLS, the TLS 1.2. Using the latest version of TLS (1.2) or higher to encrypt data-in-transit is particularly crucial, because it offers enhanced security over older versions. \[source,go]

## resource "azurerm\_mariadb\_server" "example" { ... ssl\_enforcement\_enabled = true ssl\_minimal\_tls\_version\_enforced = "TLS1\_2" }


---

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