July 19, 2020 Service Pack
The following Service Pack versions were released:
Versions (Sensor and Server) |
---|
19.1.221 19.2.120 |
The tables below describe the enhancements, fixed issues, and changes included in each version.
The Versions column indicates the versions that include the fix.
The Required Update column indicates if the fix requires sensor/server update.
IMPORTANT: If you want to upgrade your servers to this version, we recommend that you upgrade all components - Registration server, Detection servers, and WebApp server - to this version.
Enhancements
Issue |
Area |
Description |
Versions |
Required Update |
Sensor OS |
---|---|---|---|---|---|
CYBR-30403 |
Configuration |
To enhance customization, it is now possible to enable different proxy settings (for all sensors) for communication between the sensor and the Detection server. This can be enabled by the Technical Support team via sensor personalization. |
19.1.221, 19.2.120 |
Sensor |
Mac |
CYBR-32335 |
Endpoint Detection |
We have updated the term ‘blacklist’ and ‘whitelist’ to ‘blocklist’ and ‘allowlist’ respectively. |
19.1.221, 19.2.120 |
Server |
N/A |
CYBR-32436 |
Endpoint Detection |
To reduce sensor network usage we have improved the efficiency of sensor traffic. |
19.1.221, 19.2.120 |
Sensor |
All |
CYBR-30188 |
Server Management |
The ‘Alerts’, ‘Performance’ and ‘Current version’ sections of the System > Overview screen, and the ‘Status’ and ‘Alerts’ columns in the System > Detection Servers screen are hidden by default. For more information, see Cybereason's Monitoring Solution FAQ. |
19.1.221, 19.2.120 |
Server |
N/A |
Fixed issues
Issue |
Area |
Description |
Versions |
Required Update |
Sensor OS |
---|---|---|---|---|---|
CYBR-32680 |
Data Platform & Hunt |
If the Malop details screen timed-out, we have added an error message explaining that the page should be refreshed. |
19.1.221, 19.2.120 |
Server |
N/A |
CYBR-32332 |
Detection |
If a File search request using the fileSearch API contained the size parameter, a 500 error would be returned. This issue has been resolved. |
19.1.221, 19.2.120 |
Server |
N/A |
CYBR-32076 |
Sensor Management |
Linux sensors upgraded after the February 23rd Service Pack had an invalid unique identifier (PylumID). This issue has been resolved. |
19.1.221, 19.2.120 |
Sensor |
Linux |
CYBR-32220 |
Sensor Management |
In cases where Windows could not fetch the intermediate ‘GeoTrust RSA CA 2018’ certificate, sensors would not trust Cybereason server certificates. This caused sensors to fail to connect to the server. This issue has been resolved, sensors now trust Cybereason server certificates and successfully connect to the Detection server. |
19.1.221, 19.2.120 |
Sensor |
Windows |
CYBR-26090 |
Sensor Management |
If PowerShell malware was excluded from the Malware alerts screen it would not be excluded for sensors on versions 19.1 and above. This issue has been resolved and the exclusion applies to all existing policies. |
19.1.221, 19.2.120 |
Server |
N/A |
CYBR-32293 |
Sensor Management |
We have improved the performance of the Linux sensor to ensure recovery after a crash due to a corrupted policy configuration. |
19.1.184, 19.1.221, 19.2.120 |
Sensor |
Linux |
CYBR-31221 |
Sensor Management |
While upgrading a Linux sensor, on the System > Sensors screen, the ‘Last update status’ column listed the upgrade as ‘In progress’ even after the upgrade had been successful. This issue has been resolved. |
19.1.221, 19.2.120 |
Sensor |
Linux |
CYBR-31556 |
Sensor Management |
When upgrading from versions 18.1 and below, if sensors had been archived and the auto-archive option was disabled, the archived sensors did not appear in the new version. This issue has been resolved. |
19.1.221, 19.2.120 |
Server |
N/A |
CYBR-31881 |
Sensor Management |
On the System > Sensor screen, if a query for Online sensors with an Internal IP was run multiple times, the results would return empty. This issue has been resolved. |
19.1.221, 19.2.120 |
Server |
All |