Data protection in AWS Diagnostic Tools - AWS Diagnostic Tools
Data encryptionInternetwork privacy

Data protection in AWS Diagnostic Tools

The AWS shared responsibility model applies to data protection in Diagnostic Tools. 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 Diagnostic Tools 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

AWS Diagnostic Tools data is encrypted in transit and at rest. When you submit data to Diagnostic Tools, it encrypts the data as it receives and stores it. When you retrieve data from Diagnostic Tools, it transmits the data to you by using current security protocols. Additionally, when you run a tool, the output of the Diagnostic Tools service encrypts the tool output generated by the service.

Encryption at rest

Diagnostic Tools encrypts all the data that it stores for you. This includes configuration data, user and endpoint data, analytics data, and any data that you add or import into Diagnostic Tools. To encrypt your data, Diagnostic Tools uses internal AWS Key Management Service (AWS KMS) keys that the service owns and maintains. We rotate these keys on a regular basis. For information about AWS KMS, see the AWS Key Management Service Developer Guide.

Encryption in transit

Diagnostic Tools uses HTTPS and Transport Layer Security (TLS) 1.2 or later to communicate with your clients and applications. To communicate with other AWS services, Diagnostic Tools uses HTTPS and TLS 1.2. In addition, when you create and manage Diagnostic Tools resources by using the console, an AWS SDK, or the AWS Command Line Interface, all communications are secured using HTTPS and TLS 1.2.

Key management

Diagnostic Tools uses HTTPS and Transport Layer Security (TLS) 1.2 or later to communicate with your clients and applications. To communicate with other AWS services, Diagnostic Tools uses HTTPS and TLS 1.2. In addition, when you create and manage Diagnostic Tools resources by using the console, an AWS SDK, or the AWS Command Line Interface, all communications are secured using HTTPS and TLS 1.2.

Internetwork privacy

You can use Amazon Virtual Private Cloud (Amazon VPC) to create boundaries between resources in your managed nodes and control traffic between them, your on-premises network, and the internet. For details, see Create VPC endpoints..

For more information about Amazon Virtual Private Cloud security, see Internetwork traffic privacy in Amazon VPC in the Amazon VPC User Guide.