Rule: EFS File Systems Should Be in a Backup Plan
Ensure that EFS file systems are included in a backup plan for data protection.
| Rule | EFS file systems should be in a backup plan |
| Framework | NIST 800-53 Revision 5 |
| Severity | ✔ High |
Rule Description:
The NIST 800-53 Revision 5 recommends including EFS (Elastic File System) file systems in the backup plan for ensuring data protection and recovery capabilities. EFS file systems are managed by the Amazon Web Services (AWS) cloud platform and serve as scalable, fully managed file storage systems.
Including EFS file systems in your backup plan helps prevent data loss and enables the restoration of files in case of accidental deletion, corruption, or system failures. By regularly backing up your EFS file systems, you ensure business continuity and reduce the risk of data loss.
Troubleshooting Steps (if applicable):
If you encounter any issues while backing up or restoring your EFS file systems, you can follow these troubleshooting steps:
- 1.
Check EFS Permissions: Ensure that the appropriate IAM (Identity and Access Management) roles have the necessary permissions to perform backup and restore operations on EFS file systems.
- 2.
Verify EFS Mount Points: Double-check the mount points of your EFS file systems to ensure they are correctly configured. Incorrect mount points might prevent successful backup or restoration.
- 3.
Review AWS Backup Settings: Confirm that you have set up AWS Backup correctly for your EFS file systems. Ensure that the backup schedule, retention policies, and target storage locations are accurately configured.
- 4.
Monitor CloudWatch Logs: Check the CloudWatch Logs for any error messages or notifications related to EFS backup or restore operations. This can provide insights into the possible causes of failures.
- 5.
Contact AWS Support: If you have followed the above steps and are still experiencing issues, it is recommended to reach out to AWS support for further assistance. Provide them with relevant details about your backup plan, EFS file systems, and any error messages received for efficient troubleshooting.
Necessary Codes (if applicable):
Here are some example codes that can be used to implement an AWS Backup plan for EFS file systems:
Resources:
MyEFSFileSystemBackupSelection:
Type: AWS::Backup::BackupSelection
Properties:
BackupPlanId: !Ref MyBackupPlan
BackupSelection:
ListOfTags:
- ConditionKey: aws:efs:file-system-id
ConditionType: STRINGEQUALS
ConditionValue: fs-12345678
MyBackupPlan:
Type: AWS::Backup::BackupPlan
Properties:
BackupPlan:
BackupPlanName: MyEFSBackupPlan
BackupPlanRule:
RuleName: DailyBackup
TargetBackupVault:
Name: MyBackupVault
ScheduleExpression: cron(0 12 * * ? *)
Lifecycle:
DeleteAfterDays: 30
This YAML CloudFormation template creates a backup selection for a specific EFS file system with the file system's ID (
fs-12345678MyEFSBackupPlanMyBackupVaultStep-by-Step Guide for Remediation:
To ensure compliance with NIST 800-53 Revision 5 and include EFS file systems in your backup plan, follow these step-by-step instructions:
- 1.
Identify EFS File Systems: Make a list of the EFS file systems that need to be included in the backup plan. Determine the criticality of each file system to prioritize backup frequency and retention policies.
- 2.
Set Up AWS Backup: If you haven't already, enable the AWS Backup service in your AWS account. This service allows you to create, manage, and monitor backup plans for various AWS resources, including EFS file systems.
- 3.
Create a Backup Vault: In the AWS Backup console, create a backup vault to store the EFS file system backups. Choose a meaningful name for the vault that reflects its purpose.
- 4.
Configure Backup Plan: Create a backup plan that defines the schedule, retention, and target vault for EFS file system backups. Use the AWS Management Console, AWS CLI, or AWS CloudFormation to create the backup plan.
- 5.
Add Backup Rules: Within the backup plan, define backup rules specifying which EFS file systems to include, their backup frequency, and how long to retain the backups. Use tags or file system IDs to select the EFS file systems for backup.
- 6.
Enable Backup: Once the backup plan and rules are defined, enable the backup for the EFS file systems. AWS Backup will automatically create and manage backups based on the defined plan and schedule.
- 7.
Monitor Backup Operations: Regularly monitor AWS Backup operations and ensure that EFS file system backups are happening according to the specified schedule. Review backup reports and logs for any potential issues.
- 8.
Validate and Test Restorations: Periodically validate the backup and restoration process by performing test restorations. Ensure that restored files are accurate and accessible. Document any deviations or improvements required.
By following these steps, you can implement a robust backup plan for your EFS file systems and comply with the NIST 800-53 Revision 5 recommendations.