Menú
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-storage-6-10El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
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
Basado en la clasificación ocupacional SOC
Mostrando SKILL.md
| name | cis-aws-storage-6.10 |
| description | Ensure execution of a Disaster Recovery Failover |
| category | cis-storage-services |
| version | 1.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","storage","edr","disaster-recovery","failover","recovery","business-continuity"] |
| cis_id | 6.10 |
| cis_benchmark | CIS AWS Storage Services Benchmark v1.0.0 |
| tech_stack | ["aws"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-storage-6.8","cis-aws-storage-6.9","cis-aws-storage-6.11"] |
| prerequisites | [] |
| severity_boost | {} |
Execute a comprehensive disaster recovery failover to transition operations from the primary system to a backup system during disruptions. This process includes ensuring all critical data and applications are accurately replicated to the backup site for seamless operational continuity. Regularly test and document the failover process to identify and resolve any issues, maintaining readiness to minimize downtime and data loss during real disasters.
Executing a comprehensive disaster recovery failover is essential to ensure operational continuity during disruptions. Accurate replication of critical data and applications to the backup site guarantees that business operations can continue seamlessly. Regular testing and documentation of the failover process help identify and resolve potential issues, maintaining a state of readiness and minimizing downtime and data loss in actual disaster scenarios.
Failover execution requires:
Benefits:
Follow the steps where we learned how to conduct a recovery drill with the below modifications:
Select Server for Failover:
Choose Recovery Point:
Initiate Recovery Job:
Note: You can use the job details to monitor the progress and status of the recovery job.
Verify Completion:
Test Recovery Instance:
Prepare for Failover:
Initiate Failover:
Monitor Progress:
Verify Completion:
Test Recovery Instance:
Document Results:
Implement a disaster recovery failover.
By default, no failover procedures are configured or automated. Organizations must manually plan, test, and execute failover operations.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 11.4 Establish and Maintain an Isolated Instance of Recovery Data Establish and maintain an isolated instance of recovery data. Example implementations include, version controlling backup destinations through offline, cloud, or off-site systems or services. | ● | ● | ● |
| v8 | 11.5 Test Data Recovery Test backup recovery quarterly, or more frequently, for a sampling of in-scope enterprise assets. | ● | ● | |
| v7 | 10.4 Ensure Protection of Backups Ensure that backups are properly protected via physical security or encryption when they are stored, as well as when they are moved across the network. This includes remote backups and cloud services. | ● | ● | ● |
| v7 | 10.5 Ensure Backups Have At least One Non-Continuously Addressable Destination Ensure that all backups have at least one backup destination that is not continuously addressable through operating system calls. | ● | ● | ● |
