Fixed PR-GCP-TRF-INST-009: Ensure GCP HTTPS Load balancer SSL Policy is using restrictive profile#704
Open
rezoan wants to merge 1 commit intogcp-resource-addfrom
Open
Fixed PR-GCP-TRF-INST-009: Ensure GCP HTTPS Load balancer SSL Policy is using restrictive profile#704rezoan wants to merge 1 commit intogcp-resource-addfrom
rezoan wants to merge 1 commit intogcp-resource-addfrom
Conversation
…is using restrictive profile
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Violation Id: PR-GCP-TRF-INST-009
Violation Description:
This policy identifies HTTPS Load balancers which are not using restrictive profile in it's SSL Policy, which controls sets of features used in negotiating SSL with clients. As a best security practice, use RESTRICTED as SSL policy profile as it meets stricter compliance requirements and does not include any out-of-date SSL features.
How to Fix:
make sure you are following the deployment template format presented here