AVD-AWS-0088 Flagged on S3 Buckets with AES Encryption #9132
Replies: 1 comment 8 replies
-
|
Hi @shxjing ! When scanning the following hcl configuration, the
We need to revise AVD-AWS-0008 as AWS now applies SSE-S3 by default. @simar7 The Terraform plan alone does not provide enough information to distinguish whether a field is a nested block or a regular attribute, as both appear similarly in the JSON output. I suggest introducing an optional flag, for example terraform providers schema -json > providers-schema.jsonEach resource in the plan contains a Additionally, having the provider schema is useful when analyzing Terraform configurations in JSON format, enabling precise interpretation of the resource structure. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
IDs
AVD-AWS-0088
Description
Hello,
I have a terraform snippet:
Locally, im running the commands:
We are getting flagged for
AVD-AWS-0088, with trivy output as follows:Our buckets currently are encrypted by default with server-side encryption (SSE-S3).
I think there is a previous issue created #6024, but the fix seems to only be for cloudformation. Looking at the vulnerability DB page here: https://avd.aquasec.com/misconfig/aws/s3/avd-aws-0088#Terraform, it seems like there are only examples with KMS keys. For this rule to pass, must we encrypt using a KMS key, or is this bugged? :o
Reproduction Steps
Target
Git Repository
Scanner
Misconfiguration
Target OS
No response
Debug Output
Version
Checklist
-f jsonthat shows data sources and confirmed that the security advisory in data sources was correctBeta Was this translation helpful? Give feedback.
All reactions