Cloud Defense Logo

Products

Solutions

Company

Book A Live Demo

Rule: DynamoDB Tables in Backup Plan

This rule ensures that DynamoDB tables are included in a backup plan to prevent data loss.

RuleDynamoDB tables should be in a backup plan
FrameworkSOC 2
Severity
Medium

DynamoDB Backup Plan for SOC 2

Description:

In order to comply with SOC 2 (Service Organization Control 2) requirements, it is essential to have a backup plan in place for your DynamoDB tables. Implementing a thorough backup plan helps ensure the availability and integrity of your data in case of accidental deletion, system failures, or other unexpected incidents.

Troubleshooting Steps:

There are no specific troubleshooting steps for this policy. However, if you encounter any issues while configuring or managing backup plans, it is recommended to consult the official AWS documentation or reach out to AWS support for assistance.

Necessary Codes:

No specific codes are required for this policy. However, you can utilize AWS SDKs or AWS Command Line Interface (CLI) commands to automate backup plan configurations.

Step-by-Step Guide for Remediation:

  1. 1.

    Identify Critical DynamoDB Tables: Determine which DynamoDB tables contain critical data that require regular backups. Consider factors such as data significance, business-criticality, compliance requirements, and regulatory obligations.

  2. 2.

    Define Backup Frequency and Retention Period: Establish a backup frequency and retention period based on your specific needs and compliance requirements. Consider factors such as recovery point objectives (RPO) and recovery time objectives (RTO).

  3. 3.

    Configure AWS Backup Service:

    a. Create a Backup Vault: Use the AWS Management Console or AWS CLI to create a backup vault. The backup vault serves as a centralized location for storing backups.

    b. Create a Backup Plan: Utilize AWS Backup service to create a backup plan. Specify the DynamoDB tables to be included, backup frequency, retention period, and any desired lifecycle rules for archive transfers or deletion.

    c. Apply Tags (Optional): If required, apply tags to the backup plan for better management and organization.

  4. 4.

    Validate Backup Plan Configuration: Review the backup plan configuration to ensure it aligns with your specified requirements. Double-check the DynamoDB table selections, frequency, retention period, and any additional policies applied.

  5. 5.

    Monitor Backup Plan Execution: Regularly monitor the execution of the backup plan to ensure its successful completion. Utilize AWS Backup monitoring tools and services to stay informed about backup status, potential failures, or any inconsistencies.

  6. 6.

    Periodically Test Restores: Perform regular restore tests to validate the effectiveness of your backup plan. Test the restoration process for both individual items and entire tables. This step ensures that backups are accurate and can be relied upon in case of emergencies.

  7. 7.

    Periodically Review and Update: Regularly review and update your backup plan configuration. Consider any changes in compliance requirements, business needs, or changes to DynamoDB table usage. Adjust backup frequency or retention periods as necessary.

Conclusion:

Creating and maintaining a backup plan for DynamoDB tables is crucial for SOC 2 compliance. It ensures the availability and integrity of data, reducing the risk of data loss. By implementing this policy, you can safeguard your business and meet the necessary compliance standards.

Is your System Free of Underlying Vulnerabilities?
Find Out Now