Skip to content

Conversation

@ConsoleCatzirl
Copy link
Member

@ConsoleCatzirl ConsoleCatzirl commented Jan 2, 2025

Secure the ConfigAuditBucket by denying any S3 API calls for the bucket that do not use TLS/HTTPS.

This addresses a Security Hub finding from
cis-aws-foundations-benchmark/v/1.4.0/2.1.2.

Ref: https://repost.aws/knowledge-center/s3-bucket-policy-for-config-rule

Secure the `ConfigAuditBucket` by denying any S3 API calls for the
bucket that do not use TLS/HTTPS.

This addresses a Security Hub finding from
`cis-aws-foundations-benchmark/v/1.4.0/2.1.2`.

Ref: https://repost.aws/knowledge-center/s3-bucket-policy-for-config-rule
@ConsoleCatzirl ConsoleCatzirl requested a review from a team as a code owner January 2, 2025 18:51
@brucehoff
Copy link
Contributor

@ConsoleCatzirl What do you think about adding this restriction at the "organization" level, as a security control policy? I ask because we have 24 Jira issues for the cis-aws-foundations-benchmark/v/1.4.0/2.1.2 control, across the accounts in our AWS organization, and I'm wondering if we can address all with a single policy.

@brucehoff brucehoff self-requested a review January 2, 2025 19:20
@ConsoleCatzirl
Copy link
Member Author

@brucehoff I think that's a great idea. I'm closing this PR in favor of #1312

@ConsoleCatzirl
Copy link
Member Author

Unfortunately we can't do this with an SCP, reopening

@ConsoleCatzirl ConsoleCatzirl reopened this Jan 7, 2025
@ConsoleCatzirl ConsoleCatzirl merged commit 14a3519 into Sage-Bionetworks-IT:master Jan 9, 2025
4 checks passed
@ConsoleCatzirl ConsoleCatzirl deleted the it-2431 branch January 9, 2025 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants