Cis Azure Storage 11.3
DevOps & Securitycis-azure-storage-11.3Cis Azure Storage 11.3 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Ensure that soft delete for blobs on Azure Blob Storage storage accounts is Enabled
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Storage_Services_Benchmark_v1.0.0/cis-azure-storage-11.3/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-storage-11-3, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
11.3 Ensure that soft delete for blobs on Azure Blob Storage storage accounts is Enabled (Automated)
Description
Blobs in Azure storage accounts may contain sensitive or personal data, such as ePHI or financial information. Data that is erroneously modified or deleted by an application or a user can lead to data loss or unavailability.
It is recommended that soft delete be enabled on Azure storage accounts with blob storage to allow for the preservation and recovery of data when blobs or blob snapshots are deleted.
Rationale
Blobs can be deleted incorrectly. An attacker or malicious user may do this deliberately in order to cause disruption. Deleting an Azure storage blob results in immediate data loss. Enabling this configuration for Azure storage accounts ensures that even if blobs are deleted from the storage account, the blobs are recoverable for a specific period of time, which is defined in the "Retention policies," ranging from 7 to 365 days.
Impact
All soft-deleted data is billed at the same rate as active data. Additional costs may be incurred for deleted blobs until the soft delete period ends and the data is permanently removed.
Audit Procedure
Audit from Azure Portal
- Go to
Storage Accounts. - For each Storage Account with blob storage, under
Data management, go toData protection. - Ensure that
Enable soft delete for blobsis checked. - Ensure that the retention period is a sufficient length for your organization.
Audit from Azure CLI
Run the following command to list storage accounts:
az storage account list
Run the following command to determine if a storage account has containers:
az storage container list --account-name <storage-account>
For each storage account with containers, ensure that the output of the below command contains "enabled": true and days is not null:
az storage blob service-properties delete-policy show --account-name <storage-account>
Expected Result
enabled is true and days is set to a value between 7 and 365, inclusive, appropriate for the organization.
Remediation
Remediate from Azure Portal
- Go to
Storage Accounts. - For each Storage Account with blob storage, under
Data management, go toData protection. - Check the box next to
Enable soft delete for blobs. - Set the retention period to a sufficient length for your organization.
- Click
Save.
Remediate from Azure CLI
For each storage account requiring remediation, run the following command to enable soft delete for blobs:
az storage blob service-properties delete-policy update --days-retained <retention-days> --account-name <storage-account> --enable true
Default Value
Soft delete for 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.
References
Profile
Level 1 | Automated