Configuring security groups benefits the user because it helps manage networks within the database and gives only certain permission for traffic that leaves and enters the database.
Rationale
Security groups act as virtual firewalls that control inbound and outbound traffic to RDS instances. Proper configuration ensures only authorized access.
Impact
Allows certain users to access the instance and it only allows them to work within that network.
Choose the Amazon RDS instance for which you want to configure security groups. Click on the instance name to access its details page.
Navigate to the Connectivity & Security Section
In the instance details page, navigate to the Connectivity & Security or "Security" section.
View and Modify Existing Security Groups
Under the Security section, you will see the existing security groups associated with the RDS instance.
Take note of the existing security groups and their inbound and outbound rules.
Create a New Security Group
If you need to create a new security group for the RDS instance
Click the Create New Security Group button.
Provide a name and description for the new security group.
Configure the inbound and outbound rules to control network traffic to and from the RDS instance.
Click "Create" to create the new security group.
Modify Security Group Rules
To modify the rules of an existing security group, click on the security group name or the Modify button next to it.
You can add, edit, or delete inbound and outbound rules on the security group details page.
Specify each rule's source IP addresses, port ranges, and protocols.
Click Save or Apply Changes to update the security group rules.
Associate Security Groups
To associate a security group with the RDS instance, navigate to the Connectivity & Security or Security section of the instance details page.
Click Modify next to the VPC security groups option.
Select the desired security groups from the list.
Click Save or Apply Changes to associate them with the RDS instance.
Verify and Test Security Group Configuration
Review the security group settings to match your network access requirements.
Test the connectivity to the RDS instance by attempting to access it from authorized IP addresses or applications.
Monitor and Update Security Groups
Regularly monitor the network traffic and access patterns to your RDS instance.
Update the security group rules as needed to reflect changes in your network access requirements.
Expected Result
Security groups should be configured with the principle of least privilege, allowing only necessary inbound traffic from trusted sources on required ports.
Remediation
Using AWS Console
Follow the audit steps above to review and configure security groups. Remove overly permissive rules (e.g., 0.0.0.0/0) and restrict access to specific IP ranges and ports.
Default Value
The default security group allows all outbound traffic and restricts inbound traffic to the same security group.
14.6 Protect Information through Access Control Lists
x
x
x
Profile
Level 1 | Manual
1---2name: cis-aws-database-3-43description: Ensure to Configure Security Groups4---56# 3.4 Ensure to Configure Security Groups (Manual)78## Description910Configuring security groups benefits the user because it helps manage networks within the database and gives only certain permission for traffic that leaves and enters the database.1112## Rationale1314Security groups act as virtual firewalls that control inbound and outbound traffic to RDS instances. Proper configuration ensures only authorized access.1516## Impact1718Allows certain users to access the instance and it only allows them to work within that network.1920## Audit Procedure2122### Using AWS Console23241. Sign into the AWS Management Console25 - Sign into the AWS Management Console at https://console.aws.amazon.com/ with your AWS account credentials.26272. Open the Amazon RDS Console28 - Navigate to the service using the `Find Services` search bar or by directly accessing the console at https://console.aws.amazon.com/rds/.29303. Select the RDS Instance31 - Choose the Amazon RDS instance for which you want to configure security groups. Click on the instance name to access its details page.32334. Navigate to the `Connectivity & Security` Section34 - In the instance details page, navigate to the `Connectivity & Security` or "Security" section.35365. View and Modify Existing Security Groups37 - Under the `Security` section, you will see the existing security groups associated with the RDS instance.38 - Take note of the existing security groups and their inbound and outbound rules.39406. Create a New Security Group41 - If you need to create a new security group for the RDS instance42 - Click the `Create New Security Group` button.43 - Provide a name and description for the new security group.44 - Configure the inbound and outbound rules to control network traffic to and from the RDS instance.45 - Click "Create" to create the new security group.46477. Modify Security Group Rules48 - To modify the rules of an existing security group, click on the security group name or the `Modify` button next to it.49 - You can add, edit, or delete inbound and outbound rules on the security group details page.50 - Specify each rule's source IP addresses, port ranges, and protocols.51 - Click `Save` or `Apply Changes` to update the security group rules.52538. Associate Security Groups54 - To associate a security group with the RDS instance, navigate to the `Connectivity & Security` or `Security` section of the instance details page.55 - Click `Modify` next to the `VPC security groups` option.56 - Select the desired security groups from the list.57 - Click `Save` or `Apply Changes` to associate them with the RDS instance.58599. Verify and Test Security Group Configuration60 - Review the security group settings to match your network access requirements.61 - Test the connectivity to the RDS instance by attempting to access it from authorized IP addresses or applications.626310. Monitor and Update Security Groups64 - Regularly monitor the network traffic and access patterns to your RDS instance.65 - Update the security group rules as needed to reflect changes in your network access requirements.6667## Expected Result6869Security groups should be configured with the principle of least privilege, allowing only necessary inbound traffic from trusted sources on required ports.7071## Remediation7273### Using AWS Console7475Follow the audit steps above to review and configure security groups. Remove overly permissive rules (e.g., 0.0.0.0/0) and restrict access to specific IP ranges and ports.7677## Default Value7879The default security group allows all outbound traffic and restricts inbound traffic to the same security group.8081## References82831. https://aws.amazon.com/products/databases/8485## CIS Controls8687| Controls Version | Control | IG 1 | IG 2 | IG 3 |88| ---------------- | ----------------------------------------------------- | ---- | ---- | ---- |89| v8 | 3.3 Configure Data Access Control Lists | x | x | x |90| v7 | 14.6 Protect Information through Access Control Lists | x | x | x |9192## Profile9394Level 1 | Manual
Run npx skillmds@latest add cyberstrikeus/cis-aws-database-3-4 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 to Configure Security Groups 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.