Menü
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Basierend auf der SOC-Berufsklassifikation
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-storage-4-4Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
SKILL.md wird angezeigt
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
| name | cis-aws-storage-4.4 |
| description | Ensure the creation of Elastic File Cache |
| category | cis-storage-services |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","storage","fsx","file-cache","cache-creation","vpc","kms","level-2"] |
| cis_id | 4.4 |
| 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.2","cis-aws-storage-4.3","cis-aws-storage-4.5"] |
| prerequisites | ["cis-aws-storage-4.2","cis-aws-storage-4.3"] |
| severity_boost | {} |
With the prerequisites completed, we can now proceed to create our Elastic File Cache.
By implementing an Elastic File Cache, frequently accessed data is stored closer to the application, reducing latency and speeding up access times. This approach optimizes resource utilization, improves user experience, and ensures that the system can handle high-demand workloads effectively.
Without implementing Elastic File Cache, applications may experience higher latency, slower data access times, and reduced performance, particularly for frequently accessed data. This can negatively impact user experience and system efficiency.
# List all File Caches
aws fsx describe-file-caches --query 'FileCaches[].[FileCacheId,FileCachePath,Lifecycle,StorageCapacity]' --output table
# Describe a specific File Cache
aws fsx describe-file-caches --file-cache-ids <cache-id>
# Check Data Repository Associations
aws fsx describe-data-repository-associations --filters Name=file-cache-id,Values=<cache-id>
Elastic File Cache should be properly created and configured with:
s3://(example-bucket)/(example-prefix)/ns1 or subdirectory such as /ns1/subdir within Amazon File Cache to associate with the S3 data repository. The first forward slash in the path is required# Create File Cache
aws fsx create-file-cache \
--file-cache-type LUSTRE \
--file-cache-type-version 2.12 \
--storage-capacity 1200 \
--subnet-ids <subnet-id> \
--security-group-ids <security-group-id> \
--data-repository-associations '[
{
"FileCachePath": "/ns1",
"DataRepositoryPath": "s3://<bucket-name>/<prefix>",
"DataRepositorySubdirectories": []
}
]' \
--kms-key-id "alias/aws/fsx"
# Verify cache creation
aws fsx describe-file-caches --file-cache-ids <cache-id>
By default, no Elastic File Cache exists. It must be explicitly created and configured.
This control does not map to specific CIS Controls but follows general AWS security best practices for encryption, network isolation, and access control.
Level 2