OpenParable
Skip to content
← Back to skills

Cis AWS Database 6.1

DevOps & Security
cis-aws-database-6.1

Cis AWS Database 6.1 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 Network Security is Enabled

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-6.1/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aws-database-6-1, 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.

6.1 Ensure Network Security is Enabled (Manual)

Description

Ensure network security is enabled for Amazon MemoryDB for Redis clusters by deploying them within a secure Virtual Private Cloud (VPC), configuring appropriate security groups, network ACLs, and VPC endpoints.

Rationale

Network security controls are essential to isolate Amazon MemoryDB clusters from unauthorized access and ensure that only trusted sources can communicate with the clusters.

Impact

Properly configured network security settings ensure that MemoryDB clusters are protected from unauthorized network access while allowing legitimate traffic.

Audit Procedure

Using AWS Console

  1. Create or Select a Virtual Private Cloud (VPC)

    • Sign in to the AWS Management Console and open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
    • Create a new VPC or select an existing VPC where you want to deploy your Amazon MemoryDB clusters.
  2. Configure Subnets

    • In the VPC console, navigate to Subnets in the left-side menu.
    • Create or select the subnets within your VPC where you want to deploy your Amazon MemoryDB clusters.
    • Ensure you have private subnets to isolate your MemoryDB clusters from the public internet.
  3. Define Security Groups

    • In the VPC console, navigate to Security Groups in the left-side menu.
    • Create a new security group or select an existing one for your Amazon MemoryDB clusters.
    • Configure inbound and outbound rules in the security group to control traffic access.
      • Allow inbound access only from trusted sources, such as specific IP ranges or security groups, on the necessary ports used by MemoryDB.
      • Define outbound rules based on your requirements, allowing outbound traffic to necessary destinations or ports.
    • Associate the security group with your Amazon MemoryDB clusters.
  4. Configure Network Access Control Lists (ACLs)

    • In the VPC console, navigate to Network ACLs in the left-side menu.
    • Create or select the network ACLs associated with the subnets used by your Amazon MemoryDB clusters.
    • Configure inbound and outbound rules in the network ACLs to control traffic access.
      • Define rules based on your security requirements, allowing only necessary protocols, ports, and IP ranges.
      • Deny unnecessary or unwanted traffic.
    • Associate the network ACLs with the subnets used by your Amazon MemoryDB clusters.
  5. Configure VPC Endpoints

    • In the VPC console, navigate to Endpoints in the left-side menu.
    • Create or select the VPC endpoints required for Amazon MemoryDB.
      • If you need to access MemoryDB from within your VPC, create a VPC endpoint for Amazon MemoryDB to connect your applications securely.
      • If you need to access MemoryDB from another VPC or on-premises network, set up VPC peering or a transit gateway to establish a secure connection.
  6. Verify Connectivity and Test

    • Launch an Amazon EC2 instance within the same VPC and subnet as your Amazon MemoryDB clusters or use an existing one.
    • Connect to the EC2 instance using SSH or other remote access methods.
    • Test the connectivity to your Amazon MemoryDB clusters by trying to connect to them using the appropriate client or utility.
    • Verify that the network security settings allow the necessary traffic and deny unauthorized access.

Expected Result

MemoryDB clusters are deployed in private subnets within a VPC, with security groups restricting access to only trusted sources and necessary ports.

Remediation

Using AWS Console

Follow the same steps as the audit procedure to configure VPC, subnets, security groups, network ACLs, and VPC endpoints for your Amazon MemoryDB clusters.

Default Value

Amazon MemoryDB clusters must be deployed within a VPC. Default security group rules may allow all outbound traffic.

References

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

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v812.2 Establish and Maintain a Secure Network ArchitectureXX
v711.7 Manage Network Infrastructure Through a Dedicated NetworkXX

Profile

Level 1 | Manual