Data protection in Amazon CodeGuru Security

The AWS shared responsibility model applies to data protection in Amazon CodeGuru Security. 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 CodeGuru Security 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 captured by CodeGuru Security

CodeGuru Security stores the following to create code scans:

• Scan information, such as scan name and scan ID

• Findings and suggested remediations generated by CodeGuru Security, which include source code snippets and code suggestions

• Source code

• Metadata about scans and findings, which does not include customer information

Data retention

CodeGuru Security stores customer code for up to 10 days. Source code is transiently stored in memory until its code scan is complete. This typically lasts a few hours. When the code scan is complete, it is flushed from memory, encrypted and stored in an Amazon Simple Storage Service bucket owned by CodeGuru Security for up to 10 days, and then deleted.

Code scans, findings, and suggested remediations are currently stored indefinitely.

Encryption at rest

Data collected by Amazon CodeGuru Security is stored using Amazon Simple Storage Service and Amazon DynamoDB. The data at rest is encrypted using AWS encryption solutions by default. Amazon CodeGuru Security encrypts your data, such as code resources and generated security findings, using AWS owned encryption keys from AWS Key Management Service (AWS KMS). You don’t have to take any action to protect the AWS managed keys that encrypt your data. For more information see AWS owned keys in the AWS Key Management Service Developer Guide.

If you choose to use to protect data with customer-managed KMS keys, it is your responsibility to protect the keys that encrypt your data. For more information on customer-managed KMS keys, see Key management.

Encryption in transit

All communication between customers and CodeGuru Security and between CodeGuru Security and its downstream dependencies is protected using TLS connections that are signed using the Signature Version 4 signing process. All CodeGuru Security endpoints use SHA-256 certificates that are managed by AWS Private Certificate Authority. For more information, see Signature Version 4 signing process in the Amazon Web Services General Reference and What is AWS Private CA? in the AWS Private Certificate Authority User Guide.