Cloud Defense Logo

Products

Solutions

Company

Book A Live Demo

Rule: EBS Volumes in Backup Plan

Ensure EBS volumes are included in a backup plan for system and information integrity.

RuleEBS volumes should be in a backup plan
FrameworkNIST 800-53 Revision 5
Severity
High

Rule Description

The rule requires that EBS (Elastic Block Store) volumes should be included in a backup plan in accordance with the NIST (National Institute of Standards and Technology) 800-53 revision 5 framework. This ensures that data stored on EBS volumes is regularly backed up to protect against data loss, corruption, or unauthorized access.

Troubleshooting Steps (if applicable)

  1. 1.
    Validate EBS Volume Configuration: Check if the EBS volumes are properly configured and attached to the instances that require backup.
  2. 2.
    Verify Backup Schedule: Confirm that the backup plan includes a suitable schedule for backing up the EBS volumes. Ensure it aligns with the defined RPO (Recovery Point Objective) and RTO (Recovery Time Objective) requirements of the system.
  3. 3.
    Review Backup Frequency: Ensure that the backup plan specifies an appropriate frequency for EBS volume backups based on the criticality and volume of data changes.
  4. 4.
    Check Backup Retention: Validate that the backup plan defines a retention policy for EBS volume backups to retain them for an adequate period. Consider compliance, legal, and business requirements when determining the retention period.
  5. 5.
    Evaluate Backup Storage: Confirm that the backup plan designates a secure and durable storage location for EBS volume backups. This can be AWS S3 (Simple Storage Service) or another suitable backup repository.
  6. 6.
    Verify Backup Encryption: Ensure that the backup plan includes encryption of EBS volume backups to protect data confidentiality.
  7. 7.
    Validate Backup Monitoring: Check if the backup plan has appropriate monitoring mechanisms in place to verify the successful completion of EBS volume backups and promptly resolve any backup failures.

Necessary Codes (if applicable)

There are no specific codes associated with this rule. However, you may require AWS CLI commands for managing backup plans and EBS volumes.

Step-by-step Guide for Remediation

  1. 1.
    Identify the EBS volumes that need to be included in the backup plan.
  2. 2.
    Open the AWS Management Console or use the AWS CLI for the following steps.
  3. 3.
    Create a Backup Vault: If you don't have a backup vault, create one using the AWS Backup service. This will serve as the storage location for EBS volume backups.
  4. 4.
    Define a Backup Plan: Create a backup plan that includes the EBS volumes you identified earlier. Specify the backup frequency, retention period, backup window, and encryption settings as per your requirements and compliance needs.
  5. 5.
    Assign EBS Volumes to the Backup Plan: Associate the identified EBS volumes with the backup plan. This can be done by tagging the EBS volumes with the appropriate backup plan name or using the AWS Backup console/CLI/API to assign the volumes to the plan.
  6. 6.
    Test the Backup: Trigger a backup manually or wait for the next scheduled backup to confirm that the EBS volumes are being backed up successfully.
  7. 7.
    Monitor Backup Status: Regularly monitor the backup status of the EBS volumes through the AWS Backup service or custom monitoring tools. Address any backup failures promptly.
  8. 8.
    Periodically Review and Update the Backup Plan: As the system requirements change or new EBS volumes are added, review and update the backup plan accordingly to ensure comprehensive coverage.

Note: Refer to the AWS Backup documentation for specific CLI commands and options for backup plan configuration and management.

Is your System Free of Underlying Vulnerabilities?
Find Out Now