OpenParable
Skip to content
← Back to skills

Cis AWS Database 9.3

DevOps & Security
cis-aws-database-9.3

Cis AWS Database 9.3 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure Data in Transit is Encrypted

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_AWS_Database_Services_Benchmark_v2.0.0/cis-aws-database-9.3/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aws-database-9-3, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

9.3 Ensure Data in Transit is Encrypted (Manual)

Description

Enabling encryption in transit helps that the data is protected when it is moving from one location to another.

Rationale

Encryption in transit ensures data transmitted between clients and Neptune remains confidential and protected from interception.

Impact

If an unauthorized user steals the data, it would be unreadable for them because a key would be required to decrypt the message into plaintext.

Audit Procedure

Using AWS Console

  1. Sign into the AWS Management Console at https://console.aws.amazon.com/ with your AWS account credentials.
  2. Open the Amazon Neptune Console - Navigate to the service using the Find Services search bar or by directly accessing the console at https://console.aws.amazon.com/neptune/.
  3. Select the Neptune Cluster:
    • Choose the Amazon Neptune cluster for which you want to implement encryption in transit.
    • Click on the cluster name to access its details page.
  4. Enable SSL/TLS Encryption:
    • In the cluster details page, navigate to the Configuration or Encryption in Transit section.
    • Under Encryption in Transit, ensure that the Enable option is selected.
    • Optionally, you can also select the Enforce option to require SSL/TLS encryption for all client connections to the Neptune cluster.
    • Click Apply Changes to enable SSL/TLS encryption for the Neptune cluster.
  5. Update Client Applications:
    • When connecting to the Neptune cluster, update your client applications to establish an SSL/TLS-encrypted connection.
    • Consult your client drivers or libraries documentation or configuration settings to enable SSL/TLS encryption.
    • Configure the necessary SSL/TLS settings, such as specifying the SSL/TLS certificate to use.
  6. Verify Encryption in Transit:
    • Test the connection to the Neptune cluster from your client application.
    • Ensure that the connection is established using SSL/TLS encryption.
    • Verify that all data transmitted between your client applications and the Neptune cluster is encrypted in transit.

Expected Result

SSL/TLS encryption in transit should be enabled (and preferably enforced) for all connections to the Neptune cluster.

Remediation

Using AWS Console

Follow the audit steps above to enable and enforce SSL/TLS encryption in transit for your Neptune cluster.

Default Value

Neptune supports SSL/TLS encryption in transit. It should be explicitly enabled and enforced for all client connections.

References

  1. https://aws.amazon.com/products/databases/

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v83.10 Encrypt Sensitive Data in Transitxx
v714.4 Encrypt All Sensitive Information in Transitxx

Profile

Level 1 | Manual