القائمة
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-storage-4-7يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى 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.7 |
| description | Ensure mounting FSx cache |
| category | cis-storage-services |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","storage","fsx","lustre","mount","file-system","level-2"] |
| cis_id | 4.7 |
| cis_benchmark | CIS AWS Storage Services Benchmark v1.0.0 |
| tech_stack | ["aws","linux"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-storage-4.5","cis-aws-storage-4.6","cis-aws-storage-4.8"] |
| prerequisites | ["cis-aws-storage-4.4","cis-aws-storage-4.5","cis-aws-storage-4.6"] |
| severity_boost | {} |
Mounting the FSx cache is a crucial step to optimize data retrieval and system performance. This process involves connecting the FSx file system to your compute instances, allowing them to access cached data efficiently. Properly mounting the FSx cache ensures low-latency access to frequently used data, enhances overall application performance, and leverages the full capabilities of the AWS FSx service. This setup is essential for achieving high performance and efficient data processing in your AWS environment.
By connecting the FSx file system to your compute instances, you enable low-latency access to frequently used data, significantly improving application performance. This setup leverages the full capabilities of the AWS FSx service, ensuring efficient data processing and resource utilization in your AWS environment. Properly mounting the FSx cache is essential for achieving high performance and operational efficiency.
Without properly mounting the FSx cache, compute instances cannot access the cached data, resulting in inability to benefit from the high-performance caching layer and potential degradation in application performance and data access times.
ssh -i "{KEY.pem}" ubuntu@{your-ec2-instance}
ls -ld /mnt
df -h | grep /mnt
mount | grep lustre
# Check if the path shows up in the file system
ls -la /mnt
# Verify DNS name is resolvable
nslookup <cache_dns_name>
# Check VPC connectivity
# Ensure EC2 instance is in the same VPC as the cache
The FSx cache should be properly mounted with:
/mnt or custom path)df -h, mount)To mount your cache, follow the next steps:
sudo mkdir -p /mnt
cache_dns_name with the actual file cache's Domain Name System (DNS) namemountname with the cache's mount name, which you can get by running the describe-file-caches AWS CLI command or DescribeFileCaches API operationsudo mount -t lustre -o relatime,flock cache_dns_name@tcp:/mountname /mnt
Note: Make sure your EC2 instance is in the same VPC as your cache.
# If done correctly, the path of your folder will show up in the /mnt folder
df -h
ls -la /mnt
# You can also use the df command to see the DNS and mount point is attached to your file system:
df -h | grep /mnt
# Get cache DNS name and mount name
aws fsx describe-file-caches --file-cache-ids <cache-id> \
--query 'FileCaches[0].[DNSName,LustreConfiguration.MountName]' \
--output text
# Get cache details including VPC information
aws fsx describe-file-caches --file-cache-ids <cache-id> \
--query 'FileCaches[0].[DNSName,VpcId,SubnetIds]'
By default, FSx cache is not mounted on EC2 instances. Manual mounting is required after cache creation and Lustre client installation.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v7 | 3.3 Protect Dedicated Assessment Accounts Use a dedicated account for authenticated vulnerability scans, which should not be used for any other administrative activities and should be tied to specific machines at specific IP addresses. | ● | ● | |
| v7 | 5.2 Maintain Secure Images Maintain secure images or templates for all systems in the enterprise based on the organization's approved configuration standards. Any new system deployment or existing system that becomes compromised should be imaged using one of those images or templates. | ● | ● | |
| v7 | 6.4 Ensure adequate storage for logs Ensure that all systems that store logs have adequate storage space for the logs generated. | ● | ● | |
| v7 | 8.3 Enable Operating System Anti-Exploitation Features/ Deploy Anti-Exploit Technologies Enable anti-exploitation features such as Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR) that are available in an operating system or deploy appropriate toolkits that can be configured to apply protection to a broader set of applications and executables. | ● | ● |
Level 2