MEDIUM

Ensure Azure Functions has CORS configured properly

CORS should be restricted to specific trusted origins, not wildcard.

Security Impact

Unrestricted CORS allows malicious websites to invoke functions with user credentials.

How to Remediate

Configure CORS to allow only specific domains instead of wildcard (*).

Affected Resources

Microsoft.Web/sites

Compliance Frameworks

SOC 2OWASP

How TigerGate Helps

TigerGate continuously monitors your Azure environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Azure Functions resources across your Azure subscriptions 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, OWASP compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
azure-functions-6
Service
Azure Functions
Category
Access Control
Severity
MEDIUM

Automate This Check

TigerGate automatically scans your Azure environment for this and 160+ other security checks.

Start Free Trial

Related Azure Functions Checks

View all checks
azure-functions-1high

Ensure Azure Functions uses HTTPS only

azure-functions-2medium

Ensure Azure Functions uses managed identity

azure-functions-3medium

Ensure Azure Functions has diagnostic logging enabled

azure-functions-4medium

Ensure Azure Functions uses latest runtime version

azure-functions-5high

Ensure Azure Functions uses minimum TLS 1.2