Web Isolation Google Cloud Platform Migration FAQ
Article ID: 197350
Updated On:
Products
Issue/Introduction
This information is subject to change. Please check back often for updates.
Symantec's integration into Broadcom has presented operational and business opportunities that will enable us to sharpen our focus on delivering industry-leading security software for our customers. To help accelerate our cloud roadmap and strengthen integrations within our portfolio, we will consolidate our cloud environments into a single platform hosted in GCP.
Environment
Web Isolation Cloud Service
Resolution
Where was Web Isolation Cloud Service hosted prior to this change?
Web Isolation Cloud Service has been hosted in Amazon Web Services (AWS).
What are the benefits of operating from a common platform?
This change will allow us to accelerate the development of transformational cloud services while reducing latency of service-to-service communications (e.g.,Web Isolation to WSS) and providing greater scalability, and improved resilience.
How is Broadcom planning to achieve this?
Our cloud services that currently operate in Amazon Web Services (AWS) will be migrated to Google Cloud Platform (GCP). This transition will provide significant customer value and simplification of our operational environment.
What is the migration timeline?
We will begin to migrate customers on a weekly basis starting August 2020. This activity is expected to continue through the rest of calendar year 2020.
In simple terms, what does this migration mean?
Web Isolation cloud service will be co-located with WSS and other Symantec services, allowing for easier integration and better performance.
What is the migration plan?
We will notify you by email at least seven (7) calendar days in advance of your migration window along with any changes needed to ensure connectivity with the new environment.
How do I avoid an outage when Symantec migrates?
We expect that this process will involve a downtime window of 15 minutes or fewer, during which DNS will be updated to point to the new environment.
If additional steps are needed, we will provide instructions in your pre-migration email. If you encounter problems, please contact us at [email protected] for assistance. We will retain legacy environments for quick rollback if needed.
What are the new IP address ranges for GCP?
APAC
|
GCP Region Name |
Location |
Range |
First |
Last |
|
asia-east2 |
Hong Kong |
34.96.224.96/27 |
34.96.224.96 |
34.96.224.127 |
|
asia-northeast1 |
Tokyo, Japan |
34.84.38.0/25 |
34.84.38.0 |
34.84.38.127 |
|
asia-northeast3 |
Seoul, South Korea |
34.64.150.64/27 |
34.64.150.64 |
34.64.150.95 |
|
asia-south1 |
Mumbai, India |
34.93.178.192/26 |
34.93.178.192 |
34.93.178.255 |
|
asia-southeast1 |
Jurong West, Singapore |
34.87.130.0/24 |
34.87.130.0 |
34.87.130.255 |
|
australia-southeast1 |
Sydney, Australia |
34.87.246.64/27 |
34.87.246.64 |
34.87.246.95 |
EMEA
|
GCP Region Name |
Location |
Range |
First |
Last |
|
europe-west1 |
St. Ghislain, Belgium |
34.77.178.64/26 |
34.77.178.64 |
34.77.178.127 |
|
europe-west2 |
London, England, UK |
34.89.99.0/24 |
34.89.99.0 |
34.89.99.255 |
|
europe-west3 |
Frankfurt, Germany |
34.107.18.0/24 |
34.107.18.0 |
34.107.18.255 |
Americas
|
GCP Region Name |
Location |
Range |
First |
Last |
|
northamerica-northeast1 |
Montréal, Québec, Canada |
34.95.42.192/27 |
34.95.42.192 |
34.95.42.223 |
|
southamerica-east1 |
Osasco (São Paulo), Brazil |
34.95.154.64/27 |
34.95.154.64 |
34.95.154.95 |
|
us-east4 (range #1) |
Ashburn, Northern Virginia, USA |
34.86.18.0/25 |
34.86.18.0 |
34.86.18.127 |
|
us-east4 (range #2) |
Ashburn, Northern Virginia, USA |
34.86.99.0/24 |
34.86.99.0 |
34.86.99.255 |
|
us-west1 |
The Dalles, Oregon, USA |
34.105.99.0/24 |
34.105.99.0 |
34.105.99.255 |
|
us-west2 |
Los Angeles, California, USA |
34.94.230.64/27 |
34.94.230.64 |
34.94.230.95 |
What are you doing to mitigate risk?
We are reducing risk from multiple angles:
- Focus: All Web-Isolation teams are focused on the success of the migration and all other major projects have been put on hold to minimize distractions.
- Expertise: We have retained Google as a consultant to ensure optimal planning, communication, and execution.
- Consistency: We are lift-and-shifting the architecture with only minimal changes to reduce risk.
- Slow roll pilot: Apart from extensive pre-migration testing, we will pilot the smallest, lowest risk sites first, and only after a record of successful small site migrations will we move on to larger sites.
What is your contingency plan?
Our plan allows us to roll back to the existing AWS environment at any point during the migration.
Will the SLA (Service Level Agreement) change?
No, our SLA will not change.
Will the user experience change? Will I have to retrain my users and IT support staff?
No, the application-level functionality is not changing. In fact, the vast majority of our platform and application code is moving over untouched. Some of the underlying components require adjustments for compatibility with GCP, but these do not impact the user experience.
Do I have to save or download my data for it to migrate?
No, all customer data will be securely migrated by Symantec.
Is encryption of data in transit and data at rest being changed?
Encryption in all phases will meet or exceed what is currently deployed.
What is the impact on service availability and RTO/RPO?
No change in the SLA or RTO/RPO.
Additional Information
Cloud Data Privacy - https://cloud.google.com/security/privacy
Cloud Compliance - Regulations & Certifications - https://cloud.google.com/security/compliance/offerings/#/
Feedback
