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.

Sign up for GitHub

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

Jump to bottom

Operational-Best-Practices-for-CMMC-2.0-Level-2: Conflicting Config Rules #400

Open
mikedizon opened this issue Jan 11, 2023 · 1 comment
Open

Operational-Best-Practices-for-CMMC-2.0-Level-2: Conflicting Config Rules #400

mikedizon opened this issue Jan 11, 2023 · 1 comment

Comments

@mikedizon
Copy link

S3BucketLoggingEnabled and S3DefaultEncryptionKms seem to conflict with one another.

AWS-KMS (SSE-KMS) can not be used on the target bucket for Server Access Logging, which causes S3_DEFAULT_ENCRYPTION_KMS to report as being non compliant. There should be a way to specify which buckets can be exempted from this rule.
@pnutshellmenace
Copy link

I am running into a similar conflict with ElbLoggingEnabled and S3DefaultEncryptionKms. With access logs enabled on an application load balancer, the S3 bucket has to use Amazon S3-managed keys.

From: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/enable-access-logging.html

The only server-side encryption option that's supported is Amazon S3-managed keys (SSE-S3).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mikedizon @pnutshellmenace