aws-customer-playbook-framework

Incident Response Playbook: Public Resources Exposure - RDS

This document is provided for informational purposes only. It represents the current product offerings and practices from Amazon Web Services (AWS) as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.

© 2024 Amazon Web Services, Inc. or its affiliates. All Rights Reserved. This work is licensed under a Creative Commons Attribution 4.0 International License.

This AWS Content is provided subject to the terms of the AWS Customer Agreement available at http://aws.amazon.com/agreement or other written agreement between the Customer and either Amazon Web Services, Inc. or Amazon Web Services EMEA SARL or both.

Points of Contact

Author: Author Name
Approver: Approver Name
Last Date Approved:

Executive Summary

This playbook outlines the process to identify owners of public resources, determine who may have accessed those while they were exposed, determine impact of revoking access to the resource, and determine root cause of public accessibility.

Potential Indicators of Compromise

Objectives

Throughout the execution of the playbook, focus on the *desired outcomes*, taking notes for enhancement of incident response capabilities.

Determine:

Recover:

Enhance CAF Security Perspective components:

AWS Cloud Adoption Framework Security Perspective

Image


Response Steps

  1. [PREPARATION] Create an Asset Inventory
  2. [PREPARATION] Create an RDS Instance Inventory
  3. [PREPARATION] Establish RDS Security and Logging Checks
  4. [PREPARATION] Implement a training program to identify and assess RDS access and log analysis
  5. [PREPARATION] Identify, document, and test escalation Procedures[DETECTION AND ANALYSIS]
  6. [DETECTION AND ANALYSIS] Perform Instance Checks
  7. [DETECTION AND ANALYSIS] Review CloudTrail for RDS Public Resources
  8. [DETECTION AND ANALYSIS] Review VPC Flow Logs
  9. [DETECTION AND ANALYSIS] Review RDS Endpoint / Host Based Logs
  10. [CONTAINMENT] Contain RDS Public Exposure
  11. [ERADICATION] Delete any unrecognized or unauthorized public snapshots or databases
  12. [PREPARATION] Additional Preventative Actions: RDS Security Checks
  13. [PREPARATION] Additional Preventative Actions: Security Control Policy - RDS Encryption
  14. [PREPARATION] Additional Preventative Actions: AWS Config
  15. [PREPARATION] Additional Preventative Actions: Overall Security Posture

***The response steps follow the Incident Response Life Cycle from NIST Special Publication 800-61r2 Computer Security Incident Handling Guide

Image***

Incident Classification & Handling

Incident Handling Process

The incident response process has the following stages:

Preparation

This playbook references and integrates, where possible, with Prowler which is a command line tool that helps you with AWS security assessment, auditing, hardening and incident response.

It follows guidelines of the CIS Amazon Web Services Foundations Benchmark (49 checks) and has more than 100 additional checks including related to GDPR, HIPAA, PCI-DSS, ISO-27001, FFIEC, SOC2 and others.

This tool provides a rapid snapshot of the current state of security within a customer environment. As an alternative, AWS Security Hub provides for automated compliance scanning and can integrate with Prowler

Asset Inventory

Identify all existing resources and have an updated asset inventory list coupled with who owns each

RDS Instance Inventory

RDS Security and Logging Checks

Training

Communication Technology

Detection

RDS Instance Checks

AWS Config

AWS Config has several managed rules to evaluate your RDS instances

Escalation Procedures

Analysis

It is highly recommended to export logs to a security incident event management (SIEM) solution (such as Splunk, ELK stack, etc.) to aide in viewing and analyzing a variety of logs for a more complete attack timeline analysis.

CloudTrail: RDS Public

  1. Navigate to your CloudTrail Dashboard
  2. In the left-hand margin select Event History
  3. In the drop-down change from Read-Only to Event Name
  4. Review CloudTrail logs for the eventname ModifyDBInstance, ModifyDBSnapshotAttribute, or ModifyDBClusterSnapshotAttribute and look for the value PubliclyAccessible events from public IP addresses

VPC Flow Logs

VPC Flow Logs is a feature that enables you to capture information about the IP traffic going to and from network interfaces in your VPC. This can be useful for IP addresses discovered within CloudTrail to determine the types of external connections to any public resources.

For further information and steps, including querying with Athena, please refer to the AWS Documentation for VPC Flow Logs. It is recommended that Athena analysis be included in a separate playbook and linked to other relavent items.

Endpoint / Host Based

Containment

RDS Public Exposure

When you launch a DB instance inside a VPC, the DB instance has a private IP address for traffic inside the VPC. This private IP address isn’t publicly accessible. You can use the Public access option to designate whether the DB instance also has a public IP address in addition to the private IP address.

The following illustration shows the Public access option in the Additional connectivity configuration section. To set the option, open the Additional connectivity configuration section in the Connectivity section.

Image

Eradication

RDS Unauthorized / Unrecognized Resources

Delete any unrecognized or unauthorized public snapshots or databases

  1. Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/
  2. In the navigation pane, choose Snapshots.
  3. The Manual snapshots list appears.
  4. Choose the DB snapshot that you want to delete.
  5. For Actions, choose Delete Snapshot.
  6. Choose Delete on the confirmation page.

Recovery

Same procedures as those listed for Eradication

Preventative Actions

RDS Security Checks

Security Control Policy: RDS Encryption

Enforce Mandatory RDS Encryption

AWS Config

AWS Config has multiple automated rules to protect against public access including rds-snapshots-public-prohibited

Overall Security Posture

Execute a Self-Service Security Assessment against the environment to further identify other risks and potentially other public exposure not identified throughout this playbook.

Lessons Learned

This is a place to add items specific to your company that do not necessarilly need "fixing", but are important to know when executing this playbook in tandem with operational and business requirements.

Addressed Backlog Items

Current Backlog Items