8.3 Ensure Data at Rest and in Transit is Encrypted (Manual)
Description
Once a user is logged in to their AWS account and has access to their Amazon Keyspaces they are encouraged to choose from the following two options to encrypt their data. Depending on which key they select for encryption at rest would store the data according to their preference. For encryption in transit the user is also encouraged to choose from two options depending on if the data needs to be encrypted during transit.
Rationale
Encryption at rest and in transit protects data from unauthorized access whether stored or being transferred between locations.
Impact
Prevents any unauthorized user from accessing the database and provides security when transferring the data from one location to another.
Open the Amazon Keyspaces Console - Navigate to the service using the Find Services search bar or by directly accessing the console at https://console.aws.amazon.com/keyspaces/.
Select the Keyspace:
Choose the Keyspace (database) for which you want to enable encryption at rest and in transit.
Click on the Keyspace name to access its details page.
Enable Encryption at Rest:
In the Keyspace details page, click on the Configuration tab.
Under the Encryption section, locate the "Encryption at Rest" option.
Click on Edit.
Select the desired encryption setting:
Default Encryption: Choose this option to use the default AWS-managed key for encryption at rest. Amazon Keyspaces automatically encrypts your data using this default key.
Customer Managed Key (CMK): Choose this option if you want to use your own AWS Key Management Service (KMS) customer-managed key for encryption. Select the appropriate CMK from the dropdown menu.
Click "Save" to enable encryption at rest for the Keyspace.
Enable Encryption in Transit:
In the Keyspace details page, click on the Configuration tab.
Under the Encryption section, locate the "Encryption in Transit" option.
Click on Edit.
Select the desired encryption setting:
Encryption in Transit Enabled: Choose this option to enable encryption in transit for data transmitted between your client applications and Amazon Keyspaces. Keyspaces support Transport Layer Security (TLS) encryption for secure communication.
Encryption in Transit Disabled: Choose this option if you do not require encryption in transit.
Click "Save" to enable encryption in transit for the Keyspace.
Verify Encryption Status:
Wait a few minutes for the changes to propagate and the encryption settings to take effect.
Refresh the Keyspace details page to see the updated encryption status.
Verify that encryption at rest and in transit are enabled for the Keyspace.
Expected Result
Encryption at rest should be enabled (using either AWS-managed or customer-managed KMS key) and encryption in transit should be enabled with TLS.
Remediation
Using AWS Console
Follow the audit steps above to enable encryption at rest and in transit for your Amazon Keyspaces.
Default Value
Amazon Keyspaces encrypts data at rest by default using AWS-managed keys. Encryption in transit via TLS is supported but requires client configuration.
1---2name: cis-aws-database-8-33description: Ensure Data at Rest and in Transit is Encrypted4---56# 8.3 Ensure Data at Rest and in Transit is Encrypted (Manual)78## Description910Once a user is logged in to their AWS account and has access to their Amazon Keyspaces they are encouraged to choose from the following two options to encrypt their data. Depending on which key they select for encryption at rest would store the data according to their preference. For encryption in transit the user is also encouraged to choose from two options depending on if the data needs to be encrypted during transit.1112## Rationale1314Encryption at rest and in transit protects data from unauthorized access whether stored or being transferred between locations.1516## Impact1718Prevents any unauthorized user from accessing the database and provides security when transferring the data from one location to another.1920## Audit Procedure2122### Using AWS Console23241. Sign in to the AWS Management Console at https://console.aws.amazon.com/ with your AWS account credentials.252. Open the Amazon Keyspaces Console - Navigate to the service using the `Find Services` search bar or by directly accessing the console at https://console.aws.amazon.com/keyspaces/.263. Select the Keyspace:27 - Choose the Keyspace (database) for which you want to enable encryption at rest and in transit.28 - Click on the Keyspace name to access its details page.294. Enable Encryption at Rest:30 - In the Keyspace details page, click on the `Configuration` tab.31 - Under the `Encryption` section, locate the "Encryption at Rest" option.32 - Click on `Edit`.33 - Select the desired encryption setting:34 - Default Encryption: Choose this option to use the default AWS-managed key for encryption at rest. Amazon Keyspaces automatically encrypts your data using this default key.35 - Customer Managed Key (CMK): Choose this option if you want to use your own AWS Key Management Service (KMS) customer-managed key for encryption. Select the appropriate CMK from the dropdown menu.36 - Click "Save" to enable encryption at rest for the Keyspace.375. Enable Encryption in Transit:38 - In the Keyspace details page, click on the `Configuration` tab.39 - Under the `Encryption` section, locate the "Encryption in Transit" option.40 - Click on `Edit`.41 - Select the desired encryption setting:42 - Encryption in Transit Enabled: Choose this option to enable encryption in transit for data transmitted between your client applications and Amazon Keyspaces. Keyspaces support Transport Layer Security (TLS) encryption for secure communication.43 - Encryption in Transit Disabled: Choose this option if you do not require encryption in transit.44 - Click "Save" to enable encryption in transit for the Keyspace.456. Verify Encryption Status:46 - Wait a few minutes for the changes to propagate and the encryption settings to take effect.47 - Refresh the Keyspace details page to see the updated encryption status.48 - Verify that encryption at rest and in transit are enabled for the Keyspace.4950## Expected Result5152Encryption at rest should be enabled (using either AWS-managed or customer-managed KMS key) and encryption in transit should be enabled with TLS.5354## Remediation5556### Using AWS Console5758Follow the audit steps above to enable encryption at rest and in transit for your Amazon Keyspaces.5960## Default Value6162Amazon Keyspaces encrypts data at rest by default using AWS-managed keys. Encryption in transit via TLS is supported but requires client configuration.6364## References65661. https://aws.amazon.com/products/databases/6768## CIS Controls6970| Controls Version | Control | IG 1 | IG 2 | IG 3 |71| ---------------- | ------------------------------------------------- | ---- | ---- | ---- |72| v8 | 3.10 Encrypt Sensitive Data in Transit | | x | x |73| v8 | 3.11 Encrypt Sensitive Data at Rest | | x | x |74| v7 | 14.4 Encrypt All Sensitive Information in Transit | | x | x |75| v7 | 14.8 Encrypt Sensitive Information at Rest | | | x |7677## Profile7879Level 1 | Manual
Run npx skillmds@latest add cyberstrikeus/cis-aws-database-8-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Ensure Data at Rest and in Transit is Encrypted It is listed under DevOps & Infra on SkillMD.
SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
cyberstrikeus (@cyberstrikeus) published this skill. Their other Agent Skills are listed on their SkillMD profile.