Patch Management in CloudCare
Add an essential part of a powerful endpoint security strategy to your CloudCare platform – easy software patching.
Patch Management is an integral layer of security to keep your customers’ applications safe
Stay ahead of the latest threats
Maintain compliance
Centralize and simplify management
What exactly is
Patch Management?
Patches are released to fix vulnerabilities or security gaps in Windows operating systems and other application software. If patches are not applied in a timely manner, networks can be severely compromised.
While most businesses are aware of the importance of patching, many don’t do it because there are too many patches, patching often interrupts operations, and and it can conflict with certain systems.
Patch Management solves these issues by making it easy to identify and deploy critical patches, and monitor ongoing activity from a central cloud management dashboard.
How does patching work?
Scan all devices for missing patches
Deploy patches
Review patch status
Features
Flexible deployment schedules
Master agent capabilities
Intuitive dashboard
Patch scan results
Customizable patches
Automatic scans
Thousands of patches
Roll back and ignore
Get Patch in the CloudCare platform
Patch Management and any of the Avast Business antivirus products are deployed through the CloudCare layered security platform. Easily manage and monitor your clients’ endpoint and network security from a single, cloud-based platform for seamless protection across all devices.
Everything you need to know to use your Patch Management like a pro
Yes, it is highly recommended that you change Windows Update settings for your devices via the Windows Update Center and/or Group Policy so Patch Management can provide updates.
The Windows Update service must not be disabled; rather, it should be set to either Manual or Automatic to successfully deploy patches. In addition, the Windows Update setting on each target machine (Control Panel > System and Security > Windows Update > Change settings) should be set to Never check for updates.
Deployment of patches will run under the remote machine's Local System account so make sure this is allowed.
You can set up your patch schedule in Policies > Patch Management > Patch Deployment. All devices under the Patch Management policy will follow the schedule you set.
Patches page provides detailed information on the severity of missing, approved, failed, ignored, and installed patches with vendors, and software applications.
You will be able to see how many devices are licensed for patch under the ‘Devices’ section in a customer account.
1. The patch is currently being installed on those devices and will sync back with the console after the patch has been successfully installed.
2. The patch could have failed to install and will be scheduled for a reinstall based on your patch deployment schedule.
3. The device is offline.
You can modify the patch auto-approval rules for vendors, applications, and severity by going to Policies > Patch Management > Auto-Approval rules tab.
Yes, you can manually deploy patches to individual devices and groups of devices in one step by selecting patches under Patches, then Approve for Deployment.
Missing: Patch is missing from device(s)
Approved: Patch is approved to be deployed to device(s)
Deployed: Patch successfully deployed to device(s)
Failed: Failed to deploy patch/es to device(s)
Ignored: Patch has been ignored and will not be deployed
It could take anywhere from a few seconds to several hours. The time depends on the size of the patch that is being downloaded to the device, the software application it is updating, and the hardware of the device.
Yes, the device you have selected as the Update Agent will be used to store the software application patches and will distribute them to devices on the network to save bandwidth. If you do not have an Update Agent selected, devices will download the software application patch directly from the internet (not recommended).
