AWS macie medium security documentation change
Summary
Corrected behavior description of manual score assignment in Macie. Changed from 'Macie continues to perform automated discovery' to 'Macie stops performing automated discovery' for buckets with manual score 100.
Security assessment
The change addresses a potential security misconfiguration by clarifying that manually setting maximum score (100) stops ongoing sensitive data scanning. This prevents false security assumptions where users might believe scanning continues after manual override. The correction explicitly states that buckets are excluded from further scanning, which impacts security monitoring posture.
Diff
diff --git a/macie/latest/user/discovery-asdd-s3bucket-manage.md b/macie/latest/user/discovery-asdd-s3bucket-manage.md index 5045ff04f..7631a4db4 100644 --- a//macie/latest/user/discovery-asdd-s3bucket-manage.md +++ b//macie/latest/user/discovery-asdd-s3bucket-manage.md @@ -13 +13 @@ If you're a Macie administrator or you have a standalone Macie account, you can -You can override a bucket's calculated score and manually assign the maximum score (_100_), which also applies the _Sensitive_ label to the bucket. If you do this, Macie continues to perform automated sensitive data discovery for the bucket. However, subsequent analyses don't affect the bucket's score. To calculate the score automatically again, change the setting again. +You can override a bucket's calculated score and manually assign the maximum score (_100_), which also applies the _Sensitive_ label to the bucket. If you do this, Macie stops performing automated sensitive data discovery for the bucket, as buckets with a score of 100 are excluded from further scanning. To calculate the score automatically again and resume scanning, change the setting again.