last sync: 2025-Jul-01 17:24:08 UTC

API Management APIs should use only encrypted protocols

Azure BuiltIn Policy definition

Source Azure Portal
Display name API Management APIs should use only encrypted protocols
Id ee7495e7-3ba7-40b6-bfee-c29e22cc75d4
Version 2.0.2
Details on versioning
Versioning Versions supported for Versioning: 1
2.0.2
Built-in Versioning [Preview]
Category API Management
Microsoft Learn
Description To ensure security of data in transit, APIs should be available only through encrypted protocols, like HTTPS or WSS. Avoid using unsecured protocols, such as HTTP or WS.
Cloud environments AzureCloud = true
AzureUSGovernment = unknown
AzureChinaCloud = unknown
Available in AzUSGov Unknown, no evidence if Policy definition is/not available in AzureUSGovernment
Assessment(s) Assessments count: 1
Assessment Id: 741b141d-8111-4d86-a4e0-f74b06270a74
DisplayName: API Management APIs should use only encrypted protocols
Description: To ensure security of data in transit, APIs should be available only through encrypted protocols, like HTTPS or WSS. Avoid using unsecured protocols, such as HTTP or WS.
Related OWASP API Security Top 10 Risks: (API8:2023) Security Misconfiguration
Remediation description: To set an API to HTTPS or WSS only for API Management Apis: 1. In the Azure portal, find your API Management Resource 2. Navigate to APIs and select the API 4. Select Settings 5. Under URL Scheme, select HTTPS for HTTP Apis, WSS for WebSocket Apis.
Categories: Compute
Severity: High
User impact: High
Threats: DataExfiltration
Mode All
Type BuiltIn
Preview False
Deprecated False
Effect Default
Audit
Allowed
Audit, Disabled, Deny
RBAC role(s) none
Rule aliases IF (1)
Alias Namespace ResourceType Path PathIsDefault DefaultPath Modifiable
Microsoft.ApiManagement/service/apis/protocols[*] Microsoft.ApiManagement service/apis properties.protocols[*] True False
Rule resource types IF (1)
Compliance
The following 12 compliance controls are associated with this Policy definition 'API Management APIs should use only encrypted protocols' (ee7495e7-3ba7-40b6-bfee-c29e22cc75d4)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
Azure_Security_Benchmark_v3.0 DP-3 Azure_Security_Benchmark_v3.0_DP-3 Microsoft cloud security benchmark DP-3 Data Protection Encrypt sensitive data in transit Shared **Security Principle:** Protect the data in transit against 'out of band' attacks (such as traffic capture) using encryption to ensure that attackers cannot easily read or modify the data. Set the network boundary and service scope where data in transit encryption is mandatory inside and outside of the network. While this is optional for traffic on private networks, this is critical for traffic on external and public networks. **Azure Guidance:** Enforce secure transfer in services such as Azure Storage, where a native data in transit encryption feature is built in. Enforce HTTPS for workload web application and services by ensuring that any clients connecting to your Azure resources use transportation layer security (TLS) v1.2 or later. For remote management of VMs, use SSH (for Linux) or RDP/TLS (for Windows) instead of an unencrypted protocol. Note: Data in transit encryption is enabled for all Azure traffic traveling between Azure datacenters. TLS v1.2 or later is enabled on most Azure PaaS services by default. **Implementation and additional context:** Double encryption for Azure data in transit: https://docs.microsoft.com/azure/security/fundamentals/double-encryption#data-in-transit Understand encryption in transit with Azure: https://docs.microsoft.com/azure/security/fundamentals/encryption-overview#encryption-of-data-in-transit Information on TLS Security: https://docs.microsoft.com/security/engineering/solving-tls1-problem Enforce secure transfer in Azure storage: https://docs.microsoft.com/azure/storage/common/storage-require-secure-transfer?toc=/azure/storage/blobs/toc.json#require-secure-transfer-for-a-new-storage-account n/a link 15
DORA_2022_2554 9.3a DORA_2022_2554_9.3a DORA 2022 2554 9.3a 9 Implement Secure Data Transfer Solutions for ICT Systems Shared n/a Leverage information and communication technology (ICT) solutions and processes that ensure the security of data transfer methods to protect against unauthorized access and data breaches. 50
DORA_2022_2554 9.3b DORA_2022_2554_9.3b DORA 2022 2554 9.3b 9 Minimize Risks of Data Corruption and Loss in ICT Processes Shared n/a Implement information and communication technology (ICT) processes that minimize the risk of data corruption or loss, unauthorized access, and technical flaws that may disrupt business activities. 36
EU_AI_Act_2024_1689 15.5 EU_AI_Act_2024_1689_15.5 EU AI Act 2024 1689 15.5 15 Implement Cybersecurity Measures for High-Risk AI Systems Shared n/a Confirm high-risk AI systems are resilient against unauthorized attempts to alter their use or performance. Implement appropriate technical solutions to address vulnerabilities, including measures to prevent, detect, and respond to data poisoning, model poisoning, and adversarial attacks. 6
EU_AI_Act_2024_1689 55.1d EU_AI_Act_2024_1689_55.1d EU AI Act 2024 1689 55.1d 55 Ensure Cybersecurity for General-Purpose AI Models with Systemic Risk Shared n/a Ensure, as required for AI providers of general-purpose AI models with systemic risk, an adequate level of cybersecurity for both the model and its supporting physical infrastructure. 6
K_ISMS_P_2018 2.10.1 K_ISMS_P_2018_2.10.1 K ISMS P 2018 2.10.1 2.10 Establish Procedures for Managing the Security of System Operations Shared n/a Establish and implement operating procedures for managing the security of system operations such as designating system administrators, updating policies, changing rulesets, monitoring events, managing policy implementations or exceptions. 455
K_ISMS_P_2018 2.10.2 K_ISMS_P_2018_2.10.2 K ISMS P 2018 2.10.2 2.10 Establish Protective Measures for Administrator Privileges and Security Configurations Shared n/a Establish and implement protective measures with regard to administrator privileges and security configurations to ensure that important information and personal information are not exposed as a result of unauthorized access by service type or misconfigurations. 431
K_ISMS_P_2018 2.10.4 K_ISMS_P_2018_2.10.4 K ISMS P 2018 2.10.4 2.10 Establish Protective Measures when Working with Electronic Transactions or Fintech Services Shared n/a Establish and implement protective measures such as authentication and encryption to prevent information leakage, data alteration, or fraud when working with electronic transactions and Fintech services. In the event connections to external systems are required, safety must be checked. 45
K_ISMS_P_2018 2.10.5 K_ISMS_P_2018_2.10.5 K ISMS P 2018 2.10.5 2.10 Establish Secure Data Transmission Procedures with External Organizations Shared n/a Establish secure transmission policies, transmission methods, and technical measures for protecting personal information and important information if transmitting data to external organizations. Agreement on management responsibilities for data transmission must be established. 30
K_ISMS_P_2018 2.7.1b K_ISMS_P_2018_2.7.1b K ISMS P 2018 2.7.1b 2.7 Ensure Data is Encrypted at Rest and In-Transit Shared n/a Ensure data is encrypted when storing and transmitting personal and important information. 70
New_Zealand_ISM 17.1.55.C.03 New_Zealand_ISM_17.1.55.C.03 New_Zealand_ISM_17.1.55.C.03 17. Cryptography 17.1.55.C.03 Information and Systems Protection n/a Agencies MUST encrypt aggregated agency data using an approved algorithm and protocol over insecure or unprotected networks such as the Internet, public infrastructure or non-agency controlled networks when the compromise of the aggregated data would present a significant impact to the agency. 1
U.05.1 - Cryptographic measures U.05.1 - Cryptographic measures 404 not found n/a n/a 18
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type polSet in AzUSGov
DORA 2022 2554 f9c0485f-da8e-43b5-961e-58ebd54b907c Regulatory Compliance GA BuiltIn unknown
Enforce recommended guardrails for API Management Enforce-Guardrails-APIM API Management GA ALZ
EU AI Act 2024 1689 1308bccf-446a-4283-a4e0-0c983fe7a572 Regulatory Compliance GA BuiltIn unknown
K ISMS P 2018 e0782c37-30da-4a78-9f92-50bfe7aa2553 Regulatory Compliance GA BuiltIn unknown
Microsoft cloud security benchmark 1f3afdf9-d0c9-4c3d-847f-89da613e70a8 Security Center GA BuiltIn true
New Zealand ISM 4f5b1359-4f8e-4d7c-9733-ea47fcde891e Regulatory Compliance GA BuiltIn unknown
NL BIO Cloud Theme V2 d8b2ffbe-c6a8-4622-965d-4ade11d1d2ee Regulatory Compliance GA BuiltIn unknown
History
Date/Time (UTC ymd) (i) Change type Change detail
2023-03-27 17:43:07 change Patch (2.0.1 > 2.0.2)
2022-07-08 16:32:07 change Patch (2.0.0 > 2.0.1)
2022-06-24 19:15:47 change Major (1.0.0 > 2.0.0)
2022-06-17 16:31:08 add ee7495e7-3ba7-40b6-bfee-c29e22cc75d4
JSON compare
compare mode: version left: version right:
JSON
api-version=2021-06-01
EPAC