CIS 6.4: Ensure configuration of replication settings (Manual)
Profile Applicability
Description
Set up and maintain the replication settings to ensure accurate and efficient data duplication across systems. Proper configuration includes specifying source and target locations, defining replication schedules, and setting bandwidth limits to optimize performance. Regularly review and update these settings to accommodate changes in data volume and network conditions, ensuring data integrity and availability during replication processes.
Rationale
Proper configuration of replication settings is essential to ensure data consistency and availability across systems. Accurate replication schedules and bandwidth management optimize performance and prevent network congestion. Regular reviews and updates of these settings help adapt to changes in data volume and network conditions, maintaining efficient and reliable data replication processes.
Impact
Replication configuration affects:
- Data consistency across regions
- Network bandwidth utilization
- Recovery Time Objective (RTO) and Recovery Point Objective (RPO)
- Operational costs
- System performance
Audit Procedure
Via AWS Console
Access Replication Settings:
- Select "Configure and Initialize" in the AWS Elastic Disaster Recovery screen.
- You will be navigated to setup your replication settings template.
- This will create a staging area in a subnet of your choice and a replication server instance types.
- The default replication server instance type will be a t3 micro EC2 instance. This is good for normal workloads with small I/O operations.
Review EBS Configuration:
- Configure EBS encryption and volume types. This will depend on your workload requirements.
- To encrypt EBS volumes, leave the setting as "default." If you wish to make a custom encryption setting, you will need to create an AWS KMS key.
Review Security Group Configuration:
- Configure the security group to your specific needs.
- Remember what ports need to be opened on inbound / outbound traffic that was specified in previous steps.
- You can choose how you want your data routed and if you want to throttle network traffic to reserve bandwidth.
- To keep your data as secure as possible, it's recommended to get set up with a VPN or AWS direct connect, so your backups are not traveling over the public internet.
- Point in time policy defines the snapshot retention time. Because Elastic Disaster Recovery service uses incremental backups, it's not necessary to keep old copies of backups.
Launch Template:
- Now, you're ready to launch this template.
Expected Result
- Replication settings template properly configured
- Staging area created in appropriate subnet
- Replication server instance type selected (default: t3.micro for small I/O)
- EBS encryption configured (default or custom KMS key)
- EBS volume types match workload requirements
- Security groups configured with correct ports:
- Inbound TCP 1500 for replication traffic
- Outbound TCP 443 for EDR, S3, EC2 API access
- Network routing configured appropriately
- Bandwidth throttling configured if needed
- VPN or AWS Direct Connect recommended for secure transit
- Point-in-time policy configured for snapshot retention
- Incremental backup strategy implemented
Remediation
Via AWS Console
Configure Replication Template:
- Navigate to AWS Elastic Disaster Recovery service
- Select "Configure and Initialize"
- Choose staging area subnet
- Select appropriate replication server instance type
Configure EBS Settings:
- Configure EBS encryption (leave as "default" or create custom KMS key)
- Select appropriate volume types for workload requirements
Configure Security Groups:
- Configure security group rules:
- Allow inbound TCP 1500 for replication
- Allow outbound TCP 443 for EDR, S3, EC2
- Configure network routing
- Set bandwidth throttling if needed
- Implement VPN or Direct Connect for secure data transit
Configure Retention Policy:
- Set point-in-time policy for snapshot retention
- Configure incremental backup settings
Launch Configuration:
- Review all settings
- Launch the replication template
- Verify configuration is active
Default Value
By default, no replication settings are configured. Organizations must manually configure all replication parameters including staging area, instance types, encryption, security groups, and retention policies.
References
CIS Controls
| Controls Version |
Control |
IG 1 |
IG 2 |
IG 3 |
| v8 |
11.2 Perform Automated BackupsPerform automated backups of in-scope enterprise assets. Run backups weekly, or more frequently, based on the sensitivity of the data. |
● |
● |
● |
| v8 |
11.4 Establish and Maintain an Isolated Instance of Recovery DataEstablish and maintain an isolated instance of recovery data. Example implementations include, version controlling backup destinations through offline, cloud, or off-site systems or services. |
● |
● |
● |
| v7 |
10.4 Ensure Protection of BackupsEnsure that backups are properly protected via physical security or encryption when they are stored, as well as when they are moved across the network. This includes remote backups and cloud services. |
● |
● |
● |
| v7 |
10.5 Ensure Backups Have At least One Non-Continuously Addressable DestinationEnsure that all backups have at least one backup destination that is not continuously addressable through operating system calls. |
● |
● |
● |
Profile
1---2name: cis-aws-storage-6-43description: Ensure configuration of replication settings4---56# CIS 6.4: Ensure configuration of replication settings (Manual)78## Profile Applicability910- **Level:** 21112## Description1314Set up and maintain the replication settings to ensure accurate and efficient data duplication across systems. Proper configuration includes specifying source and target locations, defining replication schedules, and setting bandwidth limits to optimize performance. Regularly review and update these settings to accommodate changes in data volume and network conditions, ensuring data integrity and availability during replication processes.1516## Rationale1718Proper configuration of replication settings is essential to ensure data consistency and availability across systems. Accurate replication schedules and bandwidth management optimize performance and prevent network congestion. Regular reviews and updates of these settings help adapt to changes in data volume and network conditions, maintaining efficient and reliable data replication processes.1920## Impact2122Replication configuration affects:2324- Data consistency across regions25- Network bandwidth utilization26- Recovery Time Objective (RTO) and Recovery Point Objective (RPO)27- Operational costs28- System performance2930## Audit Procedure3132### Via AWS Console33341. **Access Replication Settings:**35 - Select "Configure and Initialize" in the AWS Elastic Disaster Recovery screen.36 - You will be navigated to setup your replication settings template.37 - This will create a staging area in a subnet of your choice and a replication server instance types.38 - The default replication server instance type will be a t3 micro EC2 instance. This is good for normal workloads with small I/O operations.39402. **Review EBS Configuration:**41 - Configure EBS encryption and volume types. This will depend on your workload requirements.42 - To encrypt EBS volumes, leave the setting as "default." If you wish to make a custom encryption setting, you will need to create an AWS KMS key.43443. **Review Security Group Configuration:**45 - Configure the security group to your specific needs.46 - Remember what ports need to be opened on inbound / outbound traffic that was specified in previous steps.47 - You can choose how you want your data routed and if you want to throttle network traffic to reserve bandwidth.48 - To keep your data as secure as possible, it's recommended to get set up with a VPN or AWS direct connect, so your backups are not traveling over the public internet.49 - Point in time policy defines the snapshot retention time. Because Elastic Disaster Recovery service uses incremental backups, it's not necessary to keep old copies of backups.50514. **Launch Template:**52 - Now, you're ready to launch this template.5354## Expected Result5556- Replication settings template properly configured57- Staging area created in appropriate subnet58- Replication server instance type selected (default: t3.micro for small I/O)59- EBS encryption configured (default or custom KMS key)60- EBS volume types match workload requirements61- Security groups configured with correct ports:62 - Inbound TCP 1500 for replication traffic63 - Outbound TCP 443 for EDR, S3, EC2 API access64- Network routing configured appropriately65- Bandwidth throttling configured if needed66- VPN or AWS Direct Connect recommended for secure transit67- Point-in-time policy configured for snapshot retention68- Incremental backup strategy implemented6970## Remediation7172### Via AWS Console73741. **Configure Replication Template:**75 - Navigate to AWS Elastic Disaster Recovery service76 - Select "Configure and Initialize"77 - Choose staging area subnet78 - Select appropriate replication server instance type79802. **Configure EBS Settings:**81 - Configure EBS encryption (leave as "default" or create custom KMS key)82 - Select appropriate volume types for workload requirements83843. **Configure Security Groups:**85 - Configure security group rules:86 - Allow inbound TCP 1500 for replication87 - Allow outbound TCP 443 for EDR, S3, EC288 - Configure network routing89 - Set bandwidth throttling if needed90 - Implement VPN or Direct Connect for secure data transit91924. **Configure Retention Policy:**93 - Set point-in-time policy for snapshot retention94 - Configure incremental backup settings95965. **Launch Configuration:**97 - Review all settings98 - Launch the replication template99 - Verify configuration is active100101## Default Value102103By default, no replication settings are configured. Organizations must manually configure all replication parameters including staging area, instance types, encryption, security groups, and retention policies.104105## References106107- [AWS Elastic Disaster Recovery Replication Settings](https://docs.aws.amazon.com/drs/latest/userguide/replication-settings.html)108- [AWS EDR Configuration Best Practices](https://docs.aws.amazon.com/drs/latest/userguide/best-practices.html)109110## CIS Controls111112| Controls Version | Control | IG 1 | IG 2 | IG 3 |113| ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- |114| v8 | 11.2 Perform Automated Backups<br/>Perform automated backups of in-scope enterprise assets. Run backups weekly, or more frequently, based on the sensitivity of the data. | ● | ● | ● |115| v8 | 11.4 Establish and Maintain an Isolated Instance of Recovery Data<br/>Establish and maintain an isolated instance of recovery data. Example implementations include, version controlling backup destinations through offline, cloud, or off-site systems or services. | ● | ● | ● |116| v7 | 10.4 Ensure Protection of Backups<br/>Ensure that backups are properly protected via physical security or encryption when they are stored, as well as when they are moved across the network. This includes remote backups and cloud services. | ● | ● | ● |117| v7 | 10.5 Ensure Backups Have At least One Non-Continuously Addressable Destination<br/>Ensure that all backups have at least one backup destination that is not continuously addressable through operating system calls. | ● | ● | ● |118119## Profile120121- Level 2