CyberCNS V3 to V4 Migration Information
- Vrushali
Welcome Email
Once your new V4 tenant is ready for login and migration, you will receive an email containing instructions for setting up your login and accessing the V4 portal; sample email notification below.
NOTE:
Emails are sent from notifications@connectsecure.com
V4 tenant will have information flowing once the new companies are added as per the Onboarding Guide OR once the companies are migrated from V3 instance.
V3 existing platform will be running in parallel over the next 90 days.
Migration Steps (How to Migrate Companies and Settings)
NOTE:
Only users with ADMIN security role permissions can perform migration actions.
Migration process installs the new (V4) agent, but does not uninstall the old one (V3).
Only the agents that are online can be migrated while the migration of the company is initiated.
Agents will have an option to restart migration under V3 Probes/Agents.
Once all the old (V3) agents are migrated, uninstall of old (V3) agents can be performed.
Post agent uninstall from V3, deletion of those agents from V3 dashboard and or deletion of the company can be performed.
Automated Migrations: Migrations are set to automatic to avoid any manual intervention from 2nd Jan 2023.
In your current V3 CyberCNS portal, when the migration is available for your tenant, you will see the 'Migrate Company' icon available on the top navigation toolbar.
Tap on the Migrate Company icon to display the list of current companies to be migrated.
You can monitor the status of the migration(s) progress from the right side of the panel.
You will also see the total global progress of all companies from the dashboard view at the top.
Migration Details (What is Migrating?)
What is migrating from V3 to V4?
The good news is that most of your settings will be migrating to V4 during this process!
When migrating a company from the V3 to the V4 portal, please see the table below for a list of the configurations, features, and settings that will automatically be migrated and what will not.
General Information | Status |
|---|---|
Tenant Mapping | Pass |
Company Migration | Pass |
Company Migration Set of 10 | Pass |
Company Mapping | Pass |
Company Details | Pass |
Company Description and Details | Pass |
User Migration & Roles | Status |
All users should migrate from V3 to V4 | Pass |
Users with Admin should remain as Admin | Pass |
Users with Custom Roles should be set as No-Role | Pass |
Users with ITADMIN and allowed companies should remain the same in V4 | Pass |
Users with ITADMIN and denied companies should remain the same in V4 | Pass |
Users with ITADMIN should remain as ITADMIN | Pass |
Users with No-Role should remain as No-Role | Pass |
Users with Read Only will be given Viewer access | Pass |
Verify Email Being Received | Pass |
SSO Login & Users | Status |
Authentication Providers | Not Migrating |
Agent Migration | Status |
After Migration V3 & V4, agents should be running | Pass |
Agent Credentials Encryption and decryption should happen as in V3 | Pass |
Agent Credentials should map to the same agent | Pass |
Agent details and the last scanned time should be migrated | Pass |
Agents should receive a new agent installation job | Pass |
Lightweight agent: No need to download probe dependencies | Pass |
Probe: Download all dependencies | Pass |
Discovery Settings and Credentials | Status |
Firewall credentials should be as firewall OS | Pass |
Migrate all sets of credentials | Pass |
Migrate both exclude and include discovery settings | Pass |
Company Settings | Status |
AD audit tag | Pass |
Agent deprecation | Pass |
Asset deprecation | Pass |
Backup software | Pass |
Default tags | Pass |
Deprecated asset retention period | Pass |
EDR application | Pass |
Manage tags | Pass |
Patching status | Pass |
Ports policy settings: Exclude and include ports | Pass |
Suppress vulnerabilities | Pass |
Integrations | Status |
Alerts: Check credentials and company mappings | Pass |
Associated company and agent for firewall | Pass |
Azure AD section: Verify credentials set, company mappings, sync option | Pass |
Company mappings | Pass |
Credentials migration for all integrations | Pass |
Email: Check credentials and company mappings | Pass |
Firewall: Check credentials and associated company; also, check credentials updated as firewallOS under the Agent credentials section | Pass |
Event Sets | Not Migrating |
Nucleus security: Check credentials & company mappings | Pass |
PSA: Check the Credentials section and credentials profile count, Integration profile, and Manage company mappings | Pass |
PII Scan Profile | Status |
PII scan profile Global | Pass |
PII scan profile migration: Map to the same agents as V3 | Pass |
External Scan Profiles & Configurations | Status |
Configuration Settings (Discovery Settings) migration | Pass |
External scan profile migration | Pass |
Service detection settings: Exclude from migration | Pass |
Attack Surface Mapper | Status |
Attack Surface Mapper Profile | Pass |
Assets | Status |
Check updated assets | Pass |
Probe: Initiate Full scan and verify agent; for DC machines, check Ad data | Pass |
Application Baseline Rules | Status |
Company- Appbaseline profile | Pass |
Global- Appbaseline profile | Pass |
Schedulers | Pass |
Deprecated Agents | Not Migrating |
One Time Assessments | Not Migrating |
Global Settings | Status |
Agent Deprecation Days | Pass |
Asset deperecation days | Pass |
Backup Software | Pass |
Custom Domain Name | Pass |
Default Tags | Pass |
Deprecated Asset Retention Period | Pass |
EDR Applications Excluded | Pass |
Excluded Ports | Pass |
Insecure Ports | Pass |
Manage Tags | Pass |
Patching Status | Pass |
Select Date Format | Pass |
Session Timeout | Pass |
Suppress Vulnerabilities Days for Microsoft Patches | Pass |
Timezone Settings | Pass |
White Label Settings | Pass |
Post Migration Updates
Here are some items to consider once you have completed migration to V4.
Login to the V4 portal and verify company data and settings (report any issues to our Support Team)
Reconfigure Authentication Providers (login methods) since they are not migrated.
Reconfigure ‘Event Sets’ for any Integrations.
Update any agent installation automation, maintenance, or scripting; the new URL for RMM or scripting installation should be NEEDURL
Need Help?
You can contact our support team by emailing support@cybercns.com or visiting our Support Portal at cybercns.freshdesk.com
Please let us know your tenant/domain name if you request support assistance.