Release Notes 3.0.0 GA

Article summary

Did you find this summary helpful?

Thank you for your feedback

Release Date

12-April-2024

Exception addition in case of Web Protection incidents can be now performed at a granular level defining custom conditions. Click here for more information

Users can now define Global Allowlists using APIs where executables can be allowlisted across profiles. Click here for more information
Host Protection now utilizes kernel cache to store executables and optimize the Host Detection and Protection response time. Click here to configure the associated parameters

CMS as SaaS Instance - CMS is now provided as a SaaS instance. This removes the requirements of an On-prem infrastructure for it
1. Installation, upgrade and migration processes are taken care by the Virsec team
2. If CMS is migrated from 2.x On-Prem to 3.x SaaS instance, Probe instances also need an upgrade to 3.x. They can be deployed in two configurations:
  1. Without Proxy Server
  2. With Proxy Server
3. SaaS CMS instance now supports 1500 associated Probe instances
  NOTE
  VSP SaaS CMS 3.x is compatible with VSP Probe 3.x
CMS can be installed with On-prem configuration (Internet access is required during installation). Click here for more information
Information about all the available APIs are now provided in CMS. They can also be accessed from CMS itself. Click here for more information
The incidents page is modified to make the available fields more easily readable by the user

Single MSI now supports all Operating systems from Windows 2008 - Windows 2022. A single MSI supports both 32-bit and 64-bit configuration on Windows 2003. Click here for more information regarding MSI-based installation
CPM (Centralized Probe Management) API provides an option to manage Probe (Installation, Upgrade, View logs, execute VSP-CLI commands, Service - start/stop probe instances) through API. Migrate API is also included to aid CMS migration from On-prem to SaaS instance. For Click here for more information

Defect ID	Description
SUPP-1088	Tomcat application does not move to Normal state after VSP-Web instrumentation
SUPP-1097	Webhook configuration on CMS does not accept nested JSON
SUPP-1100	File Inclusion Profile displays incorrect column header
SUPP-1104	"Old File Path" variable required for File Rename custom action is not listed in the catalogue
SUPP-1105	Windows probe wrapper script corrupts hosts file when trailing newline is not present

Was this article helpful?

Table of contents