用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-storage-2-5命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 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
基于 SOC 职业分类
正在显示 SKILL.md
| name | cis-aws-storage-2.5 |
| description | Ensure creating snapshots of EBS volumes |
| category | cis-storage-services |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","storage","ebs","snapshot","backup","disaster-recovery","data-replication"] |
| cis_id | 2.5 |
| cis_benchmark | CIS AWS Storage Services Benchmark v1.0.0 |
| tech_stack | ["aws"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-storage-2.3","cis-aws-storage-2.4"] |
| prerequisites | ["cis-aws-storage-2.1"] |
| severity_boost | {} |
A snapshot is a backup of your EBS volume that captures its state at a specific point in time, storing only the data changes since the last snapshot to optimize storage costs and speed. Snapshots are crucial for data recovery, creating new EBS volumes, and replicating data across AWS regions for disaster recovery and high availability. Restoring from a snapshot allows you to create a new EBS volume and attach it to an EC2 instance in the same availability zone, ensuring data integrity and accessibility.
The rationale behind using EBS snapshots is to ensure efficient and cost-effective data backup and recovery. By capturing only the data changes since the last snapshot, storage costs are minimized and the backup process is expedited. Snapshots are essential for maintaining data integrity, facilitating quick recovery, and enabling seamless data replication across regions, thereby enhancing disaster recovery capabilities and operational resilience.
Not utilizing EBS snapshots can lead to significant risks and drawbacks. Without snapshots, data recovery becomes more complex and time-consuming, increasing the risk of prolonged downtime in the event of data loss or system failure. Additionally, the absence of incremental backups can result in higher storage costs and inefficient use of resources. The lack of data replication across regions severely compromises disaster recovery efforts, making it challenging to maintain high availability and operational continuity. Overall, failing to use snapshots undermines data integrity, security, and the ability to quickly restore critical information.
To audit the use of EBS snapshots in AWS, follow these steps:
Access the AWS Management Console
Review EBS Snapshots
Verify Snapshot Policies
Check Snapshot Status and Details
Inspect IAM Policies and Permissions
Use AWS Config Rules
Review AWS CloudTrail Logs
Generate Reports
# List all EBS snapshots
aws ec2 describe-snapshots --owner-ids self \
--query 'Snapshots[].[SnapshotId,VolumeId,StartTime,State,Description]' \
--output table
# Find volumes without recent snapshots (example: no snapshot in last 7 days)
aws ec2 describe-volumes --query 'Volumes[].VolumeId' --output text | \
while read volume; do
snapshot=$(aws ec2 describe-snapshots \
--filters Name=volume-id,Values=$volume \
--query 'Snapshots | sort_by(@, &StartTime) | [-1].StartTime' \
--output text)
echo "Volume: $volume, Latest Snapshot: $snapshot"
done
# Check snapshot lifecycle policies
aws dlm get-lifecycle-policies
# Verify snapshot encryption
aws ec2 describe-snapshots --owner-ids self \
--query 'Snapshots[?Encrypted==`false`].[SnapshotId,VolumeId]' \
--output table
To create an EBS snapshot on AWS, follow these steps:
Access the AWS Management Console
Navigate to the EC2 Dashboard
Select the Volume
Create a Snapshot
Configure the Snapshot
Initiate the Snapshot Creation
Monitor the Snapshot
Verify Completion
# Create a snapshot manually
aws ec2 create-snapshot \
--volume-id vol-xxxxxxxxx \
--description "Manual backup - $(date +%Y-%m-%d)" \
--tag-specifications 'ResourceType=snapshot,Tags=[{Key=Name,Value=DataSnapshot},{Key=Backup,Value=Manual}]'
# Create snapshot lifecycle policy
aws dlm create-lifecycle-policy \
--description "Daily EBS Snapshot Policy" \
--state ENABLED \
--execution-role-arn arn:aws:iam::ACCOUNT:role/AWSDataLifecycleManagerDefaultRole \
--policy-details file://snapshot-policy.json
# Copy snapshot to another region for DR
aws ec2 copy-snapshot \
--source-snapshot-id snap-xxxxxxxxx \
--source-region us-east-1 \
--region us-west-2 \
--description "DR copy"
By default, no automatic snapshots are created. Users must manually create snapshots or configure Data Lifecycle Manager (DLM) policies.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 11.1 Establish and Maintain a Data Recovery Process | ● | ● | ● |
| v7 | 10.1 Ensure Regular Automated Back Ups | ● | ● | ● |