Check ID:
Provider: OpenStack
Service:
Severity: MEDIUM
Categories:
Resource type:
blockstorage_volume_backup_existsProvider: OpenStack
Service:
blockstorageSeverity: MEDIUM
Categories:
forensics-readyResource type:
OS::Cinder::VolumeWhat this check verifies
OpenStack block storage volumes are evaluated to verify that at least one backup exists. Volume backups provide disaster recovery capability by storing volume data in a separate storage backend (e.g., Swift or Ceph). Without backups, data loss from volume corruption, accidental deletion, or infrastructure failure is irrecoverable.Risk
Volumes without backups are vulnerable to permanent data loss from hardware failures, accidental deletion, software bugs, or ransomware attacks. Without backups, recovery from disasters requires rebuilding data from scratch, which may be impossible for stateful applications.Recommendation
Create regular backups for all block storage volumes, especially those containing critical data. Implement automated backup schedules. Use incremental backups to reduce storage costs and backup time. Test backup restoration regularly to ensure recoverability.Remediation
- CLI
- Dashboard steps
openstack volume backup create —name <backup_name> <volume_id>
References
Where this check fires
This check runs on every scheduled scan against your OpenStack account. Findings appear at Cloud Security → Findings filterable byCheck ID = blockstorage_volume_backup_exists. 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 OpenStack checks