Ensure API Gateway has mutual TLS enabled for sensitive APIs
Sensitive APIs should use mutual TLS (mTLS) for client certificate authentication.
Security Impact
Without mTLS, client identity cannot be cryptographically verified.
How to Remediate
Configure mutual TLS on custom domain with truststore containing client CA certificates.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Amazon API Gateway resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, FedRAMP compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-apigateway-13
- Service
- Amazon API Gateway
- Category
- Authentication
- Severity
- MEDIUM
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon API Gateway Checks
View all checksEnsure API Gateway has authentication enabled
Ensure API Gateway has logging enabled
Ensure API Gateway uses TLS 1.2 or higher
Ensure API Gateway has WAF enabled
Ensure API Gateway has throttling enabled