Release Notes 2.7.0
- 27 Oct 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Release Notes 2.7.0
- Updated on 27 Oct 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Release Date
7-April-2023
What's new in 2.7?
CMS Enhancements:
- CMS UI has improvements in the left pane for better grouping of features and ease of navigation
- CMS now enables easy deployment of Probes on VM with commands for download and installation. Refer to Install Probe in VM for more information
- Enhancements are incorporated in incident management for better processing
- New APIs are available to obtain incident related information
- The licenses maintain persistence during VM restarts on on-prem license servers. Refer to Persistence of Licenses for more information
- Incident Type information is provided in the VSP Reports
- Probes page now displays the Probe First Installed and Probe Last Installed fields. Refer to the Monitoring Handbook for more information
- During Application creation, Web Profile is now an optional field. The field “Application Type” is no longer applicable for Java
Platform Enhancements:
- New MSI-based installation option is available for Windows-based probe installation
- Signed scripts are available for Linux-based probe installation
- Password is required to uninstall or upgrade Probe on Windows and Linux
Web Enhancements:
- Application Discovery is a new component of the installed VSP probe. It scans the Probes after installation and at regular intervals (Default duration - weekly) to discover the web applications hosted on them. Once the web applications are discovered, appropriate Applications are created on CMS with the discovered information. Refer to Application Auto-Discovery in CMS Applications for more information
Executable Allowlist Enhancements:
- An active Maintenance Mode can be stopped at the host level. In earlier releases, “STOP” was applicable for all the hosts in the profile. Refer to the Maintenance Mode for more information
- Ability to automatically allow new publishers/packages discovered during runtime. This is a configurable option in the host profile and is enabled by default for newly created ones
- Files marked as SAFE by reversing labs also have the trust factor. VSP now trusts only the files having trust factor values 0, 1 and 2. Files with trust factor 3 and above are not considered as known by VSP for higher levels of efficacy.
- Incidents related to executable allowlisting and App Control Policies can now be cached locally on the probe when CMS is not reachable. Further, these incidents are sent when CMS is reachable
App Control Policy Enhancements:
- ACP related incidents are reported as a separate category “App Control Violation” with relevant information. Refer to the ACP Incidents for more information on the various event types
- ACP rules are now applied based on the hash values of the application in scope, even though only application name is defined in ACP rule. This allows VSP to stop application masquerading attack
- Ability to detect incidents based on the redirection parts of the command is added
Memory Exploit Protection Enhancements:
- MEP is now supported on a wide range of kernel versions for the supported Linux Operating systems. While Virsec automatically adds support for the newly available kernel versions on a regular basis, if any kernel version is unsupported, the user is notified through CMS. Refer to the Unsupported Kernel Versions under Memory Exploit Protection for more information about how you can identify unsupported kernel versions and update LFR to get support for the latest Linux Kernels
- MEP now provides protection against additional Linux based exploit - ptrace Sudo Token Privilege Escalation
- Regular Expressions based exclusions are now supported. Refer to the Memory Exploit Protection Exclusion for more information
Fixes
Defect ID | Description |
---|---|
SUPP-51 | Maintenance Mode does not auto-whitelist scripts executed during this window |
SUPP-58 | ADVERTISED_LISTENER is missing from vsp-kafka |
SUPP-308 | ACP does not block the command line in protect mode during certain attempts |
SUPP-393 | Critical Vulnerabilities found in images after CI Phase |
SUPP-427 | ACP does not alert/block some Command lines |
SUPP-446 | RBAC displays errors for certain tabs |
SUPP-465 | The field "Updated By" for all system alerts related to Maintenance mode displays the value "SYSTEM" |
SUPP-483 | Unable to upload the file Caprequest.bin on Flexnet using Activation ID |
SUPP-487 | RDP failed for windows servers when the profile (in detect mode) and MEP are enabled |
SUPP-508 | .NET Application does not move to normal status |
SUPP-557 | SIEM Qradar Syslog format issue causes incident |
SUPP-571 | Website login fails after VSP instrumentation for .NET application |
SUPP-572 | Remove hardcoded credentials and IP addresses in 2.5.0 LFR Helm chart |
SUPP-573 | K8s SA is not created when the Helm value - serviceAccount.create is set to true |
SUPP-576 | Unknown error encountered while managing 2.5.0 Allowlists |
SUPP-577 | Wiki (tomcat) application does not work in protect mode |
SUPP-584 | Expired digital certificate process is reported as a threat in the allowlist but process execution behavior is different in the Protect Mode |
SUPP-611 | Windows Strict ACP does not cover regedit.exe |
SUPP-622 | RBAC issue is detected in host incident management on CMS |
SUPP-636 | Linux Probe script directory has unmaintained files |
SUPP-646 | CD tool modifies the container name in addition to the image name |
SUPP-651 | On Windows 2003, the file vm-install.bat has a function mislabeled |
SUPP-672 | Some .NET Applications hang due to the loading order of the libraries when MEP is injected |
V2-22513 | MS Exchange Server does not report incidents for attacks against the OWA application |
V2-22298 | LDAP User Group base DN displays validation error |
Was this article helpful?