用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-storage-17-7命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
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
基于 SOC 职业分类
| name | cis-azure-storage-17.7 |
| description | Ensure Soft Delete is Enabled for Azure Containers and Blob Storage |
| category | cis-azure-storage |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","storage","storage-accounts","soft-delete"] |
| cis_id | 17.7 |
| cis_benchmark | CIS Microsoft Azure Storage Services Benchmark v1.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
The Azure Storage blobs contain data like ePHI or Financial, which can be secret or personal. Data that is erroneously modified or deleted by an application or other storage account user will cause data loss or unavailability.
It is recommended that both Azure Containers with attached Blob Storage and standalone containers with Blob Storage be made recoverable by enabling the soft delete configuration. This is to save and recover data when blobs or blob snapshots are deleted.
Containers and Blob Storage data can be incorrectly deleted. An attacker/malicious user may do this deliberately in order to cause disruption. Deleting an Azure Storage blob causes immediate data loss. Enabling this configuration for Azure storage ensures that even if blobs/data were deleted from the storage account, Blobs/data objects are recoverable for a particular time which is set in the "Retention policies," ranging from 7 days to 365 days.
Additional storage costs may be incurred as snapshots are retained.
Storage Accounts.Data management, go to Data protection.Enable soft delete for blobs is checked.Enable soft delete for containers is checked.Blob Storage: Ensure that the output of the below command contains enabled status as true and days is not empty or null:
az storage blob service-properties delete-policy show
--account-name <storageAccount>
--account-key <accountkey>
Azure Containers: Ensure that within containerDeleteRetentionPolicy, the enabled property is set to true:
az storage account blob-service-properties show
--account-name <storageAccount>
--resource-group <resourceGroup>
Soft delete should be enabled for both blobs and containers with an appropriate retention period (7-365 days). CLI output should show enabled: true for both blob delete policy and container delete retention policy.
Storage Accounts.Data management, go to Data protection.Enable soft delete for blobs.Enable soft delete for containers.Save.Update blob storage retention days in below command:
az storage blob service-properties delete-policy update --days-retained <RetentionDaysValue> --account-name <StorageAccountName> --account-key <AccountKey> --enable true
Update container retention with the below command:
az storage account blob-service-properties update
--enable-container-delete-retention true
--container-delete-retention-days <days>
--account-name <storageAccount>
--resource-group <resourceGroup>
Soft delete for containers and blob storage is enabled by default on storage accounts created via the Azure Portal, and disabled by default on storage accounts created via Azure CLI or PowerShell.
Level 1 | Automated