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

Non-Compliant CloudFront Distribution Using Default Domain Name #1320

Closed
bestickley opened this issue Jun 1, 2023 · 3 comments
Closed

Non-Compliant CloudFront Distribution Using Default Domain Name #1320

bestickley opened this issue Jun 1, 2023 · 3 comments

Comments

@bestickley
Copy link

bestickley commented Jun 1, 2023

Hi,
When I instantiate a default CloudFront distribution using the default domain name I see the error: [Error at /ss-stickb/ui/NextSite/Distribution/Distribution/Resource] AwsSolutions-CFR4: The CloudFront distribution allows for SSLv3 or TLSv1 for HTTPS viewer connections.. This is happening because of the line below:

Is this intended behavior? I would expect it to be secure behavior to use default CloudFront domain.

@dontirun
Copy link
Collaborator

dontirun commented Jun 2, 2023

Yes. The extended explanation on that rule has more information

Vulnerabilities have been and continue to be discovered in the deprecated SSL and TLS protocols. Help protect viewer connections by specifying a viewer certificate that enforces a minimum of TLSv1.1 or TLSv1.2 in the security policy. Distributions that use the default CloudFront viewer certificate or use 'vip' for the SslSupportMethod are non-compliant with this rule, as the minimum security policy is set to TLSv1 regardless of the specified MinimumProtocolVersion

@bestickley
Copy link
Author

@dontirun, thank you for explaining. Where is the extended explanation?

@dontirun
Copy link
Collaborator

dontirun commented Jun 2, 2023

Enabling the verbose flag will show the extended explanations for all rules. They're also all listed on the
RULES file

Aspects.of(stack).add(new AwsSolutionsChecks({ verbose: true }));

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

No branches or pull requests

2 participants