AWS Security ChangesHomeSearch

AWS guardduty: Add GuardDuty RDS exfiltration/destructive remediation

Service: guardduty · 2026-10-09 · Documentation medium

File: guardduty/latest/ug/guardduty-remediate-compromised-database-rds.md · Type: data-exfiltration

Summary

Adds remediation guidance for GuardDuty findings involving anomalous RDS/Aurora data exfiltration and destructive DELETE/DROP activity, covering credential rotation, network restriction, least privilege, and data recovery.

Security assessment

The added content documents incident response and hardening steps for GuardDuty RDS findings, including credential rotation, session revocation, network restriction, and least-privilege permissions. It does not reference a specific CVE or fixed vulnerability, so it is security documentation rather than a vulnerability remediation.

Evidence

+Immediately change the password of the affected database user and revoke active sessions. If the user has elevated privileges, temporarily restrict their permissions to read-only or remove access entirely until investigation is complete.

Diff

diff --git a/guardduty/latest/ug/guardduty-remediate-compromised-database-rds.md b/guardduty/latest/ug/guardduty-remediate-compromised-database-rds.md
index cd59f22..40759a7 100644
--- a//guardduty/latest/ug/guardduty-remediate-compromised-database-rds.md
+++ b//guardduty/latest/ug/guardduty-remediate-compromised-database-rds.md
@@ -7 +7 @@
-Remediating potentially compromised database with successful login eventsRemediating potentially compromised database with failed login eventsRemediating potentially compromised credentialsRestrict network access
+Remediating potentially compromised database with successful login eventsRemediating potentially compromised database with failed login eventsRemediating potentially compromised database with anomalous exfiltration activityRemediating potentially compromised database with anomalous destructive activityRemediating potentially compromised credentialsRestrict network access
@@ -24,0 +25,4 @@ Follow these recommended steps to remediate a potentially compromised Amazon Aur
+  * Remediating potentially compromised database with anomalous exfiltration activity
+
+  * Remediating potentially compromised database with anomalous destructive activity
+
@@ -99,0 +104,86 @@ Set up an alert to get notified when an activity modifies a networking policy an
+## Remediating potentially compromised database with anomalous exfiltration activity
+
+The following recommended steps can help you remediate a potentially compromised Aurora database that exhibits unusual behavior related to data exfiltration events.
+
+  1. **Identify the affected database and user.**
+
+The generated GuardDuty finding provides the name of the affected database and the corresponding user details. For more information, see [Finding details](./guardduty_findings-summary.html).
+
+  2. **Identify the scope of data accessed.**
+
+Review available RDS data activity logs to determine which tables and rows were accessed by the anomalous user during the time window indicated by the finding. Assess the sensitivity of the data that was potentially exfiltrated.
+
+  3. **Confirm that this behavior is unexpected.**
+
+Examine whether this activity represents legitimate operational behavior as follows:
+
+     * If the source is internal, examine whether a scheduled ETL job, reporting tool, or backup process may account for the elevated query volume.
+
+     * If this is an external actor or previously unseen database attribute, examine whether the corresponding database credentials may have been exposed or shared externally.
+
+     * Review whether the combination of volume and unseen attributes (IP address, ASN, application name) aligns with any known operational change.
+
+  4. **Begin this step if the behavior is unexpected.**
+
+**Revoke access and rotate credentials.**
+
+Immediately change the password of the affected database user and revoke active sessions. If the user has elevated privileges, temporarily restrict their permissions to read-only or remove access entirely until investigation is complete.
+
+  5. **Assess the business impact.**
+
+Identify the data that was accessible to the affected user, determine if any sensitive or regulated data (PII, financial, healthcare) was potentially exfiltrated, and follow your organization's data breach notification procedures if applicable.
+
+  6. **Restrict network access.**
+
+Restrict database access for the suspected accounts and the source of this activity. Place the database in a private VPC if not already configured, and limit the security group rules to allow traffic only from the necessary sources. For more information, see Restrict network access.
+
+  7. **Perform root-cause analysis and determine the steps that potentially led to this activity.**
+
+Set up an alert to get notified when an activity modifies a networking policy and creates an insecure state. For more information, see [Firewall policies in AWS Network Firewall](https://docs.aws.amazon.com/network-firewall/latest/developerguide/firewall-policies.html) in the _AWS Network Firewall Developer Guide_.
+
+
+
+
+## Remediating potentially compromised database with anomalous destructive activity
+
+The following recommended steps can help you remediate a potentially compromised Aurora database that exhibits unusual behavior related to destructive `DELETE` or `DROP` events.
+
+  1. **Identify the affected database and user.**
+
+The generated GuardDuty finding provides the name of the affected database and the corresponding user details. For more information, see [Finding details](./guardduty_findings-summary.html).
+
+  2. **Identify the scope of destructive operations.**
+
+Review available RDS data activity logs to determine which tables, rows, or database objects were deleted or dropped by the anomalous user during the time window indicated by the finding. Determine whether the data loss is recoverable from existing backups or snapshots.
+
+  3. **Confirm that this behavior is unexpected.**
+
+Examine whether this activity represents legitimate operational behavior as follows:
+
+     * If the source is internal, examine whether a scheduled maintenance job, cleanup script, or migration process may account for the `DELETE` or `DROP` operations.
+
+     * If this is an external actor or previously unseen database attribute, examine whether the corresponding database credentials may have been exposed or compromised.
+
+     * Review whether the combination of destructive operations and unseen attributes (IP address, ASN, application name) aligns with any known operational change.
+
+  4. **Begin this step if the behavior is unexpected.**
+
+**Revoke access and rotate credentials.**
+
+Immediately change the password of the affected database user and revoke active sessions. Remove the user's `DROP` and `DELETE` privileges until investigation is complete to prevent further data destruction.
+
+  5. **Initiate data recovery.**
+
+If data loss is confirmed, initiate point-in-time recovery from automated backups or restore from the most recent snapshot. For Amazon Aurora, you can use backtrack to rewind the database to a time before the destructive activity occurred. For Amazon RDS, use point-in-time recovery to restore to a point before the event.
+
+  6. **Restrict network access and harden permissions.**
+
+Restrict database access for the suspected accounts and the source of this activity. Place the database in a private VPC if not already configured, and limit the security group rules to allow traffic only from the necessary sources. Review IAM policies and database user privileges to enforce least-privilege access, and enable deletion protection on the RDS instance if not already enabled. For more information, see Restrict network access.
+
+  7. **Perform root-cause analysis and determine the steps that potentially led to this activity.**
+
+Set up an alert to get notified when an activity modifies a networking policy and creates an insecure state. For more information, see [Firewall policies in AWS Network Firewall](https://docs.aws.amazon.com/network-firewall/latest/developerguide/firewall-policies.html) in the _AWS Network Firewall Developer Guide_.
+
+
+
+