Now traffic that is destined for the URLs in the exemption group will not have the Full packet scan performed but all other traffic will continue to be fully inspected.Set the SSL Inspection profile to a profile that does not perform Full packet inspection. Open the Windows Task Manager (On the keyboard, hold the Ctrl, Shift, and Esc keys simultaneously) Open the Processes tab Right-click on the processes associated with CCleaner CCleaner64 (and any other processes related to CCleaner or ccsetup) Click End Process > End process 2.Remove all other addresses from the Destination field.In the 'Destination' field add the “SSL Full inspection exemption” list you created above.Edit the copy and name it something like “Bypass SSL Inspection”.

Paste the copy above the normal outgoing traffic policy.Make a copy of the policy being used for normal outgoing traffic.Then exempt those addresses in the SSL Inspection Profile that is being used for the Policy.You can place the addresses into a group if you like. Create an address for each of the URLs provided.Additionally, it needs to be able to communicate with the following domains: Informationįor CCleaner Cloud to connect, it needs access to port 443, and port 8080. Please find a solution below: IssueĪfter enabling full SSL inspection on the normal outgoing traffic policy on Fortigate CCleaner Cloud agents could not connect to the cloud service. According to CrowdStrike, this backdoor was discovered embedded in the legitimate, signed version of CCleaner 5.33, and thus constitutes a supply chain. There is a known issue with CCleaner Cloud if SSL Full inspection is enabled within Fortigate.

Ccleaner dl