Check ID:
Provider: Azure
Service:
Severity: MEDIUM
Categories:
Resource type:
app_client_certificates_onProvider: Azure
Service:
appSeverity: MEDIUM
Categories:
identity-accessResource type:
microsoft.web/sites/configWhat this check verifies
Azure App Service apps enforce mutual TLS whenclient certificate mode is set to Required, meaning every inbound request must present a valid client certificate that the app can validate.
Risk
Without mTLS, clients aren’t cryptographically authenticated at the transport layer. Adversaries can reach endpoints using spoofed sources or stolen tokens, leading to unauthorized data access (confidentiality), request tampering (integrity), and automated abuse that degrades service (availability).Recommendation
Setclient certificate mode to Required and validate client certs in application logic (issuer, validity, revocation).
Enforce HTTPS only, avoid broad exclusion paths, and manage certs via a trusted CA with rotation and revocation. Apply least privilege and zero trust, layering with private access or IP restrictions as needed.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
References
- https://learn.microsoft.com/en-us/security/benchmark/azure/security-controls-v3-identity-management#im-4-authenticate-server-and-services
- https://learn.microsoft.com/en-us/azure/app-service/app-service-web-configure-tls-mutual-auth
Where this check fires
This check runs on every scheduled scan against your Azure account. Findings appear at Cloud Security → Findings filterable byCheck ID = app_client_certificates_on. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to Azure checks