Data protection in AWS Audit Manager - AWS Audit Manager

Data protection in AWS Audit Manager

The AWS shared responsibility model applies to data protection in AWS Audit Manager. As described in this model, AWS is responsible for protecting the global infrastructure that runs all of the AWS Cloud. You are responsible for maintaining control over your content that is hosted on this infrastructure. This content includes the security configuration and management tasks for the AWS services that you use. For more information about data privacy, see the Data Privacy FAQ. For information about data protection in Europe, see the AWS Shared Responsibility Model and GDPR blog post on the AWS Security Blog.

For data protection purposes, we recommend that you protect AWS account credentials and set up individual user accounts with AWS Identity and Access Management (IAM). That way each user is given only the permissions necessary to fulfill their job duties. We also recommend that you secure your data in the following ways:

  • Use multi-factor authentication (MFA) with each account.

  • Use SSL/TLS to communicate with AWS resources. We recommend TLS 1.2 or later.

  • Set up API and user activity logging with AWS CloudTrail.

  • Use AWS encryption solutions, along with all default security controls within AWS services.

  • Use advanced managed security services such as Amazon Macie, which assists in discovering and securing personal data that is stored in Amazon S3.

  • If you require FIPS 140-2 validated cryptographic modules when accessing AWS through a command line interface or an API, use a FIPS endpoint. For more information about the available FIPS endpoints, see Federal Information Processing Standard (FIPS) 140-2.

We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form fields such as a Name field. This includes when you work with Audit Manager or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form fields used for names may be used for billing or diagnostic logs. If you provide a URL to an external server, we strongly recommend that you do not include credentials information in the URL to validate your request to that server.

In addition to the recommendation above, we recommend specifically that AWS Audit Manager customers don't include sensitive identifying information in free-form fields when creating assessments, custom controls, custom frameworks, and delegation comments.

Encryption at rest

To encrypt data at rest, AWS Audit Manager uses server-side encryption with AWS managed keys for all its data stores and logs.

Your data is encrypted under a customer managed key or an AWS owned key, depending on your selected settings. If you don’t provide a customer managed key, AWS Audit Manager uses an AWS owned key to encrypt your content. All service metadata in DynamoDB and Amazon S3 in Audit Manager is encrypted using an AWS owned key.

AWS Audit Manager encrypts data as follows:

  • Service metadata stored in Amazon S3 is encrypted under an AWS owned key using SSE-KMS.

  • Service metadata stored in DynamoDB is server side encrypted using KMS and an AWS owned key.

  • Your content stored in DynamoDB is client-side encrypted using either a customer managed key or an AWS owned key. The KMS key is based on your chosen settings.

  • Your content stored in Amazon S3 in AWS Audit Manager is encrypted using SSE-KMS. The KMS key is based on your selection, and could be either a customer managed key or an AWS owned key.

  • The assessment reports published to your Amazon S3 are encrypted as follows:

    • If you provided a customer managed key, your data is encrypted using SSE-KMS.

    • If you used the AWS owned key, your data is encrypted using SSE-S3.

Encryption in transit

AWS Audit Manager provides secure and private endpoints for encrypting data in transit. The secure and private endpoints allow AWS to protect the integrity of API requests to Audit Manager.

Inter-service transit

By default, all inter-service communications are protected by using Transport Layer Security (TLS) encryption.

Key management

AWS Audit Manager supports both AWS owned keys and customer managed keys for encrypting all Audit Manager resources (assessments, controls, frameworks, evidence, and assessment reports saved to Amazon S3 buckets in your accounts).

We recommend that you use a customer managed key. By doing so, you can view and manage the encryption keys that protect your data, including viewing logs of their use in AWS CloudTrail. When you choose a customer managed key, AWS Audit Manager creates a grant on the KMS key so that it can be used to encrypt your content.


After you delete or disable a KMS key that is used to encrypt AWS Audit Manager resources, you can no longer decrypt the resource that was encrypted under that KMS key, which means that data becomes unrecoverable.

Deleting a KMS key in AWS Key Management Service (AWS KMS) is destructive and potentially dangerous. For more information about deleting KMS keys, see Deleting AWS KMS keys in the AWS Key Management Service User Guide.

You can specify your encryption settings when you enable AWS Audit Manager using the AWS Management Console, API, or AWS Command Line Interface (AWS CLI). For more information, see Enable AWS Audit Manager.

You can review and change these settings at any time by choosing Settings in the left navigation pane of AWS Audit Manager.

  • To use the AWS owned key provided by AWS Audit Manager, clear Customize encryption settings (advanced).

  • To use your own customer managed key, select Customize encryption settings (advanced). You can then choose an existing KMS key, or create a new one.

For more information about how to change this setting, see Data encryption.

For more information about how to set up customer managed keys, see Creating keys in the AWS Key Management Service User Guide.