AWS guardduty: Document enabling GuardDuty RDS data activity monitoring (RDS_DATA_RISK)
Summary
Adds instructions and an AWS CLI example for enabling the RDS_DATA_RISK additional configuration alongside RDS_LOGIN_EVENTS when updating a GuardDuty detector, so RDS data activity monitoring can be turned on.
Security assessment
The change documents how to enable GuardDuty's RDS data activity monitoring (RDS_DATA_RISK) via updateDetector, expanding threat detection/audit coverage for RDS. It is security documentation for a monitoring feature, not a fix for a specific vulnerability or incident, so it is security-adjacent rather than a vulnerability remediation.
Evidence
+Run the [updateDetector](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateDetector.html) API operation using your own regional detector ID and passing the `features` object `name` as `RDS_LOGIN_EVENTS` and `status` as `ENABLED`. To also enable RDS data activity monitoring, pass `RDS_DATA_RISK` as the `name` under `AdditionalConfiguration` with `status` set to `ENABLED`.
Diff
diff --git a/guardduty/latest/ug/configure-rds-pro-standalone.md b/guardduty/latest/ug/configure-rds-pro-standalone.md index 27e3f81..6a38df8 100644 --- a//guardduty/latest/ug/configure-rds-pro-standalone.md +++ b//guardduty/latest/ug/configure-rds-pro-standalone.md @@ -34 +34 @@ API/CLI -Run the [updateDetector](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateDetector.html) API operation using your own regional detector ID and passing the `features` object `name` as `RDS_LOGIN_EVENTS` and `status` as `ENABLED`. +Run the [updateDetector](https://docs.aws.amazon.com/guardduty/latest/APIReference/API_UpdateDetector.html) API operation using your own regional detector ID and passing the `features` object `name` as `RDS_LOGIN_EVENTS` and `status` as `ENABLED`. To also enable RDS data activity monitoring, pass `RDS_DATA_RISK` as the `name` under `AdditionalConfiguration` with `status` set to `ENABLED`. @@ -40,2 +40,18 @@ To find the `detectorId` for your account and current Region, see the **Settings - - aws guardduty update-detector --detector-id 12abc34d567e8fa901bc2d34e56789f0 --region us-east-1 --features '[{"Name" : "RDS_LOGIN_EVENTS", "Status" : "ENABLED"}]' +The following example enables both `RDS_LOGIN_EVENTS` and `RDS_DATA_RISK`: + + + aws guardduty update-detector \ + --detector-id 12abc34d567e8fa901bc2d34e56789f0 \ + --region us-east-1 \ + --features '[ + { + "Name": "RDS_LOGIN_EVENTS", + "Status": "ENABLED", + "AdditionalConfiguration": [ + { + "Name": "RDS_DATA_RISK", + "Status": "ENABLED" + } + ] + } + ]'