Product release information for VIPRE Cloud Agent for macOS version 12.0.48 early access, released on 2025 December 10.

What's New

We are excited to announce a major upgrade for our business and enterprise clients: the VIPRE Cloud Agent for macOS now supports robust Endpoint Detection & Response (EDR) functionality! This is more than just an update; it's a transformation of your macOS endpoint protection, delivering the deep visibility and proactive defense capabilities demanded by today's sophisticated threat landscape.

With this release, your Mac environments gain powerful, enterprise-grade security features. At the core is Behavioral Threat Detection, providing real-time, continuous monitoring to flag and block suspicious activities. Should an incident occur, our comprehensive Threat Quarantine & Response ensures containment, allowing for automatic or manual remediation with actionable steps. Your security teams will now have access to industry-leading Incident Response and Forensic Tools, enabling enhanced investigation, deep activity tracking, and crucial insight into attack vectors to understand and neutralize threats at their source.

To empower you with precise control, we've included Automated Threat Detection Rules, allowing you to deploy pre-configured best practices to match your operational and security needs. All this intelligence is centralized in your dashboard, providing Continuous Monitoring and Reporting for a clear, 360-degree view of system health and all attempted or remediated attacks.

This enhanced agent reinforces our commitment to Cross-Platform Compatibility, ensuring consistent, reliable protection across both your macOS and Windows devices from a centralized web console. Best of all, this advanced security is delivered via a Lightweight Agent, meticulously optimized for macOS to provide unparalleled protection without compromising system performance.

Updated System Requirements

The new, feature-rich agent requires a more modern base, leading to an update in the minimum supported operating systems and a slightly increased resource requirement. 

Key differences include:

You can view the full system requirements here by navigating to the VIPRE Cloud Agent for macOS System Requirements article.

Special Instructions

With VIPRE-provided custom build codes, you can access VIPRE Cloud Agent releases that are not generally available. We may make these builds available for early access to builds planned for GA release. 

Part 1 - Retrieve Custom Build

This process assumes you are logged into your subscribed VIPRE Cloud product's web console with administrator credentials. To retrieve the custom build:

1. On the left-side blue menu, under SETUP, select Deploy Agents
2. On the right side of the window, under Retrieve Custom Build, click the button that says Enter Build Code
3. Enter the build code that was provided to you and select Retrieve

Once the custom build agent is retrieved, it will appear under the current version.

4. Select Create Policy Installer
5. Choose the desired security policy (either the default policy or a customized policy you have created)
6. Click Select to generate and download the policy-specific agent installer file

7. Securely transfer the downloaded installer file (with the unmodified name) to your target macOS endpoints

Part 2 - Install VIPRE Cloud Agent for macOS

The installation requires two files. The first file, downloaded from the VIPRE Cloud web console, is a micro installer that retrieves the appropriate agent installer. The second file is the application installer, which executes the actual installation of the VIPRE Cloud agent on your endpoint.

8. Double-click the file to begin the installation process and follow the on-screen prompts
9. On the Installation Type screen, click Install
10. When prompted, enter your local macOS administrator credentials during this process
11. When the installer download is complete, click Close to automatically launch the application installer
12. In the new installer window, click Continue on the Intro and License screens
13. Review the license agreement presented on the second License screen, then click Agree
14. On the Installation Type screen, click Install
15. When prompted, enter your local Mac administrator password and click Install Software
16. When the Installer Modify Apps prompt appears, click Allow
17. When the SecurityNetworkInstallerApp pop-up appears, click Open System Settings
18. In System Settings, configure the security component based on your macOS version:

macOS Version	Steps to Enable
11 (Big Sur) to 14 (Sonoma)	Go to Privacy & Security Under the Security section, click Allow next to the message: "System software from application 'SecurityNetworkInstallerApp' was blocked from loading" Enter local Mac admin password, then click Unlock
15 (Sequoia) and higher	Go to Network Extensions Locate SecurityNetworkInstallerApp and click the toggle button to enable it Enter local Mac admin password, then click OK Click Done

19. When the prompt “BDL Daemon” Would Like to Filter Network Content appears, click Allow
20. Once the installation is successful, click Close
21. At the top of your screen, if the agent asks for permission to show notifications, click Options and then select Allow

The VIPRE application will now begin initialization. To verify installation of the VIPRE Cloud Agent, click on the agent icon in the dock to open the VIPRE App. All lights should be GREEN.

Part 3 - Post Install System Configuration/Troubleshooting

Error	Resolution
Error Case 1: Full Disk Access not granted for BDLDaemon	If you see the prompt "Full Disk Access not granted for BDLDaemon,” click OK Open System Settings > Privacy & Security > Full Disk Access Ensure that BDLDaemon is enabled; if it's not, check the toggle next to it Enter local Mac admin password then click Unlock; Full Disk Access on BDLDaemon is now enabled
Error Case 2: Network extension not approved for SecurityNetworkInstallerApp	Follow the steps corresponding to your macOS version to enable the component: macOS 11 (Big Sur) to 14 (Sonoma): Open System Settings > Privacy & Security > Security section Click Allow next to the message: "System software from application 'SecurityNetworkInstallerApp' was blocked from loading" Enter your local Mac administrator password, then click Unlock macOS 15 (Sequoia) and higher: Open System Settings $\rightarrow$ General $\rightarrow$ Login Items & Extensions Under Extensions, click the ⓘ (info) button next to Network Extensions Locate SecurityNetworkInstallerApp and click the toggle button to enable it Enter your local Mac administrator password, then click OK All macOS Versions (11 and higher): Ensure that the prompt “BDL Daemon” Would Like to Filter Network Content is answered by clicking Allow

Part 4 - Enable EDR on your macOS Policy

Now that your macOS endpoints have the new VIPRE Cloud Agent for macOS installed, and are connected to your VIPRE Cloud account, you'll need to enable EDR functionality.

22. Under Devices, select Policies, then click Mac
23. Select your desired local policy from the Policy List
24. Select EDR from the light blue menu
25. Click in the checkbox next to Enable Extended Investigation; you can also select from the list of raw event types you want to be reported by the agent:
    • Create Process
    • Logon Process
    • Logout Process
    • Process Injection
    • Terminate Process
26. Click Save in the top right corner

To learn more about how to use EDR, navigate to our product documentation on the VIPRE Success Center.

Known Issues and Workarounds

This section highlights issues identified at the time of release. Some are bugs that we are actively addressing in future updates, while others may be related to third-party software. We've provided workarounds to help you manage these situations effectively wherever possible.

If you need more information on a specific issue, please share the ticket number (if applicable) when contacting our Technical Support team.

Issue: Duplicate Threat Detections in Cloud Reports

• What's Happening: A reporting anomaly is occurring where certain threats detected during a manual scan from the VIPRE Cloud console are being recorded twice in the agent's history and subsequently reported to the cloud. 
• What you might see/experience: VIPRE Cloud reports may show a single threat detected as two distinct entries when reviewing scan details, with one of the entries appearing with a blank or empty threat name following a remote scan execution.
• Workaround: No action is required, as the core security function is working correctly. You can safely disregard any threat entries with an empty name in your VCloud reports, as they are redundant duplicates of the correctly named entry.

Issue: Missing Login/Logout Events for VNC Connections

• What's Happening: The agent's EDR logging is currently not generating expected edr.login and edr.logout events when a user initiates and terminates a remote session via the vncviewer application. 
• What you might see/experience: Specific session start/end events are not being recorded.
• Workaround: While the specific EDR login/logout events are missing, the agent is still recording the vncviewer process creation events. System administrators can use these related process events as a proxy indicator for the start of a remote session.

Issue: Incorrect Tooltip Message for Definition Updates

• What's Happening: A minor display bug exists in the Agent console during the "Validating License" stage. If a user clicks the information icon (i) next to the "Auto-update threat definitions" option, the resulting tooltip displays an unexpectedly large and incorrect time duration (e.g., “Definitions outdated, last updated 487xxx hours ago.”)..
• What you might see/experience: You will see an alarming and technically inaccurate number of hours in the tooltip, suggesting the threat definitions are significantly outdated; however, this does not reflect the agent's actual definition status or the last successful update time.
• Workaround: Ignore the stated number of hours in this specific tooltip. The agent is likely updating correctly. After a few minutes, when the agent finishes the first definitions update, these errors will disappear.

Issue: Catch-up Quick Scan Not Triggering After System Resumes

• What's Happening: The scheduled scan catch-up mechanism is currently failing to initiate the required "catch-up scan" when the system returns to an active state, regardless of whether the scheduled time was missed due to the computer being shut down or in sleep mode.
• What you might see/experience: You may observe that a scheduled scan was skipped with no corresponding catch-up scan running shortly after the PC is powered on or wakes from sleep.
• Workaround: The agent may not run a scan until the next regularly scheduled scan time, which should run as normal. If you know a scheduled scan was missed while the system was unavailable, you can manually initiate a scan from the VIPRE Cloud console or directly on the macOS agent.