API Gateway classic custom domain does not use secure TLS protocol version (1.2 and above) Affecting API Gateway (REST APIs) service in AWS
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CC-00190
- creditSnyk Research Team
Description
The TLS (Transport Layer Security) protocol secures transmission of data over the internet using standard encryption technology. Encryption should be set with the latest version of TLS where possible. Versions prior to TLS 1.2 are deprecated and usage may pose security risks.
How to fix?
Set the security_policy attribute to the value TLS_1_2.
Example Configuration
resource "aws_api_gateway_domain_name" "domain_name" {
domain_name = "example.com"
certificate_arn = "arn:aws:acm:us-east-1:123456789012:certificate/cecbde21-a7ed-abcd-1234-abcdef123456"
security_policy = "TLS_1_2"
}
Set the AWS::ApiGateway::DomainName SecurityPolicy field to TLS_1_2, set the AWS::ApiGatewayV2::DomainName DomainNameConfigurations.SecurityPolicy field to TLS_1_2.
Example Configuration
Type: 'AWS::ApiGateway::DomainName'
Properties:
SecurityPolicy: TLS_1_2
# other required fields here
Type: 'AWS::ApiGatewayV2::DomainName'
Properties:
DomainNameConfigurations:
SecurityPolicy: TLS_1_2
# other required fields here