> 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/ai-and-machine-learning/appsec2-azure-52.md).

# Azure Synapse SQL Pool vulnerability assessment disabled misconfiguration detected in code

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_AZURE\_52                    |
| Category - Subcategory | Monitoring - Unintegrated             |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |

## Impact

This rule detects whether a Synapse SQL Pool in an Azure environment has a vulnerability assessment enabled. Vulnerability assessments are essential for maintaining a strong security posture. They help mitigate potential security risks by detecting vulnerabilities and providing recommendations for addressing them. Without vulnerability assessments, your Synapse SQL Pool could be exposed to security threats, potentially leading to data breaches, loss, or other cyberattacks.

Monitoring and maintaining the security of your database services is crucial for protecting sensitive data and complying with regulatory standards. Vulnerability assessments play a vital role in achieving this by proactively identifying and mitigating potential risks.

## How to Fix

**Terraform**

* **Resource:** azurerm\_synapse\_sql\_pool
* **Arguments:** azurerm\_synapse\_sql\_pool\_security\_alert\_policy, recurring\_scans.\*.enabled

Ensure that all `azurerm_synapse_sql_pool` resources have an associated `azurerm_synapse_sql_pool_security_alert_policy` block with recurring security scans (`recurring_scans.property`) enabled.

In this example, an `azurerm_synapse_sql_pool_vulnerability_assessment` resource is configured to enable automatic vulnerability scanning for your Synapse SQL Pool. This ensures your pool is regularly checked for potential security weaknesses.

```go
resource "azurerm_synapse_sql_pool_vulnerability_assessment" "example" {
+   sql_pool_security_alert_policy_id = azurerm_synapse_sql_pool_security_alert_policy.example.id
  ...
  recurring_scans {
+    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/ai-and-machine-learning/appsec2-azure-52.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.