Product release information for VIPRE Cloud Agent for Windows 13.2.8636, released on 2024 August 7, revised on 2024 August 9.

What's New

We have released a new custom build of the VIPRE Cloud Agent with the following updates:

Device Control

The VIPRE Cloud Agent for Windows now supports Device Control, including Mobile Device support.

EDR/ESC - Device Control

Device Control for Windows endpoints allows for the administration of external devices interacting with agents. This option is useful for limiting how users may transmit sensitive information to third-party devices, as well as protecting the endpoint from potential third-party threats.

Important

Device Control requires VIPRE Cloud Agent version 13.2 or higher.

• Review the latest release notes to find the most recent version of the VIPRE Cloud Agent for Windows
• Download and install latest VIPRE Cloud Agent for Windows

 

 

Introducing Device Control

Endpoint Security - Device Control Comparison

The table below compares Device Control between VIPRE Endpoint Security Server and VIPRE Cloud Endpoint products.

Device Control	EDR, EDR+MDR, and Endpoint Security Cloud
CD/DVD Drives	✅
Removable Drives (e.g., USB drives)	✅
Mobile Devices	✅
Floppy Drives	❌

Important

Device Control is a powerful feature that requires low-level access to device drivers. Because of this integration, Device Control can be incompatible with certain device drivers, particularly older versions. We recommend testing Device Control carefully on target systems before production deployment.

 

Configure Device Control

Use the steps below to configure different aspects of Device Control.

Enable Device Control

1. From within the VIPRE Cloud console, on the left-side blue menu, under MANAGE, select Policies
2. Choose your desired Windows policy
3. Under the Agent tab, scroll down and click the checkbox to enable Device Control
4. Select Save at the top

Device Control is now enabled in your policy. Remember that policy changes can take up to two minutes to update on your agent endpoints.

Device Control Exclusions

Create a new custom exclusion list or select an existing custom exclusion list.

1. Click +Add Exclusion at the top-right corner of the screen
2. Select Device
3. Choose to exclude device by Type or Specific Type
   • If you've chosen Type:
     • Select the desired category (CD/DVD or Removable drives)
     • Select the desired Bus (Any, ATA IDE, Firewire, SCSI, USB, PCMCIA)
   • If you've chosen Specific Type:
     • Select the desired category (CD/DVD or Removable drives)
     • Add value to Hardware ID (see example in text box)
     • Add value to Serial ID (see example in text box)

Hardware ID and Serial ID details can be copied from the Device Control Report and pasted here to add an exclusion for a specific device. This is helpful, for example, when you've set a broad Device Control policy to block all removable drives but still require at least one particular endpoint to access a specific USB flash drive.

 

4. Click Add

You can also add exclusions from the Device Control report. Continue reading below to learn more.

Device Control Reports

A real-time and historical view of device-related events, including the date and time of the event, the type of drive, the bus type that the drive was plugged into, the device that was plugged in, the policy it was accessed with, and whether it was denied/blocked, etc. 

To pull a Device Control report:

1. From within the VIPRE Cloud console, under MONITOR, select Reports
2. Clicking the Device link allows you to drill down further to see all Device Control events for a specific device.

To add exclusions from the Device Control Report, select a specific event and click Add to Exclusion. 

This will bring up the option to add the exclusion to an existing Exclusion Group or to create a new list. Once you select your desired exclusion list, you'll notice that Category, Hardware ID, and Serial ID are automatically filled in based on the device in the event you selected in the Device Control Report.

Review the auto-filled information and click Add when ready. 

Other updates include:

• We have made a number of improvements to the VIPRE Cloud Agent to harden its operation, ensure that unexpected network events don’t cause the agent to fail to load
• VIPRE Cloud Agent is now digitally signed using a VIPRE Security certificate so that end users are no longer being prompted for missing signatures
• Remote Shell now supports copy-and-paste using CTRL+Shift+C to Copy and CTRL+
  Shift+V to Paste
  • CTRL+C and CTRL+V are not supported within the VIPRE Remote Shell
• Various additional performance improvements

System Requirements

Fixed in this Release

• VPBAGENT-42197: Firewall/Web/DNS functionality was not working after a fresh Agent install
• VPBAGENT-42206: Threats were being quarantined even if chosen action was Remove
• VPBAGENT-42119: VIPREShell package wasn’t downloading after Agent install
• VPBAGENT-41721: When VIPRE install attempt was made with an incompatible software detected, it wasn’t actually installed after machine reboot
• VPBAGENT-41620: A combination of Domain Exclusions was causing Malicious URL Blocking for HTTPS to produce two VIPRE URL Inspectors per lookup but was not automatically closing them.
• VPBAGENT-41499: Some VIPRE Cloud Agents were not updating software versions after being approved
• VPBAGENT-40389: VIPRE Cloud Agent was causing SBAMSvc.exe to crash repeatedly
• VPBAGENT-41863: VIPRE Cloud Agent was causing sbwfw.sys to crash, resulting in a BSOD error - this was an issue when the network protection features were active and a malformed IPv6 packet was received
• VPBAGENT-42069: Post-install reboot loop occurring with definitions update failure with “SDK requires reboot” error
• VPBAGENT-41923: Firewall might show in Error status on Server 2016

Known Issues and Workarounds

This section lists issues that are known at the time of release. In some cases, these are bugs that we are working to resolve with a subsequent release. Other items may be due to causes outside our control, such as bugs with other vendors' software. In all cases, we have tried to provide a workaround for you to consider should you experience an issue.

If you have questions about a specific issue, please provide the ticket number below (if applicable) when contacting our Technical Support team.

Current Version