Menu
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-aws-database-4-9La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans 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
Basé sur la classification professionnelle SOC
Affichage de SKILL.md
| name | cis-aws-database-4.9 |
| description | Ensure Database has Backup enabled |
| category | cis-database |
| version | 2.0.0 |
| author | cyberstrike-official |
| tags | ["cis","aws","database","dynamodb","backup","pitr","disaster-recovery"] |
| cis_id | 4.9 |
| cis_benchmark | CIS AWS Database Services Benchmark v2.0.0 |
| tech_stack | ["aws"] |
| cwe_ids | [] |
| chains_with | ["cis-aws-database-4.8"] |
| prerequisites | [] |
| severity_boost | {} |
Ensure your DynamoDB tables have backups enabled to protect against accidental data loss or corruption. This can be achieved in two ways: by enabling Point-in-Time Recovery (PITR), which provides continuous backups for up to 35 days, and by configuring on-demand backups that can be automated using the AWS Backup service.
Backups are essential for restoring data after accidental deletions, application errors or malicious events. Enabling both continuous and scheduled backups maximizes data resilience while meeting recovery point objectives (RPO) and compliance mandates.
Without backups, data loss can be permanent which can lead to business disruption and potential regulatory penalties. Enabling backup provides assurance of data availability and accelerates recovery from incidents, supporting overall system reliability.
1. Check if Point-in-Time Recovery (PITR) is enabled
1.1 Log in to the AWS Management Console. 1.2 Navigate to DynamoDB in the AWS Services menu.
2. Check if automated backups are enabled via AWS Backup Service
2.1 Check if Table is Assigned to a Backup Plan
aws backup list-backup-plans --query "BackupPlansList[].BackupPlanName" --output table
aws backup list-backup-selections --backup-plan-id <your-backup-plan-id> --query "BackupSelections[].SelectionId" --output text
aws backup get-backup-selection --backup-plan-id <your-backup-plan-id> --selection-id <selection-id> --query "BackupSelection.Resources" --output text
If your table ARN appears in any selection, it is protected by the backup plan.
2.2 Verify Backup Plan Configuration
aws backup get-backup-plan --backup-plan-id <your-backup-plan-id>
Look for the "Lifecycle" fields in each backup rule:
Summary:
PITR is enabled on all critical DynamoDB tables and AWS Backup plans are configured with appropriate retention periods and schedules.
1. Create Backup Plan with 2 Rules (Continuous and Scheduled Snapshots)
aws backup create-backup-plan --backup-plan '{
"BackupPlanName": "<BackupPlanName>",
"Rules": [
{
"RuleName": "Continuous-PITR",
"TargetBackupVaultName": "Default",
"ScheduleExpression": "cron(0 * * * ? *)",
"StartWindowMinutes": 60,
"CompletionWindowMinutes": 180,
"Lifecycle": { "DeleteAfterDays": 35 },
"RecoveryPointTags": { "BackupType": "Continuous" },
"EnableContinuousBackup": true
},
{
"RuleName": "Scheduled-OnDemand-Snapshots",
"TargetBackupVaultName": "Default",
"ScheduleExpression": "cron(0 3 ? * SUN *)",
"StartWindowMinutes": 120,
"CompletionWindowMinutes": 360,
"Lifecycle": { "DeleteAfterDays": 90 },
"RecoveryPointTags": { "BackupType": "OnDemand" }
}
]
}'
This command outputs the BackupPlanId necessary for the next step.
2. Assign DynamoDB Table to the Backup Plan
Replace with the ID from Step 1 and with your DynamoDB table ARN.
aws backup create-backup-selection \
--backup-plan-id <BackupPlanId> \
--backup-selection '{
"SelectionName": "DynamoDBTableSelection",
"IamRoleArn": "arn:aws:iam::<account-id>:role/AWSBackupServiceRolePolicyForBackup",
"Resources": ["<TableArn>"]
}'
These commands create a centralized backup plan with continuous and scheduled snapshot backups, then assign your DynamoDB table as a resource for backup.
By default, PITR is not enabled on DynamoDB tables and no AWS Backup plans are configured.
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 11.2 Perform Automated Backups | x | x | x |
Level 1 | Manual