AWS Security ChangesHomeSearch

AWS guardduty: Add GuardDuty RDS exfiltration and impact findings documentation

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

File: guardduty/latest/ug/findings-rds-protection.md

Summary

Added new GuardDuty RDS Protection finding types for exfiltration and destructive impact, including severity levels, descriptions, and remediation recommendations.

Security assessment

The change documents new GuardDuty findings for RDS exfiltration and destructive operations, providing security guidance but not addressing a specific vulnerability.

Evidence

+## Exfiltration:RDS/AnomalousBehavior

Diff

diff --git a/guardduty/latest/ug/findings-rds-protection.md b/guardduty/latest/ug/findings-rds-protection.md
index 10923ed..25f1095 100644
--- a//guardduty/latest/ug/findings-rds-protection.md
+++ b//guardduty/latest/ug/findings-rds-protection.md
@@ -7 +7 @@
-CredentialAccess:RDS/AnomalousBehavior.SuccessfulLoginCredentialAccess:RDS/AnomalousBehavior.FailedLoginCredentialAccess:RDS/AnomalousBehavior.SuccessfulBruteForceCredentialAccess:RDS/MaliciousIPCaller.SuccessfulLoginCredentialAccess:RDS/MaliciousIPCaller.FailedLoginDiscovery:RDS/MaliciousIPCallerCredentialAccess:RDS/TorIPCaller.SuccessfulLoginCredentialAccess:RDS/TorIPCaller.FailedLoginDiscovery:RDS/TorIPCaller
+CredentialAccess:RDS/AnomalousBehavior.SuccessfulLoginCredentialAccess:RDS/AnomalousBehavior.FailedLoginCredentialAccess:RDS/AnomalousBehavior.SuccessfulBruteForceCredentialAccess:RDS/MaliciousIPCaller.SuccessfulLoginCredentialAccess:RDS/MaliciousIPCaller.FailedLoginDiscovery:RDS/MaliciousIPCallerCredentialAccess:RDS/TorIPCaller.SuccessfulLoginCredentialAccess:RDS/TorIPCaller.FailedLoginDiscovery:RDS/TorIPCallerExfiltration:RDS/AnomalousBehaviorImpact:RDS/AnomalousBehavior.DropImpact:RDS/AnomalousBehavior.DeleteExfiltration:RDS/MaliciousIPCallerExfiltration:RDS/TorIPCallerImpact:RDS/MaliciousIPCallerImpact:RDS/TorIPCaller
@@ -32,0 +33,14 @@ GuardDuty RDS Protection detects anomalous login behavior on your database insta
+  * Exfiltration:RDS/AnomalousBehavior
+
+  * Impact:RDS/AnomalousBehavior.Drop
+
+  * Impact:RDS/AnomalousBehavior.Delete
+
+  * Exfiltration:RDS/MaliciousIPCaller
+
+  * Exfiltration:RDS/TorIPCaller
+
+  * Impact:RDS/MaliciousIPCaller
+
+  * Impact:RDS/TorIPCaller
+
@@ -207,0 +222,162 @@ If this activity is unexpected for the associated database, it may indicate that
+## Exfiltration:RDS/AnomalousBehavior
+
+### Anomalous activity from a user extracting large volume of data from an RDS database in your account.
+
+**Default severity: Low**
+
+###### Note
+
+Depending on the anomalous behavior associated with this finding, the default severity can be Low, Medium, or High.
+
+  * **Low** – If the user name associated with this finding executed `SELECT` statements from an IP address that is associated with a private network.
+
+  * **Medium** – If the user name associated with this finding executed `SELECT` statements from a public IP address.
+
+  * **High** – If the user name associated with this finding executed `SELECT` statements returning an unusually large volume of rows, and the activity either originated from a previously unseen public network or was performed by a high-privilege database role or administrative client.
+
+
+
+
+  * **Feature:** RDS DB Activity Monitoring
+
+
+
+
+This finding informs you that anomalous database activity consistent with data exfiltration was observed on an RDS database in your AWS environment. This may indicate that a database user selected a significantly higher number of rows than usual, or that the activity involved a previously unseen database attribute such as a new user, IP address, or database name that contributed to the volume spike. A common scenario is a compromised database credential being used to extract data through a combination of unusual access patterns and elevated query volume.
+
+This activity was identified as anomalous by the GuardDuty anomaly detection machine learning (ML) model. The ML model evaluates all database activity events in your [Supported Amazon Aurora, Amazon RDS, and Aurora Limitless databases](./rds-protection.html#rds-pro-supported-db) and identifies anomalous events that are associated with techniques used by adversaries. The ML model tracks various factors of the RDS database activity such as the user that made the request, the queries executed, the volume of data accessed, and the specific database connection details that were used. For information about the database activity that is potentially unusual, see [RDS data activity-based anomalies](./guardduty_findings-summary.html#rds-pro-data-activity-anomaly).
+
+**Remediation recommendations:**
+
+If this activity is unexpected for the associated database, it is recommended to change the password of the associated database user, and review available audit logs to determine what data the anomalous user accessed. It is recommended to place the database in a private VPC and limit the security group rules to allow traffic only from the necessary sources. For more information, see [Remediating potentially compromised database with anomalous exfiltration activity](./guardduty-remediate-compromised-database-rds.html#gd-compromised-db-exfiltration-activity).
+
+## Impact:RDS/AnomalousBehavior.Drop
+
+### Anomalous activity from a user dropping data from an RDS database in your account.
+
+**Default severity: Medium**
+
+###### Note
+
+Depending on the anomalous behavior associated with this finding, the default severity can be Medium or High.
+
+  * **Medium** – If the user name associated with this finding executed anomalous `DROP` statements.
+
+  * **High** – If the user name associated with this finding executed multiple `DROP` statements, and the activity either originated from a previously unseen public network or was performed by a high-privilege database role or administrative client.
+
+
+
+
+  * **Feature:** RDS DB Activity Monitoring
+
+
+
+
+This finding informs you that anomalous database activity consistent with destructive operations was observed on an RDS database in your AWS environment. This may indicate that a database user dropped a significantly higher number of tables or database objects than usual, or that the activity involved a previously unseen database attribute such as a new user, IP address, or application name that contributed to the destructive operation. A common scenario is a compromised database credential being used to destroy database structures through a combination of unusual access patterns and elevated `DROP` statement volume.
+
+This activity was identified as anomalous by the GuardDuty anomaly detection machine learning (ML) model. The ML model evaluates all database activity events in your [Supported Amazon Aurora, Amazon RDS, and Aurora Limitless databases](./rds-protection.html#rds-pro-supported-db) and identifies anomalous events that are associated with techniques used by adversaries. The ML model tracks various factors of the RDS database activity such as the user that made the request, the statements executed, the database objects targeted, and the specific database connection details that were used. For information about the database activity that is potentially unusual, see [RDS data activity-based anomalies](./guardduty_findings-summary.html#rds-pro-data-activity-anomaly).
+
+**Remediation recommendations:**
+
+If this activity is unexpected for the associated database, it is recommended to immediately change the password of the associated database user and revoke their access. Review available audit logs to determine the scope of objects dropped, and initiate recovery from backups if necessary. It is also recommended to place the database in a private VPC and limit the security group rules to allow traffic only from the necessary sources. For more information, see [Remediating potentially compromised database with anomalous destructive activity](./guardduty-remediate-compromised-database-rds.html#gd-compromised-db-destructive-activity).
+
+## Impact:RDS/AnomalousBehavior.Delete
+
+### Anomalous activity from a user deleting data from an RDS database in your account.
+
+**Default severity: Low**
+
+###### Note
+
+Depending on the anomalous behavior associated with this finding, the default severity can be Low, Medium, or High.
+
+  * **Low** – If the user name associated with this finding executed `DELETE` statements from an IP address that is associated with a private network.
+
+  * **Medium** – If the user name associated with this finding executed `DELETE` statements from a public IP address.
+
+  * **High** – If the user name associated with this finding executed `DELETE` statements returning an unusually large volume of rows, and the activity either originated from a previously unseen public network or was performed by a high-privilege database role or administrative client.
+
+
+
+
+  * **Feature:** RDS DB Activity Monitoring
+
+
+
+
+This finding informs you that anomalous database activity consistent with destructive operations was observed on an RDS database in your AWS environment. This may indicate that a database user deleted a significantly higher number of rows than usual, or that the activity involved a previously unseen database attribute, such as a new user, IP address, or application name, that contributed to the destructive operation. A common scenario is a compromised database credential being used to systematically remove data through a combination of unusual access patterns and elevated `DELETE` statement volume.
+
+This activity was identified as anomalous by the GuardDuty anomaly detection machine learning (ML) model. The ML model evaluates all database activity events in your [Supported Amazon Aurora, Amazon RDS, and Aurora Limitless databases](./rds-protection.html#rds-pro-supported-db) and identifies anomalous events that are associated with techniques used by adversaries. The ML model tracks various factors of the RDS database activity such as the user that made the request, the statements executed, the number of rows affected, and the specific database connection details that were used. For information about the database activity that is potentially unusual, see [RDS data activity-based anomalies](./guardduty_findings-summary.html#rds-pro-data-activity-anomaly).
+
+**Remediation recommendations:**
+
+If this activity is unexpected for the associated database, it is recommended to immediately change the password of the associated database user and revoke their access. Review available audit logs to determine the scope of data deleted, and initiate point-in-time recovery from automated backups if data loss is confirmed. It is also recommended to place the database in a private VPC and limit the security group rules to allow traffic only from the necessary sources. For more information, see [Remediating potentially compromised database with anomalous destructive activity](./guardduty-remediate-compromised-database-rds.html#gd-compromised-db-destructive-activity).
+
+## Exfiltration:RDS/MaliciousIPCaller
+
+### An IP address that is associated with known malicious activity executed data extraction queries on an RDS database in your account.
+
+**Default severity: High**
+
+  * **Feature:** RDS DB Activity Monitoring
+
+
+
+
+This finding informs you that an IP address associated with known malicious activity executed database queries consistent with data exfiltration on an RDS database in your AWS environment. This indicates that the user and password associated with the RDS database in your account may have been compromised, and the RDS database data may have been exfiltrated by a potentially malicious actor.
+
+**Remediation recommendations:**
+
+If this activity is unexpected for the associated database, it may indicate that the user credentials may have been exposed or compromised. It is recommended to change the password of the associated database user, and review available RDS data logs for activity performed by the compromised user. It is recommended to identify the data that was accessible to the affected user and assess the business impact of any potentially exfiltrated data. It is also recommended to place the database in a private VPC and limit the security group rules to allow traffic only from the necessary sources. For more information, see [Remediating potentially compromised database with anomalous exfiltration activity](./guardduty-remediate-compromised-database-rds.html#gd-compromised-db-exfiltration-activity).
+
+## Exfiltration:RDS/TorIPCaller
+
+### A Tor exit node IP address executed data extraction queries on an RDS database in your account.
+
+**Default severity: High**
+
+  * **Feature:** RDS DB Activity Monitoring
+
+
+
+
+This finding informs you that a Tor exit node IP address executed database queries consistent with data exfiltration on an RDS database in your AWS environment. Tor is a software for enabling anonymous communication. It encrypts and randomly bounces communications through relays between a series of network nodes. The last Tor node is called the exit node. This can indicate unauthorized access to the RDS resources in your account, with the intent of hiding the anonymous user's true identity while exfiltrating data.
+
+**Remediation recommendations:**
+
+If this activity is unexpected for the associated database, it may indicate that the user credentials may have been exposed or compromised. It is recommended to change the password of the associated database user, and review available RDS data logs for activity performed by the compromised user. It is recommended to identify the data that was accessible to the affected user and assess the business impact of any potentially exfiltrated data. It is also recommended to place the database in a private VPC and limit the security group rules to allow traffic only from the necessary sources. For more information, see [Remediating potentially compromised database with anomalous exfiltration activity](./guardduty-remediate-compromised-database-rds.html#gd-compromised-db-exfiltration-activity).
+
+## Impact:RDS/MaliciousIPCaller
+
+### An IP address that is associated with known malicious activity executed destructive statements on an RDS database in your account.
+
+**Default severity: High**
+
+  * **Feature:** RDS DB Activity Monitoring
+
+
+
+
+This finding informs you that an IP address associated with known malicious activity executed database statements with destructive impact on an RDS database in your AWS environment. This indicates that the user and password associated with the RDS database in your account may have been compromised, and the RDS database may have been subjected to destructive operations by a potentially malicious actor.
+
+**Remediation recommendations:**
+
+If this activity is unexpected for the associated database, it may indicate that the user credentials may have been exposed or compromised. It is recommended to immediately change the password of the associated database user and revoke their access. Review available RDS data logs to determine the scope of destructive operations performed, and initiate recovery from backups if necessary. It is also recommended to place the database in a private VPC and limit the security group rules to allow traffic only from the necessary sources. For more information, see [Remediating potentially compromised database with anomalous destructive activity](./guardduty-remediate-compromised-database-rds.html#gd-compromised-db-destructive-activity).
+
+## Impact:RDS/TorIPCaller
+
+### A Tor exit node IP address executed destructive statements on an RDS database in your account.
+
+**Default severity: High**
+
+  * **Feature:** RDS DB Activity Monitoring
+
+
+
+
+This finding informs you that a Tor exit node IP address executed database statements with destructive impact on an RDS database in your AWS environment. Tor is an overlay network for enabling anonymous communication. It encrypts and randomly bounces communications through relays between a series of network nodes. The last Tor node is called the exit node. This can indicate unauthorized access to the RDS resources in your account, with the intent of hiding the anonymous user's true identity while performing destructive operations.
+
+**Remediation recommendations:**
+
+If this activity is unexpected for the associated database, it may indicate that the user credentials may have been exposed or compromised. It is recommended to immediately change the password of the associated database user and revoke their access. Review available RDS data logs to determine the scope of destructive operations performed, and initiate recovery from backups if necessary. It is also recommended to place the database in a private VPC and limit the security group rules to allow traffic only from the necessary sources. For more information, see [Remediating potentially compromised database with anomalous destructive activity](./guardduty-remediate-compromised-database-rds.html#gd-compromised-db-destructive-activity).
+