Internet Access TLS inspection FAQ
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit e3b5d6b · +8 −11 lines · also on GitHub
⋯ 17 unchanged lines
1818
- question: What is Transport Layer Security (TLS) inspection?
1919
answer: |
2020
TLS inspection decrypts and analyzes encrypted network traffic to help organizations detect threats, enforce security policies, and prevent data exfiltration. With the majority of internet traffic now encrypted,
21
− TLS inspection provides visibility into data flows that would otherwise be opaque to security tools. This capability enables enterprises to apply advanced protections such as content filtering without compromising
21
+ TLS inspection provides visibility into data flows that would otherwise be opaque to security tools. TLS inspection enables enterprises to apply advanced protections such as content filtering without compromising
2222
the confidentiality of legitimate communications.
2323
2424
- question: How does TLS inspection work?
⋯ 6 unchanged lines
3131
- Configure Conditional Access: Create a Conditional Access policy and associate it with the Global Secure Access security profile linked to the TLS policy.
3232
- Distribute the trusted certificate: Ensure the selected certificate authority is installed on all client devices to establish trust and enable seamless TLS inspection.
3333
34
− - question: What is certificate pinning, and how does it affect TLS inspection?
35
− answer: |
36
− Certificate pinning is a security mechanism that restricts an application's TLS connections to a specific set of trusted certificates or public keys. This ensures that the application only communicates with servers presenting those exact credentials, even if other certificates are valid and trusted by the system.
37
− This technique helps defend against man-in-the-middle (MITM) attacks by preventing unauthorized interception of encrypted traffic. However, it also interferes with network security tools that rely on TLS inspection, which works by decrypting and re-encrypting traffic using an intermediary certificate.
38
− To maintain compatibility with applications that enforce certificate pinning, it may be necessary to configure bypass rules that exclude those destinations from TLS inspection. This allows the application to function as intended while preserving inspection capabilities for other traffic.
39
−
4034
- question: Why do I receive the error "SSL certificate problem unable to get local issuer certificate" when using Git?
4135
answer: |
4236
This error occurs because certain developer tools (such as Git) don't use the operating system's certificate store by default; instead, they maintain their own certificate store. One way to resolve this is to append the certificate to Git’s Certificate Authority bundle.
43
− The following PowerShell script demonstrates how to do this on a Windows system.
44
−
37
+ The following PowerShell script demonstrates how to add the certificate to Git’s CA bundle on a Windows system.
4538
```powershell
4639
# Define the path to your custom root Certificate Authorities
4740
$certPath = "./myTLSInspectionRootCA.crt"
⋯ 15 unchanged lines
6356
Write-Host "Git CA bundle path not found. Is Git installed and configured?"
6457
}
6558
```
66
−
59
+ - question: What is certificate pinning, and how does it affect TLS inspection?
60
+ answer: |
61
+ Certificate pinning is a security mechanism that restricts an application's TLS connections to a specific set of trusted certificates or public keys. Certificate pining ensures that the application only communicates with servers presenting those exact credentials, even if other certificates are valid and trusted by the system.
62
+ This technique helps defend against man-in-the-middle (MITM) attacks by preventing unauthorized interception of encrypted traffic. However, it also interferes with network security tools that rely on TLS inspection, which works by decrypting and re-encrypting traffic using an intermediary certificate.
63
+
6764
- question: How should I handle applications that use certificate pinning?
6865
answer: |
69
− The connection fails if TLS inspection terminates traffic from applications that use certificate pinning. To ensure your applications work as expected, create a custom bypass rule in the traffic forwarding profile to exclude traffic from these applications from Global Secure Access. You can perform this operation as part of custom bypass in the [Internet access forwarding profile](/mem/intune/protect/compliance-custom-script). We're working on custom TLS rules to let you acquire traffic and bypass TLS inspection only.
66
+ The connection fails if TLS inspection terminates traffic from applications that use certificate pinning. To ensure your applications work as expected, create a custom bypass rule in the traffic forwarding profile to exclude traffic from these applications from Global Secure Access. You can perform this operation as part of custom bypass in the [Internet access forwarding profile](/mem/intune/protect/compliance-custom-script). We're working on custom TLS rules to let you acquire traffic and bypass TLS inspection only.
7067
7168
- question: Is TLS 1.3 supported?
7269
answer: Microsoft Entra TLS inspection enables TLS 1.2 and TLS 1.3 by default. The highest mutually supported version is selected for the session, from the client to Global Secure Access and from Global Secure Access to the destinations. Microsoft Entra doesn't support TLS 1.3 with Encrypted Client Hello (ECH) because the Server Name Indication (SNI) is encrypted, which prevents Global Secure Access from creating the corresponding leaf certificates for TLS termination.
⋯ 15 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 17:01 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.