How are Web Isolation Cloud policies migrated to CloudSWG ?

Products

• Cloud Secure Web Gateway
• Web Isolation Cloud

Issue/Introduction

I have read the official announcement regarding the migration from Web Isolation Cloud to Cloud Secure Web Gateway(CloudSWG).
Although it states that settings will be migrated, I have noticed some technical discrepancies.
Web Isolation Cloud supports wildcards (*), which are not supported in CloudSWG. Additionally, I am aware that using regular expressions in CloudSWG results in errors.

Could you clarify how these specific objects will be migrated to CloudSWG?

I want to know below.

• *.example.com
• *.www_mydomain.com/*
• http://*
• www.example\..+\.com\.

Environment

CloudSWG
Web isolation Cloud

Resolution

That regular expressions and asterisk-based syntax are currently not supported for URL definitions in Cloud SWG.
That said, I would like to clarify that Cloud SWG automatically treats all URLs as matching all possible subdomains and all possible paths. In other words, specifying example.com is effectively equivalent to [*.]example.com/*.
With regard to the http://* syntax, there is currently no way to match traffic based solely on the URL scheme. 
However, if you default rule is set to Isolate, there is no need to create a separate http://* isolation rule, as it would be redundant.

To address your question more specifically:

• *.example.com
  • → example.com
• *.www_mydomain.com/*
  • → www_mydomain.com
• http://*
  • → No translation; at this time, it would be converted into an object that is never matched
• Regular expressions
  • →Regular expressions are not supported. Attempting to migrate a RegEx-based object will result in an error, and the object will not be created in Cloud SWG.