> 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/appsec-azure-240.md).

# Azure Synapse Workspace not encrypted with a Customer Managed Key (CMK) misconfiguration detected in

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_AZURE\_240                    |
| Category - Subcategory | Storage - Encryption                  |
| Provider               | AZURE                                 |
| Severity               | LOW                                   |
| Framework              | ARM, Bicep, Terraform, Terraform Plan |

## Impact

This rule detects whether an Azure Synapse Workspace is encrypted with a CMK. Ensuring encryption with a CMK is crucial because it grants organizations greater control over the encryption keys used to protect their data. Using a CMK enhances security by allowing key rotation, revocation, and the ability to use an organization's own key management policies. This strengthens data protection within the Synapse Workspace. Unencrypted Synapse Workspaces pose a significant security risk. Sensitive data stored and processed within them is potentially exposed to unauthorized access and data breaches.

## How to Fix

*Resource:* Microsoft.Synapse/workspaces

* *Arguments:* encryption

## In this example, an `encryption` property is added within the `Microsoft.Synapse/workspaces` resource definition of the JSON template. This encryption property will house the configuration for the CMK, significantly enhancing data security within the workspace. \[source,go]

{ "type": "Microsoft.Synapse/workspaces", ... "properties": {

* "encryption": {
* ```
   "cmk": {
  ```
* ```
     ...
  ```
* ```
   }
  ```
* }, ... } }

***


---

# 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/ai-and-machine-learning/appsec-azure-240.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.