Azure

How to harden security of Azure API Management

Why Azure API Management Security Matters

Azure API Management (APIM) acts as the gateway between external consumers and your backend services. A misconfigured APIM instance can expose internal APIs, leak sensitive data in responses, or allow unauthorized access to backend systems. This guide walks you through the essential steps to harden your APIM deployment using CLI commands, policies, and monitoring.

Threat Landscape and Attack Surface

Hardening Azure API Management requires understanding the threat landscape specific to this service. Azure services are attractive targets because they often store, process, or transmit sensitive data and provide control-plane access to cloud infrastructure. Attackers probe for misconfigured services using automated scanners that continuously sweep Azure IP ranges for exposed endpoints, weak authentication, and default configurations.

The attack surface for Azure API Management includes several dimensions. The network perimeter determines who can reach the service endpoints. The identity and access layer controls what authenticated principals can do. The data plane governs how data is protected at rest and in transit. The management plane controls who can modify the service configuration itself. A comprehensive hardening strategy addresses all four dimensions because a weakness in any single layer can be exploited to bypass the controls in other layers.

Microsoft’s shared responsibility model means that while Azure secures the physical infrastructure, network fabric, and hypervisor, you are responsible for configuring the service securely. Default configurations prioritize ease of setup over security. Every Azure service ships with settings that must be tightened for production use, and this guide walks through the critical configurations that should be changed from their defaults.

The MITRE ATT&CK framework for cloud environments provides a structured taxonomy of attack techniques that adversaries use against Azure services. Common techniques relevant to Azure API Management include initial access through exposed credentials or misconfigured endpoints, lateral movement through overly permissive RBAC assignments, and data exfiltration through unmonitored data plane operations. Each hardening control in this guide maps to one or more of these attack techniques.

Compliance and Regulatory Context

Security hardening is not just a technical exercise. It is a compliance requirement for virtually every regulatory framework that applies to cloud workloads. SOC 2 Type II requires evidence of security controls for cloud services. PCI DSS mandates network segmentation and encryption for payment data. HIPAA requires access controls and audit logging for health information. ISO 27001 demands a systematic approach to information security management. FedRAMP requires specific configurations for government workloads.

Azure Policy and Microsoft Defender for Cloud provide built-in compliance assessments against these frameworks. After applying the hardening configurations in this guide, run a compliance scan to verify your security posture against your applicable regulatory standards. Address any remaining findings to achieve and maintain compliance. Export compliance reports on a scheduled basis to satisfy audit requirements and demonstrate continuous adherence.

The Microsoft cloud security benchmark provides a comprehensive set of security controls mapped to common regulatory frameworks. Use this benchmark as a checklist to verify that your hardening effort covers all required areas. Each control includes Azure-specific implementation guidance and links to the relevant Azure service documentation.

Step 1: Deploy APIM in a Virtual Network

APIM supports two VNet modes: External (gateway accessible from the internet, backend accessible via VNet) and Internal (everything behind the VNet). For maximum security, use internal mode with Azure Front Door or Application Gateway as the public entry point.

# Deploy APIM in internal VNet mode
az apim create --name apim-prod --resource-group rg-api \
  --publisher-email admin@contoso.com --publisher-name Contoso \
  --sku-name Premium --location eastus \
  --virtual-network Internal

# Associate with a specific subnet
az apim update --name apim-prod --resource-group rg-api \
  --set virtualNetworkConfiguration.subnetResourceId="/subscriptions/{sub}/resourceGroups/rg-network/providers/Microsoft.Network/virtualNetworks/vnet-hub/subnets/snet-apim"

Step 2: Enforce Authentication on All APIs

Never expose APIs without authentication. Use JWT validation policies to verify tokens before requests reach your backends.

<inbound>
    <validate-jwt header-name="Authorization" failed-validation-httpcode="401">
        <openid-config url="https://login.microsoftonline.com/{tenant}/v2.0/.well-known/openid-configuration" />
        <required-claims>
            <claim name="aud" match="all">
                <value>api://your-api-client-id</value>
            </claim>
        </required-claims>
    </validate-jwt>
</inbound>

Step 3: Implement Rate Limiting and Throttling

<inbound>
    <rate-limit-by-key calls="100" renewal-period="60"
        counter-key="@(context.Subscription?.Key ?? context.Request.IpAddress)" />
    <quota-by-key calls="10000" renewal-period="86400"
        counter-key="@(context.Subscription.Key)" />
</inbound>

Rate limiting prevents abuse and DDoS attacks. The rate-limit-by-key policy limits per-minute calls, while quota-by-key enforces daily limits per subscription.

Step 4: Remove Sensitive Headers and Information

<outbound>
    <set-header name="X-Powered-By" exists-action="delete" />
    <set-header name="X-AspNet-Version" exists-action="delete" />
    <set-header name="Server" exists-action="delete" />
    <set-header name="X-Backend-Host" exists-action="delete" />
</outbound>

Step 5: Enable CORS Securely

<cors allow-credentials="true">
    <allowed-origins>
        <origin>https://app.contoso.com</origin>
    </allowed-origins>
    <allowed-methods>
        <method>GET</method>
        <method>POST</method>
    </allowed-methods>
    <allowed-headers>
        <header>Authorization</header>
        <header>Content-Type</header>
    </allowed-headers>
</cors>

Never use wildcard (*) origins in production. Specify exact domains that need API access.

Identity and Access Management Deep Dive

Identity is the primary security perimeter in cloud environments. For Azure API Management, implement a robust identity and access management strategy that follows the principle of least privilege.

Managed Identities: Use system-assigned or user-assigned managed identities for service-to-service authentication. Managed identities eliminate the need for stored credentials (connection strings, API keys, or service principal secrets) that can be leaked, stolen, or forgotten in configuration files. Azure automatically rotates the underlying certificates, removing the operational burden of credential rotation.

Custom RBAC Roles: When built-in roles grant more permissions than required, create custom roles that include only the specific actions needed. For example, if a monitoring service only needs to read metrics and logs from Azure API Management, create a custom role with only the Microsoft.Insights/metrics/read and Microsoft.Insights/logs/read actions rather than assigning the broader Reader or Contributor roles.

Conditional Access: For human administrators accessing Azure API Management through the portal or CLI, enforce Conditional Access policies that require multi-factor authentication, compliant devices, and approved locations. Set session lifetime limits so that administrative sessions expire after a reasonable period, forcing re-authentication.

Just-In-Time Access: Use Azure AD Privileged Identity Management (PIM) to provide time-limited, approval-required elevation for administrative actions. Instead of permanently assigning Contributor or Owner roles, require administrators to activate their role assignment for a specific duration with a business justification. This reduces the window of exposure if an administrator’s account is compromised.

Service Principal Hygiene: If managed identities cannot be used (for example, for external services or CI/CD pipelines), use certificate-based authentication for service principals rather than client secrets. Certificates are harder to accidentally expose than text secrets, and Azure Key Vault can automate their rotation. Set short expiration periods for any client secrets and monitor for secrets that are approaching expiration.

Step 6: Use Managed Identity for Backend Authentication

<authentication-managed-identity resource="https://your-backend.azurewebsites.net" />

This eliminates hardcoded credentials in APIM policies. The managed identity authenticates to backends that accept Azure AD tokens.

Step 7: Enable Defender for APIs

# Enable Microsoft Defender for APIs
az security pricing create --name Api --tier Standard

Defender for APIs analyzes API traffic patterns and detects anomalies such as unusual data exfiltration, suspicious parameter manipulation, and authentication brute-force attempts.

Step 8: Configure Diagnostic Logging

az monitor diagnostic-settings create \
  --name apim-diagnostics \
  --resource "/subscriptions/{sub}/resourceGroups/rg-api/providers/Microsoft.ApiManagement/service/apim-prod" \
  --workspace /subscriptions/{sub}/resourceGroups/rg-monitor/providers/Microsoft.OperationalInsights/workspaces/law-prod \
  --logs '[{"category":"GatewayLogs","enabled":true}]' \
  --metrics '[{"category":"AllMetrics","enabled":true}]'

Step 9: Disable Direct Management API Access

# Disable legacy management API
az apim update --name apim-prod --resource-group rg-api \
  --set customProperties."Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Ssl30"="false" \
  --set customProperties."Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Tls10"="false" \
  --set customProperties."Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Backend.Protocols.Tls11"="false"

Step 10: Use Named Values with Key Vault

# Create named value linked to Key Vault secret
az apim nv create --service-name apim-prod --resource-group rg-api \
  --named-value-id backend-key --display-name "Backend API Key" \
  --secret true \
  --value "keyvault-secret-reference"

Store all secrets, connection strings, and API keys in Azure Key Vault. Reference them through APIM named values so secrets never appear in policy definitions or source control.

Defense in Depth Strategy

No single security control is sufficient. Apply a defense-in-depth strategy that layers multiple controls so that the failure of any single layer does not expose the service to attack. For Azure API Management, this means combining network isolation, identity verification, encryption, monitoring, and incident response capabilities.

At the network layer, restrict access to only the networks that legitimately need to reach the service. Use Private Endpoints to eliminate public internet exposure entirely. Where public access is required, use IP allowlists, service tags, and Web Application Firewall (WAF) rules to limit the attack surface. Configure network security groups (NSGs) with deny-by-default rules and explicit allow rules only for required traffic flows.

At the identity layer, enforce least-privilege access using Azure RBAC with custom roles when built-in roles are too broad. Use Managed Identities for service-to-service authentication to eliminate stored credentials. Enable Conditional Access policies to require multi-factor authentication and compliant devices for administrative access.

At the data layer, enable encryption at rest using customer-managed keys (CMK) in Azure Key Vault when the default Microsoft-managed keys do not meet your compliance requirements. Enforce TLS 1.2 or higher for data in transit. Enable purge protection on any service that supports soft delete to prevent malicious or accidental data destruction.

At the monitoring layer, enable diagnostic logging and route logs to a centralized Log Analytics workspace. Configure Microsoft Sentinel analytics rules to detect suspicious access patterns, privilege escalation attempts, and data exfiltration indicators. Set up automated response playbooks that can isolate compromised resources without human intervention during off-hours.

Continuous Security Assessment

Security hardening is not a one-time activity. Azure services evolve continuously, introducing new features, deprecating old configurations, and changing default behaviors. Schedule quarterly security reviews to reassess your hardening posture against the latest Microsoft security baselines.

Use Microsoft Defender for Cloud’s Secure Score as a quantitative measure of your security posture. Track your score over time and investigate any score decreases, which may indicate configuration drift or new recommendations from updated security baselines. Set a target Secure Score and hold teams accountable for maintaining it.

Subscribe to Azure update announcements and security advisories to stay informed about changes that affect your security controls. When Microsoft introduces a new security feature or changes a default behavior, assess the impact on your environment and update your hardening configuration accordingly. Automate this assessment where possible using Azure Policy to continuously evaluate your resources against your security standards.

Conduct periodic penetration testing against your Azure environment. Azure’s penetration testing rules of engagement allow testing without prior notification to Microsoft for most services. Engage a qualified security testing firm to assess your Azure API Management deployment using the same techniques that real attackers would employ. The findings from these tests often reveal gaps that automated compliance scans miss.

Hardening Checklist

  1. Deploy in VNet (internal mode preferred)
  2. Enforce JWT validation on all APIs
  3. Rate limiting and quotas per consumer
  4. Strip backend headers from responses
  5. Restrict CORS to specific origins
  6. Use managed identity for backend auth
  7. Enable Defender for APIs
  8. Diagnostic logging to Log Analytics
  9. Disable legacy TLS protocols
  10. Store secrets in Key Vault via named values

For more details, refer to the official documentation: What is Azure API Management?, Policies in Azure API Management.

Leave a Reply