Version 3.2, a major release, includes:
Before you can use the features and enhancements described below, you must update the relevant agent on your device. macOS/Windows agents 3.2 are generally available around a week later.
This section describes the new features that we are releasing with version 3.2.
The following features have been added to the Coro console:
Coro is now introducing roles for MSP admin users at the channel and descendant workspace levels. You can assign granular permissions to each role. This helps businesses better align with compliance needs, manage roles in alignment with their internal policies and requirements, and better ensure operational efficiency and business continuity.
You can access MSP admin users roles and permissions through Control Panel -> Manage Workspaces. Coro has three predefined roles, which can’t be edited or deleted:
- MSP Viewer: Can view content.
- MSP Administrator: Can view and edit content.
- MSP super admin: Can view and edit content. Additionally, MSP super admins can reassign roles to MSP admin users and admin users.
Additionally, custom roles can be created for MSP admin users, with permissions tailored to those users. Permissions are categorized into the following options:
- No Access: The MSP admin user cannot see or interact with the section.
- Can View: The MSP admin user can see the section but cannot make changes.
- Can Edit: The MSP admin user can view and make changes to the section.
All current MSP admin users will automatically be assigned the MSP super admin role. Any MSP admin users added after the release must be assigned a role, and will not receive one by default.
For more information, see Managing MSP roles and permissions.
An Export to CSV function has been added to the:
- Devices view’s Bulk Action
- Tickets view’s Bulk Action
- Activity Log page
- Protected users list
The following features have been added to the EDR module:
Process and telemetry information in files and folders can now be excluded from collection by the Coro Agent.
For more information, see EDR allowlist and blocklist.
EDR tickets now include a section displaying specific techniques and tactics from the MITRE ATT&CK framework associated with the security incident.
For more information, see EDR tickets.
Processes on the EDR Processes page now list all open EDR tickets associated with each listed process.
For more information, see EDR processes.
The following features have been added to the Network module:
This feature will be available soon.
The Coro Endpoint Protection app enables VPN protection on iOS and Android.
For more information, see Introducing the Network module.
DNS filtering is now available on both the Inclusive and Exclusive VPNs.
For more information, see Secure Web Gateway.
The following features have been added to the MDM module:
Coro MDM now supports enrollment and management of iOS devices configured and deployed through Apple Device Enrollment Programs (DEP). Specifically, Coro supports Apple Business Manager (ABM) and Apple School Manager (ASM) programs.
Coro MDM includes an improved and redesigned user interface.
The following features have been added to the Connectors section of the console:
Coro now supports Autotask PSA integration. Autotask is used to map services (Coro modules and add-ons) and accounts (managed workspaces) via a PSA connector in order to report workspace usage data.
For more information, see Integrating with Autotask PSA.
The following features have been added to the Email Security module:
Coro now identifies and quarantines emails containing metadata considered potentially malicious.
For more information, see Suspicious Metadata.
Version 3.2 introduces the following additional changes:
Support additional entries in the SWG allowlists and blocklists
EDR information added to reports and managed service notifications
Wildcards, IP ranges, and subnets can now be added to allowlists and blocklists of DNS filtering.
There is now a DNS filtering blocklist for adult content.
Activity logs are now available for actions taken in the Network module.
It is now possible to enable access restricted to individual users.
It is now possible to enable access restricted to named US states.
The activity logs for device posture have been updated to enhance user-friendliness and support updates in policy logging, such as device label removal.
The daily Coro email report now includes counts of opened and resolved EDR tickets.
Coro's phishing detection and response architecture has been improved to enable Coro to respond to new types of threats even faster than before.
This section describes the following additional agent updates that we are releasing with version 3.2:
The relevant agent must be updated on your device before changes take effect. The features described will not function until the updated macOS and Windows agents are installed. These are generally available around a week after the release.
macOS agent 3.2 includes the following:
The Coro Agent now supports silent updates, requiring no user interaction.
The Coro Agent now supports multi-user functionality on macOS devices, ensuring seamless UI and information collection across different user accounts, including during fast user switching.
Improvements have been made to the Agent update UI.
General bug fixes were made for this release.
Windows agent 3.2 includes the following:
The Coro Agent now supports integration with NinjaOne remote monitoring and management (RMM).
Coro is now registered as an authorized provider in the Windows Security Center (WSC) and is the primary antivirus (AV) software for the device. After Coro is registered as the primary AV software, WSC disables Windows Defender on the device.
General bug fixes were made for this release.