메뉴
Ensure locked immutability policies are used for containers storing business-critical blob data
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-azure-storage-11-6명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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-11.6 |
| description | Ensure locked immutability policies are used for containers storing business-critical blob data |
| category | cis-azure-storage |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","azure","storage","blob-storage","immutability"] |
| cis_id | 11.6 |
| cis_benchmark | CIS Microsoft Azure Storage Services Benchmark v1.0.0 |
| tech_stack | ["azure"] |
| cwe_ids | [] |
| chains_with | [] |
| prerequisites | [] |
| severity_boost | {} |
Require locked immutability policies for all containers that store business-critical blob data. This measure protects the data from modifications or deletions, ensuring that critical information remains intact and unaltered, regardless of user actions or access permissions.
Implementing a locked immutability policy creates a Write Once, Read Many (WORM) storage model that safeguards critical data from accidental or malicious changes and deletions. Enforcing immutability minimizes data loss and tampering risks, enhancing data security and supporting regulatory requirements for data retention and integrity.
Enforcing locked immutability policies for blob storage may increase long-term retention costs and require additional administrative effort for policy management.
Once the policy is locked, the container cannot be deleted or edited, and the storage account cannot be deleted until the retention period has elapsed.
Storage accounts.Data storage, click Containers.Access policy.Immutable blob storage.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 container, run the following command to view immutability policies:
az storage container immutability-policy show --account-name <storage-account> --container <blob-container>
Ensure that an immutability policy is listed with "state": "Locked" for each blob container with business-critical blob data.
An immutability policy with "state": "Locked" exists for each blob container storing business-critical data.
Storage accounts.Data storage, click Containers.Access policy.Immutable blob storage, click + Add policy.Policy type drop-down, select Legal hold or Time-based retention.Allow protected append writes to, select None or Block and append blobs.Set retention period for, enter a number of days for retention.Enable version-level immutability if appropriate. Versioning must be enabled for this option to be available.Allow protected append writes to, select None, Append blobs, or Block and append blobs.Save.Lock policy.yes to confirm.OK.By default, no immutability policies are configured on blob containers.
Level 2 | Automated