用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-foundations-6-1-1-3命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-azure-foundations-6.1.1.3 |
| description | Ensure storage account containing activity logs is encrypted with CMK |
| category | cis-azure-foundations |
| version | 5.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","logging","monitoring","encryption","cmk","storage"] |
| cis_id | 6.1.1.3 |
| cis_benchmark | CIS Microsoft Azure Foundations Benchmark v5.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | ["cis-azure-foundations-6.1.1.1"] |
| prerequisites | ["cis-azure-foundations-6.1.1.1"] |
| severity_boost | {} |
Customer-managed keys introduce additional depth to security by providing a means to manage access control for encryption keys. Where compliance and security frameworks indicate the need, and organizational capacity allows, sensitive data at rest can be encrypted using customer-managed keys (CMK) rather than Microsoft-managed keys.
By default in Azure, data at rest tends to be encrypted using Microsoft-managed keys. If your organization wants to control and manage encryption keys for compliance and defense-in-depth, customer-managed keys can be established.
Configuring the storage account with the activity log export container to use CMKs provides additional confidentiality controls on log data, as a given user must have read permission on the corresponding storage account and must be granted decrypt permission by the CMK.
If the key expires due to setting the 'activation date' and 'expiration date', the key must be rotated manually. Using customer-managed keys may also incur additional man-hour requirements to create, store, manage, and protect the keys as needed.
Monitor.Activity log.Export Activity Logs.Subscription.Storage Account for the diagnostic setting.Storage accounts.Security + networking, click Encryption.Customer-managed keys is selected and a key is set.az monitor diagnostic-settings subscription list --subscription <subscription id> --query 'value[*].storageAccountId'
az storage account list --query "[?name=='<Storage Account Name>']"
In command output ensure keySource is set to Microsoft.Keyvault and keyVaultProperties is not set to .
nullGet-AzStorageAccount -ResourceGroupName <resource group name> -Name <storage account name>|select-object -ExpandProperty encryption|format-list
Ensure the value of KeyVaultProperties is not null or empty, and ensure KeySource is not set to Microsoft.Storage.
The storage account containing activity logs should use Customer-managed keys (CMK) for encryption, with keySource set to Microsoft.Keyvault.
Monitor.Activity log.Export Activity Logs.Subscription.Storage Account for the diagnostic setting.Storage accounts.Security + networking, click Encryption.Encryption type, select Customer-managed keys.az storage account update --name <name of the storage account> --resource-group <resource group for a storage account> --encryption-key-source=Microsoft.Keyvault --encryption-key-vault <Key Vault URI> --encryption-key-name <KeyName> --encryption-key-version <Key Version>
Set-AzStorageAccount -ResourceGroupName <resource group name> -Name <storage account name> -KeyvaultEncryption -KeyVaultUri <key vault URI> -KeyName <key name>
By default, encryption type is set to Microsoft-managed keys.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.11 Encrypt Sensitive Data at Rest | x | x | |
| v7 | 14.8 Encrypt Sensitive Information at Rest | x |
| Techniques | Tactics | Mitigations |
|---|---|---|
| T1530 | TA0009 | M1041 |
Level 2 | Manual