Menu
Ensure Storage for Critical Data are Encrypted with Customer Managed Keys (CMK)
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-storage-17-1-6The command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
Based on SOC occupation classification
Showing SKILL.md
| name | cis-azure-storage-17.1.6 |
| description | Ensure Storage for Critical Data are Encrypted with Customer Managed Keys (CMK) |
| category | cis-azure-storage |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","storage","storage-accounts","cmk","encryption"] |
| cis_id | 17.1.6 |
| cis_benchmark | CIS Microsoft Azure Storage Services Benchmark v1.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Enable sensitive data encryption at rest using Customer Managed Keys (CMK) rather than Microsoft Managed keys.
By default, data in the storage account is encrypted using Microsoft Managed Keys at rest. All Azure Storage resources are encrypted, including blobs, disks, files, queues, and tables. All object metadata is also encrypted. If you want to control and manage this encryption key yourself, however, you can specify a customer-managed key. That key is used to protect and control access to the key that encrypts your data. You can also choose to automatically update the key version used for Azure Storage encryption whenever a new version is available in the associated Key Vault.
While it is possible to automate the assessment of this recommendation, the assessment status for this recommendation remains 'Manual.' This is because the recommendation pertains to storage accounts that store critical data and is therefore not applicable to all storage accounts.
If the key expires by setting the 'activation date' and 'expiration date', the user must rotate the key manually.
Using Customer Managed Keys may also incur additional man-hour requirements to create, store, manage, and protect the keys as needed.
Storage AccountsSecurity + networking, go to EncryptionEncryption type is set to Customer-managed keysConnect-AzAccount
Set-AzContext -Subscription <subscription id>
Get-AzStorageAccount |Select-Object -ExpandProperty Encryption
PowerShell Results - Non-Compliant:
KeySource : Microsoft.Storage
PowerShell Results - Compliant:
KeySource : Microsoft.Keyvault
If referencing a digital copy of this Benchmark, clicking a Policy ID will open a link to the associated Policy definition in Azure. If referencing a printed copy, you can search Policy IDs from this URL: https://portal.azure.com/#view/Microsoft_Azure_Policy/PolicyMenuBlade/~/Definitions
6fac406b-40ca-413b-bf8e-0bf964659c25The Encryption type is set to Customer-managed keys in the Azure Portal for each storage account containing critical data. In PowerShell, the KeySource property returns Microsoft.Keyvault instead of Microsoft.Storage. The Azure Policy 'Storage accounts should use customer-managed key for encryption' shows compliant.
Storage AccountsSecurity + networking, go to EncryptionEncryption type to Customer-managed keysSaveBy default, Encryption type is set to Microsoft Managed Keys.
Level 2 | Manual