Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(misconf): improve S3 server logging access detection for AVD-AWS-0089 #7239

Open
nikpivkin opened this issue Jul 26, 2024 · 0 comments · May be fixed by aquasecurity/trivy-checks#208
Open
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning
Milestone

Comments

@nikpivkin
Copy link
Contributor

We are currently warning to enable logging for those buckets that do not keep server access logs. We identify such buckets only by pre-defined grants (known as Canned ACLs). However, Amazon recommends using bucket policies to grant access. Also, in CloudFormation, the ACL field is deprecated, so users are likely to use other ways to configure access than the way we identify logging buckets.

Existing ways to grant access for logging:

  • Bucket Policy
  • Grants
  • Canned ACLs

Refs:

@nikpivkin nikpivkin added kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning labels Jul 26, 2024
@nikpivkin nikpivkin self-assigned this Jul 31, 2024
@simar7 simar7 added this to the v0.55.0 milestone Aug 6, 2024
@knqyf263 knqyf263 modified the milestones: v0.55.0, v0.56.0 Sep 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. scan/misconfiguration Issues relating to misconfiguration scanning
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants