cis-aws-database-9-6

name	cis-aws-database-9.6
description	Ensure Security Configurations are Reviewed Regularly
category	cis-database
version	2.0.0
author	cyberstrike-official
tags	["cis","aws","database","neptune","graph-database","security-review","compliance"]
cis_id	9.6
cis_benchmark	CIS AWS Database Services Benchmark v2.0.0
tech_stack	["aws"]
cwe_ids	[]
chains_with	["cis-aws-database-9.1","cis-aws-database-9.4","cis-aws-database-9.5"]
prerequisites	[]
severity_boost	{}

9.6 Ensure Security Configurations are Reviewed Regularly (Manual)

Description

This helps by removing or updating any IAM roles, security networks, encryption settings, audit logging, and authentication. By updating or removing a few things from these lists it helps tighten security and ensures that the users do not have excessive permissions.

Rationale

Regular security reviews ensure that configurations remain aligned with current security requirements and best practices, preventing configuration drift and excessive permissions.

Impact

By updating and revising the control within our Amazon Neptune cluster it would keep the system as secure as possible.

Audit Procedure

Using AWS Console

1. Establish a Security Review Schedule:
   • Determine a regular schedule for reviewing and updating the security configuration of your Amazon Neptune environment.
   • Consider factors such as the frequency of changes, compliance requirements, and industry best practices to determine the appropriate review interval.
2. Monitor AWS Security Bulletins:
   • Stay informed about AWS security updates and announcements related to Amazon Neptune.
   • Regularly review AWS security bulletins and notifications to identify any security patches, updates, or new features relevant to your Neptune environment.
   • Take note of any security recommendations or best practices provided by AWS.
3. Review IAM Roles and Policies:
   • Access the AWS Identity and Access Management (IAM) console by navigating to IAM in the AWS Management Console.
   • Review the IAM roles and policies associated with your Neptune resources.
   • Ensure that the assigned permissions align with the principle of least privilege and reflect the current access requirements.
   • Update the IAM roles and policies as needed to adapt to changes in user access or security requirements.
4. Review Security Groups and Network ACLs:
   • Access the Amazon Neptune console by navigating to the service using the Find Services search bar or by directly accessing the console at https://console.aws.amazon.com/neptune/.
   • In the Neptune console, navigate to the Connectivity & Security or Network & Security section.
   • Review the security groups and network ACLs associated with your Neptune clusters.
   • Ensure that the inbound and outbound rules are up to date and aligned with your security requirements.
   • Remove any unnecessary or outdated rules and add new rules if required.