Step 5. Encrypt backup data and vault
Organizations increasingly need to improve their data security strategy, and they might be required to meet data protection regulations as they scale in the cloud. The correct implementation of encryption methods can provide an additional layer of protection above foundational access control mechanisms. This added layer provides a mitigation if your primary access control policies fail.
For example, if you configure overly permissive access control policies on your AWS Backup data, your key management system or process can mitigate the maximum impact of a security event. This is because there are separate authorization mechanisms to access your data and encryption key, which means that the backup data is viewable only as cipher text.
To get the most from AWS Cloud encryption, encrypt data both in transit and at rest.
To protect data in transit, AWS uses published API calls to access AWS Backup through the
network using the TLS
protocol
Encryption configuration differs depending on the resource type and backup operations across accounts or Regions. Certain resource types support the ability to encrypt your backups using a separate encryption key from the key used to encrypt the source resource. Because you are responsible for managing access controls to determine who can access your AWS Backup data or vault encryption keys and under which conditions, use the policy language offered by AWS KMS to define access controls on keys. You can also use AWS Backup Audit Manager to confirm that your backup is properly encrypted. For more information, see Encryption for backups in AWS Backup.
You can use AWS KMS