AWS guardduty: GuardDuty RDS Protection adds data activity monitoring
Summary
Expands the RDS Protection documentation to cover a new 'RDS data activity' capability that profiles database query patterns on Aurora PostgreSQL and RDS for PostgreSQL to detect data access/manipulation threats (mass row reads, data deletion/drops, access from malicious or Tor IPs). Also broadens login-activity support to RDS for MySQL and RDS for MariaDB, adds a per-engine supported-versions table split into login vs. data activity monitoring, notes a two-week learning period, and updates free-trial/disable behavior.
Security assessment
The diff documents a new threat-detection/monitoring capability (data activity analysis for exfiltration and data-destructive behavior) rather than fixing a specific vulnerability or incident. It is security documentation describing detection coverage, supported engines/versions, and enablement, so it is security-relevant but not tied to a concrete CVE or weakness fix.
Evidence
+RDS Protection for data activity analyzes database query patterns on [Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html) for PostgreSQL and [RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html) databases to detect potential data access and manipulation threats.
Diff
diff --git a/guardduty/latest/ug/rds-protection.md b/guardduty/latest/ug/rds-protection.md index 77ce5be..e2e37be 100644 --- a//guardduty/latest/ug/rds-protection.md +++ b//guardduty/latest/ug/rds-protection.md @@ -7 +7 @@ -Supported databasesRDS login activity +Supported databasesRDS login activityRDS data activity @@ -15 +15 @@ You can configure RDS Protection along with all other protection plans from a si -RDS Protection in Amazon GuardDuty analyzes and profiles RDS login activity for potential access threats to your [Amazon Aurora databases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html) (Amazon Aurora MySQL-Compatible Edition and Aurora PostgreSQL-Compatible Edition) and [Amazon RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Welcome.html). +RDS Protection in Amazon GuardDuty analyzes and profiles RDS login and data activity for potential threats to your Amazon Aurora and RDS for PostgreSQL databases. @@ -17 +17 @@ RDS Protection in Amazon GuardDuty analyzes and profiles RDS login activity for -RDS Protection helps you identify potentially suspicious login behavior on these supported databases. GuardDuty continuously monitors and profiles RDS login activity for anomalous activity. For example, a previously unseen external actor has unauthorized access to your database, or adversary attempts brute-force access by guessing the database's password. +RDS Protection for login activity analyzes login events for potential access threats to [Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html) (Amazon Aurora MySQL-Compatible Edition and Aurora PostgreSQL-Compatible Edition), [RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html), [Amazon RDS for MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MySQL.html), and [Amazon RDS for MariaDB](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_MariaDB.html) databases. It helps you identify potentially suspicious login behavior on these supported databases. GuardDuty continuously monitors and profiles RDS login activity for anomalous activity. For example, a previously unseen external actor has unauthorized access to your database, or adversary attempts brute-force access by guessing the database's password. @@ -19 +19,3 @@ RDS Protection helps you identify potentially suspicious login behavior on these -With the launch of [Amazon Aurora PostgreSQL Limitless Database](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/limitless.html), GuardDuty expands RDS Protection to now also support monitoring login activity from Limitless Databases. For AWS accounts that have already enabled RDS Protection, GuardDuty will automatically start monitoring login data from their Limitless Databases. For accounts that have not yet enabled RDS Protection, you can learn more about the 30-day free trial and choose to enable this feature. To enable this feature, see [Enabling RDS Protection in multiple-account environments](./configure-rds-pro-multi-account.html) or [Enabling RDS Protection for a standalone account](./configure-rds-pro-standalone.html). +RDS Protection for data activity analyzes database query patterns on [Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html) for PostgreSQL and [RDS for PostgreSQL](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html) databases to detect potential data access and manipulation threats. GuardDuty continuously monitors and profiles RDS data activity for anomalous behavior. For example, an actor reading significantly more rows than normal for that database or user, deleting or dropping data, or accessing your database from a known malicious or Tor IP address. + +For accounts that have not yet enabled RDS Protection, you can learn more about the 30-day free trial and choose to enable this feature. To enable this feature, see [Enabling RDS Protection in multiple-account environments](./configure-rds-pro-multi-account.html) or [Enabling RDS Protection for a standalone account](./configure-rds-pro-standalone.html). @@ -23 +25 @@ With the launch of [Amazon Aurora PostgreSQL Limitless Database](https://docs.aw -RDS for PostgreSQL read replica instances require the primary database instance to be on a supported database version, and to be successfully replicated from primary database. For information about read replicas, see [Working with DB instance read replicas](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html) in _Amazon RDS User Guide_. +RDS for PostgreSQL read replica instances require the primary database instance to be on a supported database version, and to be successfully replicated from the primary database. For information about read replicas, see [Working with DB instance read replicas](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html) in _Amazon RDS User Guide_. @@ -25 +27 @@ RDS for PostgreSQL read replica instances require the primary database instance -RDS Protection doesn't require additional infrastructure; it is designed so as not to affect the performance of your database instances. When RDS Protection detects a potentially suspicious or anomalous login attempt, GuardDuty generates one or more [RDS Protection finding types](./findings-rds-protection.html) with details about the potentially compromised database. +RDS Protection doesn't require additional infrastructure; it is designed so as not to affect the performance of your database instances. When RDS Protection detects a potentially suspicious or anomalous login attempt, exfiltration, or data-destructive activity, GuardDuty generates one or more [RDS Protection finding types](./findings-rds-protection.html) with details about the potentially compromised database. @@ -31 +33 @@ RDS Protection doesn't require additional infrastructure; it is designed so as n - * When you enable GuardDuty in an AWS account in a new Region for the first time, you get a 30-day free trial. In this case, GuardDuty will also enable RDS Protection, which is included in the free trial. RDS Protection will start monitoring the login behavior of your database. + * When you enable GuardDuty in an AWS account in a new Region for the first time, you receive a 30-day free trial. In this case, GuardDuty also enables RDS Protection, which is included in the free trial. RDS Protection login activity monitoring and RDS Protection data activity monitoring will begin monitoring the activity of your databases. @@ -35 +37 @@ RDS Protection doesn't require additional infrastructure; it is designed so as n - * If you have already enabled RDS Protection, then with the launch of [Amazon Aurora PostgreSQL Limitless Database](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/limitless.html), GuardDuty will automatically start monitoring login activity for the Limitless Databases. If your RDS Protection 30-day free trial has expired already, then you will start incurring usage costs related to monitoring of Limitless Databases. + * When you are already using RDS Protection for login activity in an AWS account and decide to enable RDS Protection for data activity for the first time, your account will get a 30-day free trial for RDS Protection for data activity. @@ -37 +39 @@ RDS Protection doesn't require additional infrastructure; it is designed so as n - * You can choose to disable RDS Protection in any Region at any time. + * You can choose to disable RDS Protection or RDS Protection data activity monitoring in any Region at any time. @@ -44 +46 @@ RDS Protection doesn't require additional infrastructure; it is designed so as n -When the RDS Protection feature is not enabled, GuardDuty does't detect anomalous or suspicious login behavior. If you disable RDS Protection, GuardDuty immediately stops monitoring RDS login activity, and will not detect any potential threat to your supported database instances or generate associated finding types. +When the RDS Protection feature is not enabled, GuardDuty doesn't detect anomalous or suspicious login or data behavior. If you disable RDS Protection, GuardDuty immediately stops monitoring RDS activity and will not detect any potential threat to your supported database instances or generate associated finding types. @@ -50 +52 @@ For AWS Regions where Aurora PostgreSQL Limitless Databases are supported, see [ -The following table shows the supported Aurora and Amazon RDS database versions for RDS Protection. +The following table shows the supported Aurora and Amazon RDS database versions for RDS Protection _login activity monitoring_ and _data activity monitoring_. GuardDuty may expand to additional Amazon RDS databases in the future. @@ -52,2 +54,2 @@ The following table shows the supported Aurora and Amazon RDS database versions -Amazon Aurora and Amazon RDS DB engine | Supported engine versions ----|--- +Amazon Aurora and Amazon RDS DB engine | Login activity monitoring supported engine versions | Data activity monitoring supported engine versions +---|---|--- @@ -60 +62 @@ Aurora MySQL | - +| Not supported @@ -71,0 +74,9 @@ Aurora PostgreSQL | +| + + * 11.19 or later + * 12.14 or later + * 13.10 or later + * 14.7 or later + * 15.2 or later + * Subsequent major versions + @@ -84,0 +96,9 @@ RDS for PostgreSQL | +| + + * 11.20 or later + * 12.15 or later + * 13.11 or later + * 14.8 or later + * 15.3 or later + * Subsequent major versions + @@ -91 +111 @@ Amazon Aurora PostgreSQL Limitless Database | - +| Not supported @@ -100 +120 @@ Amazon RDS for MariaDB | - +| Not supported @@ -107 +127 @@ Amazon RDS for MySQL | - +| Not supported @@ -113 +133,5 @@ When you enable the RDS Protection feature, GuardDuty automatically starts monit -When RDS Protection detects a potential threat, such as an unusual pattern in a series of successful, failed, or incomplete login attempts, GuardDuty generates one or more [RDS Protection finding types](./findings-rds-protection.html). Based on the finding type, it may include details about the anomalous behavior, such as [RDS login activity-based anomalies](./guardduty_findings-summary.html#rds-pro-login-anomaly). +When RDS Protection detects a potential threat, such as an unusual pattern in a series of successful, failed, or incomplete login attempts, GuardDuty generates one or more [RDS Protection finding types](./findings-rds-protection.html). Based on the finding type, it may include details about the anomalous behavior, such as [RDS login activity-based anomalies](./guardduty_findings-summary.html#rds-pro-login-anomaly). GuardDuty doesn't make RDS login activity logs available to you. + +## RDS data activity + +When you enable RDS Protection for data activity, GuardDuty analyzes database activity patterns in supported Aurora and Amazon RDS databases to identify potential data access and manipulation threats. If it detects an anomalous data activity, GuardDuty generates a finding with details about the potentially compromised database. When you enable RDS Protection for data activity for the first time, or when you create a new database instance, there is a learning period of up to two weeks to establish a baseline of normal behavior. During this time you may not have an associated anomalous data activity finding. @@ -115 +139 @@ When RDS Protection detects a potential threat, such as an unusual pattern in a -GuardDuty doesn't manage your Supported databases or RDS login activity, or make RDS login activity available to you. +When RDS Protection for data activity detects a potential threat, GuardDuty generates one or more [RDS Protection finding types](./findings-rds-protection.html). Examples include an actor reading significantly more rows than is normal for that database or user, deleting or dropping data, or accessing your database from a known malicious or Tor IP address. Depending on the finding type, the finding may include details about the anomalous behavior, such as [RDS data activity-based anomalies](./guardduty_findings-summary.html#rds-pro-data-activity-anomaly). GuardDuty doesn't make RDS data activity logs available to you.