...
...
...
...
...
...
...
...
...
...
...
...
| Info |
|---|
|
...
| Table of Contents | ||
|---|---|---|
|
...
ConnectSecure V4 Agent Prerequisites
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Please visit the link below to view the V4 agent prerequisites to confirm compability and runtime requirements to ensure a fully functional agent: V4 Agent Configurations |
Your ConnectSecure tenant information is under the Info icon shown below.
...
This will include your Tenant Name, Base URL, POD (Region), Welcome information, and Documentation Links library.
...
Replication Status ⚙️
You can check the status of your replication directly inside the new V4 portal by clicking the user avatar and selecting Replication Status. This process can take 24 to 48 hours to complete and will only include the online agents; offline agents must be re-tried when they are online.
...
| Note |
|---|
NOTE: This action runs the replication for ALL companies. |
...
Replication Details (What is Replicating?)
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 replicated and what will not.
...
General Information | Status |
|---|---|
Tenant Mapping |
|
Company replication |
|
Company replication Set of 10 |
|
Company Mapping |
|
Company Details |
|
Company Description and Details |
|
User replication & Roles | Status |
All users should migrate from V3 to V4 |
|
Users with Admin should remain as Admin |
|
Users with Custom Roles should be set as No-Role |
|
Users with ITADMIN and allowed companies should remain the same in V4 |
|
Users with ITADMIN and denied companies should remain the same in V4 |
|
Users with ITADMIN should remain as ITADMIN |
|
Users with No-Role should remain as No-Role |
|
Users with Read Only will be given Viewer access |
|
Verify Email Being Received |
|
SSO Login & Users | Status |
Authentication Providers | 🔴 Not Replicating |
Agent replication | Status |
After replication V3 & V4, agents should be running |
|
Agent Credentials Encryption and decryption should happen as in V3 |
|
Agent Credentials should map to the same agent |
|
Agent details and the last scanned time should be replicated |
|
Agents should receive a new agent installation job |
|
Lightweight agent: No need to download probe dependencies |
|
Probe: Download all dependencies |
|
Discovery Settings and Credentials | Status |
Firewall credentials should be as firewall OS |
|
Migrate all sets of credentials |
|
Migrate both exclude and include discovery settings |
|
Company Settings | Status |
AD audit tag |
|
Agent deprecation |
|
Asset deprecation |
|
Backup software |
|
Default tags |
|
Deprecated asset retention period |
|
EDR application |
|
Manage tags |
|
Patching status |
|
Ports policy settings: Exclude and include ports |
|
Suppress vulnerabilities |
|
Integrations | Status |
Alerts: Check credentials and company mappings |
|
Associated company and agent for firewall |
|
Azure AD section: Verify credentials set, company mappings, sync option |
|
Company mappings |
|
Credentials replication for all integrations |
|
Email: Check credentials and company mappings |
|
Firewall: Check credentials and associated company; also, check credentials updated as firewallOS under the Agent credentials section |
|
ALL Integrations > Event Sets (Includes Alert, Email, PSA, RMM) | 🔴 Not Replicating |
Nucleus security: Check credentials & company mappings |
|
PSA: Check the Credentials section and credentials profile count, Integration profile, and Manage company mappings |
|
PII Scan Profile | Status |
PII scan profile Global |
|
PII scan profile replication: Map to the same agents as V3 |
|
External Scan Profiles & Configurations | Status |
Configuration Settings (Discovery Settings) replication |
|
External scan profile replication |
|
Service detection settings: Exclude from replication |
|
Attack Surface Mapper | Status |
Attack Surface Mapper Profile |
|
Assets | Status |
Check updated assets |
|
Probe: Initiate Full scan and verify agent; for DC machines, check Ad data |
|
Application Baseline Rules | Status |
Company- Appbaseline profile |
|
Global- Appbaseline profile |
|
Schedulers |
|
Deprecated Agents | 🔴 Not Migrating |
One Time Assessments | 🔴 Not Migrating |
Global Settings |
|
Agent Deprecation Days |
|
Asset Deprecation days |
|
Backup Software |
|
Custom Domain Name |
|
Default Tags |
|
Deprecated Asset Retention Period |
|
EDR Applications Excluded |
|
Excluded Ports |
|
Insecure Ports |
|
Manage Tags |
|
Patching Status |
|
Select Date Format |
|
Session Timeout |
|
Suppress Vulnerabilities Days for Microsoft Patches |
|
Timezone Settings |
|
White Label Settings |
|
Pass...
Post Replication Updates 
Here are some items to consider once the replication is completed.
Login to the V4 portal and verify company data and settings (report any issues to our Support Team)
Verify Agents, Companies, Discovery Settings, Schedulers, Mappings, Integrations, etc….
Reconfigure Authentication Providers (login methods) since they are not replicated.
Update any agent installation automation, maintenance, or scripting; the new URL for RMM or scripting installation should use the URL below.
https://configuration.myconnectsecure.com/api/v4/configuration/agentlink?ostype=windows
...
Ready to Offboard the V3 Portal?
Check out the KB here to decommission the V3 portal: https://cybercns.atlassian.net/wiki/x/HAAwgw
...
Need Support? 🤔
You can contact our support team by emailing support@connectsecure.com or visiting our Support Portal at cybercns.freshdesk.com
...