Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-storage-4-9명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? 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-4.9 |
| description | Ensure cleaning up FSx Resources |
| category | cis-storage-services |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","storage","fsx","cleanup","resource-management","cost-optimization","level-2"] |
| cis_id | 4.9 |
| cis_benchmark | CIS AWS Storage Services Benchmark v1.0.0 |
| tech_stack | ["aws"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-storage-4.1","cis-aws-storage-4.3","cis-aws-storage-4.4"] |
| prerequisites | [] |
| severity_boost | {} |
Cleaning up FSx resources involves removing unused or unnecessary FSx file systems and associated components to optimize costs and maintain a secure cloud environment. This includes deleting redundant file systems, snapshots, and mount targets, while ensuring all data is backed up or migrated. Regular cleanup prevents resource sprawl, reduces expenses, and maintains the overall health and performance of your AWS infrastructure.
The rationale for cleaning up FSx resources is to optimize costs and ensure a secure and efficient cloud environment. By removing unused or unnecessary file systems, snapshots, and mount targets, you prevent resource sprawl and reduce unnecessary expenses. Regular cleanup also helps maintain the overall health and performance of your AWS infrastructure, ensuring it remains organized and secure.
Failing to clean up FSx resources can lead to:
Review FSx Resources:
Review Associated Resources:
EC2 Instances:
S3 Buckets:
Security Groups and Network Resources:
# List all File Caches
aws fsx describe-file-caches \
--query 'FileCaches[].{ID:FileCacheId,Name:FileCachePath,Status:Lifecycle,Size:StorageCapacity}' \
--output table
# List EC2 instances
aws ec2 describe-instances \
--filters "Name=instance-state-name,Values=running,stopped" \
--query 'Reservations[].Instances[].[InstanceId,InstanceType,State.Name,Tags[?Key==`Name`].Value|[0]]' \
--output table
# List S3 buckets with size
aws s3 ls
aws s3 ls s3://<bucket-name> --recursive --summarize
# Get bucket size
aws s3api list-objects-v2 \
--bucket <bucket-name> \
--query 'sum(Contents[].Size)' \
--output json
All unused FSx resources should be identified and evaluated for cleanup:
To clean the FSx resources:
Terminate the EC2 instance:
Delete FSx cache:
DeleteDelete the S3 Bucket:
EmptyDelete in the S3 console# 1. Terminate EC2 instance
aws ec2 terminate-instances --instance-ids <instance-id>
# Verify termination
aws ec2 describe-instances --instance-ids <instance-id> \
--query 'Reservations[].Instances[].State.Name'
# 2. Delete File Cache
aws fsx delete-file-cache --file-cache-id <cache-id>
# Monitor deletion status
aws fsx describe-file-caches --file-cache-ids <cache-id> \
--query 'FileCaches[0].Lifecycle'
# 3. Empty S3 bucket
aws s3 rm s3://<bucket-name> --recursive
# Verify bucket is empty
aws s3 ls s3://<bucket-name>
# 4. Delete S3 bucket
aws s3api delete-bucket --bucket <bucket-name> --region <region>
# 5. Delete security groups (if created specifically for FSx)
# Note: Can only delete after all resources using them are terminated
aws ec2 delete-security-group --group-id <security-group-id>
FSx resources are not automatically cleaned up. Manual deletion is required for all components.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 3.8 Document Data Flows Document data flows. Data flow documentation includes service provider data flows and should be based on the enterprise's data management process. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard. | ● | ● | |
| v8 | 8.3 Ensure Adequate Audit Log Storage Ensure that logging destinations maintain adequate storage to comply with the enterprise's audit log management process. | ● | ● | ● |
| v7 | 7.8 Implement DMARC and Enable Receiver-Side Verification To lower the chance of spoofed or modified emails from valid domains, implement Domain-based Message Authentication, Reporting and Conformance (DMARC) policy and verification, starting by implementing the Sender Policy Framework (SPF) and the DomainKeys Identified Mail(DKIM) standards. | ● | ● | |
| v7 | 13.4 Only Allow Access to Authorized Cloud Storage or Email Providers Only allow access to authorized cloud storage or email providers. | ● | ● |
Level 2