Data protection in Amazon DataZone - Amazon DataZone
Data encryptionEncryption in transitInter-network traffic privacy

Data protection in Amazon DataZone

The AWS shared responsibility model applies to data protection in Amazon DataZone. 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. You are also responsible for 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 users with AWS IAM Identity Center or 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 require TLS 1.2 and recommend TLS 1.3.

  • Set up API and user activity logging with AWS CloudTrail. For information about using CloudTrail trails to capture AWS activities, see Working with CloudTrail trails in the AWS CloudTrail User Guide.

  • 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 sensitive data that is stored in Amazon S3.

  • If you require FIPS 140-3 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-3.

We strongly recommend that you never put confidential or sensitive information, such as your customers' email addresses, into tags or free-form text fields such as a Name field. This includes when you work with Amazon DataZone or other AWS services using the console, API, AWS CLI, or AWS SDKs. Any data that you enter into tags or free-form text 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.

Data encryption

When granting permissions, you decide who is getting what permissions to which Amazon DataZone resources. You enable specific actions that you want to allow on those resources. Therefore, you should grant only the permissions that are required to perform a task. Implementing least privilege access is fundamental in reducing security risk and the impact that could result from errors or malicious intent.

Encryption at rest

Amazon DataZone encrypts all your data by default with an AWS Key Management Service (AWS KMS) key that AWS owns and manages for you. You can also encrypt the data stored in the Amazon DataZone catalog using keys that you manage with AWS KMS.

When you create a domain in Amazon DataZone, you can provide encryption settings by selecting the checkbox next to Customize encryption settings (advanced) under Data Encryption, and providing a KMS key.

Encryption in transit

Amazon DataZone uses Transport Layer Security (TLS) and client-side encryption for encryption in transit. Communication with Amazon DataZone is always done over HTTPS so your data is always encrypted in transit.

Inter-network traffic privacy

To secure connections between accounts, Amazon DataZone uses service roles and IAM roles to securely connect to customer accounts and execute operations on behalf of the customer.

Topics