PCI scan complaining for TLSv1.0 on default api gateway url

0

I have created a REST api using AWS API Gateway.I have also attached a custom domain supporting TLSv1.2 only, still the PCI scan complains of TLSv1.0 also being supported on the default url given by AWS. How can I disable TLSv1.0 on Api gateway?

Jasleen
asked 10 months ago208 views
2 Answers
0

Under the "Security policy" section of your API Gateway custom domain name you should be able to edit the security policy to one that only supports TLSv1.2 or higher. https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-custom-domain-tls-version.html

If this was helpful, please remember to mark this answer as accepted. Thank you and good luck.

profile pictureAWS
answered 10 months ago
  • While creating the custom domain we can change the TLS version to either 1.2 or 1.0, which is under the setting 'Minimum TLS version'. I am not able to find the "Security Policy" section while creating Custom Domain. Please share a screenshot or steps to go to this section.

0

The PCI scan should be against the custom domain name that you have created, not default endpoint. I assume you have created corresponding DNS entry that points to API gateway FQDN.

To disable default endpoint, refer to How do I deactivate the API Gateway default endpoint for REST or HTTP APIs?

AWS
EXPERT
Mike_L
answered 10 months ago
  • Thanks for the reply. The PCI scan was done on the custom domain name, default URL must have been detected by the scan. I have also tried to disable the default endpoint as shared in the link you shared, but the default endpoint is still accessible. There is no GET implementation the base URL so I get { "message": "Forbidden" }.on accessing the default endpoint.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions