Pre-migration XSOAR 6 to XSOAR 8 questionnaire for customers
You can use the following Google form to provide requested information per your Xsoar instance. (Please fill the form separately for your hosted Development and Production system)
Email *
Customer Name *
Serial number *
Your serial number can be found as a part of the XSOAR URL. For example: If your Xsoar URL is; 02714585938.dev.xsoar.paloaltonetworks.com, your serial is 02714585938. In case you don’t have the serial# in the URL address, it can also be found by looking at your CSP(Customer Success Portal) account, or by running dig / nslookup commands against your Xsoar URL addresses.
XSOAR Instance Type (DEV or PROD) *
Cortex XSOAR 6 FQDN *
FQDNs can be found in the URL used to access the XSOAR 6 instance (Dev, Prod, etc.). Please share the full domain name, starting right after the https:// and ending with the first / in the URL you use to browse.
For example, in case you use the following URL to access your Cortex XSOAR 6:
https://02714585938.dev.xsoar.paloaltonetworks.com/#/incidents, the FQDN is 02714585938.dev.xsoar.paloaltonetworks.com.

List of Admins

 *

Please provide us with a list of admin user emails who will be responsible for driving the migration process. Only these designated admins will be granted access to the Cortex XSOAR 8 environment during the UAT phase. These users will be the XSOAR 8 UAT tenant admins and will have Administrator permissions on the UAT tenant. Please provide the email addresses of these users as defined in your Cortex XSOAR 6 system.

It is important to note that you do not need to include all users who use the Cortex XSOAR 6 system in this list. All users will be migrated.

The list you share with us should only include the users who will actively perform the migration and use the Cortex XSOAR 8 system during the UAT.

Custom Cortex XSOAR 8 Access URL FQDN Request (optional)

As part of the migration, there will be a change in the URL used to access the Cortex XSOAR 8 system. We auto-generate a new URL as part of the Cortex XSOAR 8 instance deployment.

You have the option to customize the Fully Qualified Domain Name (FQDN) either before the migration or after the cutoff. However, please do not change the URL during the migration itself.

If you choose to customize your FQDNs prior to migration, please share the desired subdomain name you would like to use.

Note that the FQDN is public, so you might prefer to avoid including sensitive information such as your company name.

Example of a customized FQDN: companyprod.x.com

Example of a default FQDN: 54227308933prod.x.com

Note that ‘-’ is not allowed in the XSOAR 8 domain name.
Remote Repositories(Dev to Prod) Usage *
XSOAR 8 has introduced support for a built-in content repository. Please inform us if you are currently utilising your own private content repository in XSOAR 6 and your preferences regarding the configuration of this setting for your XSOAR 8 tenant.
Private Git Repository - Branch Name (optional)
XSOAR 8 has introduced support for a built-in content repository. By default flow, if you were using a remote content repository(Dev to Prod by Git Repos) in XSOAR 6, your tenant will be configured to utilise a built-in repository.

Per your answer to the previous question, if you prefer to continue using a private repository instead, please specify a new branch name that will be generated on your Git Repos as part of the migration process. It's important to note that this branch should not exist in your repository, please do not create this new branch as it will be created during the migration process.

The built-in repository doesn't accommodate multiple branches and consistently employs the same branch. Therefore, if your development and production tenants are not using the same/single branch, you must provide new branch names for your XSOAR 8 tenants.

LDAP Authentication:

 *

Please note that LDAP authentication, which is enabled in your Cortex XSOAR 6 environment, is currently not supported in Cortex XSOAR 8. To ensure the highest level of security, we recommend transitioning to Single Sign-On (SSO) authentication, which is the recommended method in Cortex XSOAR 8.

Please let us know if you plan to continue using non-SSO LDAP authentication in Cortex XSOAR 8, although it is not recommended for SaaS platforms.

XSOAR Features Usage [Optional - only if being used]:

Certain technologies influence the prioritisation of the  migration planning, please let us know if you are actively using one or more of these features in your instance:
Date asked by the customer
Additional details / comments
Other Important Actions:
Adding the new Cortex XSOAR 8 IPs to the Allow List in the Firewall:

As Cortex XSOAR 8 has different source IPs than your Cortex XSOAR 6 tenant, the outgoing traffic from the server will now originate from distinct source IPs. 

Due to these changes, it is important to add these IPs to your Firewall Allow List if you have previously added the Cortex XSOAR 6 IPs.

Please refer to the initial migration details email that you've received for your regions IP list.

Please keep the Cortex XSOAR 6 IP and its redundancy pair in the allow list until the migration is complete.

Resource Recommendations

To familiarize yourself with the new features and improvements in XSOAR 8, we recommend reviewing the following resources:

Submit
Clear form
Never submit passwords through Google Forms.
This form was created inside of Palo Alto Networks Inc. Report Abuse
Google Forms