Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
neptune_cluster_backup_enabledProvider: AWS
Service:
neptuneSeverity: MEDIUM
Categories:
resilienceResource type:
AwsRdsDbClusterWhat this check verifies
Neptune DB cluster automated backup is enabled and retention days are more than the required minimum retention period (default to7 days).
Risk
Insufficient backup retention reduces the ability to recover from data corruption, accidental deletion, or ransomware, impacting availability and integrity.- Prevents point-in-time recovery to required dates
- Increases downtime, irreversible data loss, and compliance violations
Recommendation
Ensure automated backups are enabled and retention aligns with your RPO/RTO and regulatory requirements (at least7 days).
- Define backup lifecycle and storage retention policies
- Regularly test restore procedures and monitor backup health
- Incorporate backups into Disaster Recovery and retention governance
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws neptune modify-db-cluster —db-cluster-identifier <DB_CLUSTER_ID> —backup-retention-period 7 —apply-immediately
References
- https://docs.aws.amazon.com/securityhub/latest/userguide/neptune-controls.html#neptune-5
- https://trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/Neptune/sufficient-backup-retention-period.html
- https://support.icompaas.com/support/solutions/articles/62000233327-check-for-neptune-clusters-backup-retention-period
- https://asecure.cloud/a/p_configrule_neptune_cluster_backup_retention_check/
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = neptune_cluster_backup_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks