Skip to content

Why does the banking app break after enabling SSL inspection?

  • Home
  • Blog
  • Why does the banking app break after enabling SSL inspection?
Why does the banking app break after enabling SSL inspection?
Short answer

When a firewall decrypts HTTPS traffic and re-signs it with its own certificate authority (CA), devices that do not trust that CA and applications that use certificate pinning reject the connection. The fix has two parts: deploy the re-signing CA to every Windows device as a trusted root through Group Policy, and exclude applications that pin certificates or use client certificates (Windows Update, Microsoft 365, banking and e-signature clients) from the decrypt rule.

Symptoms: “NET::ERR_CERT_AUTHORITY_INVALID” and silent connection failures

  • The browser shows a “Your connection is not private” warning with the code NET::ERR_CERT_AUTHORITY_INVALID. In the certificate details, the issuer is the firewall’s CA rather than the bank’s (for example Fortinet_CA_SSL on a FortiGate).
  • A desktop banking or e-signature client opens but fails at sign-in with a generic “could not connect to server” type of error. The same bank website works in the browser.
  • The Windows Update scan fails; Outlook, Teams or OneDrive disconnect intermittently or become noticeably slow.
  • On mobile devices, especially Android, apps cannot reach the internet while the browser keeps working.
  • The firewall logs show repeatedly dropped or rejected TLS sessions for the same destination domains.

Root cause: the intercepting certificate, pinning and client certificates

With deep inspection, the firewall acts as the server towards the client: it decrypts the session, scans the content and re-encrypts it with a certificate signed by its own CA. Fortinet describes this as “the FortiGate impersonates the recipient of the originating SSL session, then decrypts and inspects the content” and re-encrypts it; Sophos likewise states that after inspection the traffic is re-encrypted with the re-signing CA you specify. Three separate failures follow from this design:

  • CA not deployed: the device cannot find the re-signing CA in its trusted root store and treats every site as suspicious. Fortinet states plainly that the warning appears because Fortinet_CA_SSL is not in the browser’s trusted CA list. Sophos also notes that if re-signing certificates are not trusted by endpoint devices, browsers show a warning and may refuse to complete the connection.
  • Certificate pinning: the application accepts only a specific certificate or issuer and rejects the connection even if your CA is a trusted root. Microsoft documents that Windows Update metadata connections are certificate-pinned and that TLS proxies must pass these connections without interception. According to Sophos, websites and applications that use pinning block the page fully or partially when inspection is on, and the error may not show an identifiable reason.
  • Mutual TLS (client certificates): when a smart card or e-signature presents a client certificate, the client signs the handshake with its own private key. The firewall does not have that key, so it cannot connect to the server on the client’s behalf; this traffic only works if it is passed through without decryption.

Microsoft 365 is a separate case. Microsoft lists TLS termination and deep packet inspection of Microsoft 365 domains among the scenarios it has not tested and that are known to cause connectivity issues, and recommends bypassing these domains from TLS decryption, traffic interception and deep packet inspection.

Step-by-step fix

  1. First confirm that the traffic is really being decrypted. On the affected client, the PowerShell snippet below prints the issuer of the certificate the server presents. If you see your firewall’s CA name instead of the bank’s or Microsoft’s CA, the connection is being inspected.
  2. Download the re-signing CA. On a FortiGate, go to Security Profiles > SSL/SSH Inspection and edit the deep-inspection profile; the default CA is Fortinet_CA_SSL, save it with Download. On Sophos Firewall, use the download button next to “Re-signing certificate authorities” under Rules and policies > SSL/TLS inspection rules > SSL/TLS inspection settings.
  3. Never deploy the Fortinet_CA_Untrusted certificate. Fortinet states that if warnings persist after importing Fortinet_CA_SSL, they come from Fortinet_CA_Untrusted and that this certificate must never be imported: that warning tells you the server really is untrusted.
  4. Deploy the CA with Group Policy. In Group Policy Management, edit a GPO linked to the relevant OU; under Computer Configuration\Policies\Windows Settings\Security Settings\Public Key Policies, right-click Trusted Root Certification Authorities and add the certificate with Import.
  5. On a client, confirm that the policy has applied and the certificate is in the local machine root store (adjust the search pattern to your CA name; command below).
  6. Build the exclusion list. On Sophos, the default “Exclusions by website or category” rule is fixed at the top of the table with the action “Don’t decrypt”; add problem domains to the Local TLS exclusion list under Web > URL groups. Sophos’s Managed TLS exclusion list, updated through firmware, also sits in this rule. On a FortiGate, clone the read-only built-in profile and add addresses, FQDNs, wildcard FQDNs or FortiGuard categories under “Exempt from SSL Inspection”; Fortinet suggests the Finance and Banking category to exempt all bank websites.
  7. For Microsoft 365, use the endpoint data Microsoft publishes (aka.ms/m365endpoints) as the source and exclude all “Required” domains. Microsoft states that it does not support selective allow-listing of only a few domains because it causes connectivity incidents for users.
  8. For Windows Update, exclude the DNS names listed in Microsoft’s Windows Update troubleshooting article. Microsoft does not publish IP addresses or ranges for these exceptions; do not write IP-based rules, use domain-based rules.
  9. Identify from the firewall logs the domains that banking, e-signature and e-Government (e-Devlet) related clients connect to and add them to the same list. Every connection that uses a client certificate must be in this list.
  10. Write a separate rule for Android and unmanaged devices. Sophos notes that Android devices are known to generate certificate errors and recommends creating an exclusion for all Android devices. Keep the guest network out of decryption as well.
  11. After the change, repeat the test from step 1: for excluded domains you should now see the site’s original issuer, not the firewall’s.
# Step 1
$h = "login.microsoftonline.com"
$c = New-Object System.Net.Sockets.TcpClient($h, 443)
$s = New-Object System.Net.Security.SslStream($c.GetStream(), $false, { $true })
$s.AuthenticateAsClient($h)
$s.RemoteCertificate.Issuer
$s.Dispose(); $c.Close()

# Step 5
gpupdate /force
Get-ChildItem Cert:\LocalMachine\Root |
  Where-Object { $_.Subject -like "*Fortinet*" -or $_.Subject -like "*Sophos*" } |
  Format-List Subject, Thumbprint, NotAfter

Sophos evaluates rules from the top down and applies the first match. Place your own “Don’t decrypt” rules above the general “Decrypt” rule; otherwise the exclusion never takes effect.

Long-term prevention

  • Enable deep inspection for a small pilot group first and widen the scope as your list of working applications grows.
  • When rolling out a new business application, test its domains against the inspection rules. On Sophos, you can add sites straight to the Local TLS exclusion list while troubleshooting in the Control center or Log viewer.
  • Put the expiry date of the re-signing CA in the calendar; when you renew the certificate, update the GPO as well. If you run an enterprise PKI, using a subordinate CA under your enterprise root, as Sophos suggests, makes deployment easier.
  • Microsoft recommends downloading and applying the Microsoft 365 endpoint list regularly and automatically; do not enter it once by hand and leave it.
  • Record the reason and date for every exclusion and review the exclusion list at regular intervals.

When to call an expert

If a particular application still cannot connect after you have deployed the CA and added the exclusions, you need to work out at packet level which domains it connects to and which authentication method it uses; that means reading firewall logs, the certificate chain and the client side together. As part of our security solutions (antivirus and firewall) service, Workas investigates exactly this kind of problem, which we encounter in the field at businesses in Denizli, and helps you roll out deep inspection without breaking business applications.

Frequently Asked Questions

I installed the CA on every computer, but the banking app still fails. Why?

The app most likely uses certificate pinning or a client certificate. Making the CA trusted is not enough in that case; you have to exclude the relevant domains from the decrypt rule.

Does exempting bank websites from inspection create a security gap?

Content in that traffic is not scanned, which is a trade-off. Fortinet itself suggests the Finance and Banking category to exempt all bank websites. Endpoint antivirus and EDR protection keep working on that traffic.

Does certificate inspection alone cause the same problem?

Certificate inspection does not decrypt the session; it only looks at the server name and certificate details, so it generally does not break pinned applications. The problem appears with deep inspection, which decrypts the content.

Should staff install the CA on their personal phones?

Installing a root certificate on unmanaged devices is impractical, and most mobile apps do not trust user-added CAs. Putting these devices on the guest network and keeping them out of decryption is the better approach.

Sources

  1. Sophos Firewall 21.5: SSL/TLS inspection rules
  2. Fortinet FortiOS 7.4.1: Deep inspection
  3. Microsoft Learn: Microsoft 365 network connectivity principles
  4. Microsoft Learn: Windows Update security
  5. Microsoft Learn: Distribute certificates to client computers by using Group Policy

Let's Get Started

Let's Work Together!

Let's plan your company's IT needs together — we'll quickly find the right solution for you.

x

Since 2002, Workas Software Technology has provided businesses in Denizli with ERP, cybersecurity, network, server and backup, custom software and AI solutions.

Address
Kınıklı, Hüseyin Yılmaz Cd. No:67,
B Blok Z06, 20160 Pamukkale/Denizli, Türkiye
Get in Touch
0549 669 99 06
0535 089 29 29
Working Hours
Mon - Sat: 8:00 - 18:00