Notice of Datacenter Migration of Qualys India Platform 1 Shared Cloud Platform (SCP)

Lane Smith
Lane Smith, Vice President, Global Customer Support, Qualys
- 3 min read

Last updated on: August 6, 2024

Table of Contents

This advance notification is to inform customers with subscriptions on the IN Platform 1 platform that we will be migrating from our existing colocation datacenter-only setup to a hybrid cloud setup, leveraging a colocation datacenter along with Public Cloud. This migration is scheduled to take place on 22nd August 2024 and will require a 15-hour downtime.

Please refer to the Frequently Asked Questions (FAQs) below to learn more about the benefits of this move and what is needed from customers to ensure a smooth transition.

Frequently Asked Questions

What is the scope of the migration activity?

The Qualys IN Platform 1 Shared Cloud Platform (SCP) will undergo a migration to a hybrid cloud setup. All customer data will be moved along with all applications and services from the existing SCP environment in the current data center to the new hybrid cloud environment.

When is this activity scheduled?

This migration will take place on Thursday, August 22nd, 2024, from 18:00 PM Indian Standard Time (IST). It will take place during the scheduled Quarterly Maintenance Downtime for the IN01 Platform.

Will there be any impact on customers during this migration?

Qualys services will be unavailable during this migration as we migrate customer data along with the applications and services to the Hybrid Cloud Environment. Scans using an external scanner might get interrupted until the platform is back online. Qualys recommends pausing scans and then resuming them once the platform is online. The IP address used for communication between Cloud Agents / Scanner Appliances / Qualys Gateway Appliance and the Shared Cloud Platform will partially change.

Which customers are affected by this migration?

Customers with subscriptions on the IN1 platform will be affected. Please refer to https://www.qualys.com/platform-identification/ for help identifying your platform.

What testing has been done?

Qualys operations teams have completed extensive testing of the migration process. We have also successfully migrated our other shared cloud platforms in other regions in a seamless manner

What steps does the customer need to take?

As part of the migration, the IPv4 addresses associated with the FQDNs (URLs) & Scanners will be changed. Customers who have already whitelisted the Qualys subnets 103.75.173.0/24 & 103.216.98.0/24 and allowed traffic in both directions (incoming & outgoing) to & from both subnets, there is no change to them. Only those customers who have allowed specific IP of IND pod are requested to add the additional IP below to the Allowlist to ensure uninterrupted connectivity with the Qualys services & scanners. Customers are requested not to remove the existing IP addresses until further notice. The additional IP addresses are within the existing Security Operations Center (SOC) netblock.

URLExisting IP AddressAdditional IP address to whitelistServiceTraffic direction
qualysapi.qg1.apps.qualys.in103.216.98.34103.75.173.129HTTP, HTTPSOutgoing
qgadmin.qg1.apps.qualys.in103.216.98.35103.75.173.130HTTP, HTTPSOutgoing
distribution.qg1.apps.qualys.in103.216.98.36103.75.173.131HTTP, HTTPSOutgoing
monitoring.qg1.apps.qualys.in103.216.98.37103.75.173.132HTTP, HTTPSOutgoing
download.qg1.apps.qualys.in103.216.98.38103.75.173.133HTTP, HTTPSOutgoing
certs.qg1.apps.qualys.in103.216.98.39103.75.173.134HTTP, HTTPSOutgoing
qagpublic.qg1.apps.qualys.in103.216.98.40103.75.173.135HTTP, HTTPSOutgoing
scanservice1.qg1.apps.qualys.in103.216.98.41103.75.173.136HTTP, HTTPSOutgoing
portal-bo.qg1.apps.qualys.in103.216.98.42103.75.173.137HTTP, HTTPSOutgoing
rns.qg1.apps.qualys.in103.216.98.43103.75.173.138HTTP, HTTPSOutgoing
rns-bo.qg1.apps.qualys.in103.216.98.44103.75.173.139HTTP, HTTPSOutgoing
cmsqagpublic.qg1.apps.qualys.in103.216.98.46103.75.173.140HTTP, HTTPSOutgoing
nac-le-service.qg1.apps.qualys.in103.216.98.48103.75.173.141HTTP, HTTPSOutgoing
gateway.qg1.apps.qualys.in103.216.98.49103.75.173.142HTTP, HTTPSOutgoing
camspublic.qg1.apps.qualys.in103.216.98.50103.75.173.143HTTP, HTTPSOutgoing
camspm.qg1.apps.qualys.in103.216.98.51103.75.173.144HTTP, HTTPSOutgoing
camsrepo.qg1.apps.qualys.in103.216.98.52103.75.173.145HTTP, HTTPSOutgoing
qpatchpublic.qg1.apps.qualys.in103.216.98.53103.75.173.146HTTP, HTTPSOutgoing
wasoob-dns.in1.qualysperiscope.com103.216.98.54103.75.173.147DNSOutgoing
kube.qg1.apps.qualys.in103.216.98.55103.75.173.148HTTP, HTTPSOutgoing
semca.qg1.apps.qualys.in103.216.98.56103.75.173.149HTTP, HTTPSOutgoing
debug.qg1.apps.qualys.in103.216.98.59103.75.173.150HTTP, HTTPSOutgoing
     
Scanner Block103.75.173.0- 103.75.173.127 (103.75.173.0/25)103.216.98.129- 103.216.98.254 (103.216.98.128/25)ANYIncoming
Share your Comments

Comments

Your email address will not be published. Required fields are marked *