Data protection in AWS Private Certificate Authority - AWS Private Certificate Authority
Storage and security compliance of AWS Private CA private keysData encryption in AWS Private CA Connector for Active Directory

Data protection in AWS Private Certificate Authority

The AWS shared responsibility model applies to data protection in AWS Private Certificate Authority. 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 AWS Private CA 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.

Storage and security compliance of AWS Private CA private keys

The private keys for private CAs are stored in AWS managed hardware security modules (HSMs). The HSMs comply with FIPS PUB 140-2 Level 3 Security Requirements for Cryptographic Modules.

Data encryption in AWS Private CA Connector for Active Directory

AWS Private CA Connector for AD stores customer configuration data regarding connectors, templates, directory registrations, service principal names, and template group access control entries. This data is encrypted in transit and at rest. Information about certificates issued through Connector for AD can be discovered using the GetCertificate action in the AWS Private CA API. No information regarding the certificates issued, or regarding the client or machine requesting a certificate, is stored by AWS.