Manage vulnerability remediation
In short: find your case in the remediation matrix, check the deployment prerequisites, then deploy from the details page of a vulnerability or of an asset. For the technologies that Cyberwatch does not deploy, Cyberwatch indicates what to fix and checks the fix at the next scan.
This guide helps you determine, for each technology in your fleet, how to fix the vulnerabilities detected by Cyberwatch, and to do it on your own. It complements the page Deploy a security fix, which describes the steps in the interface.
The four ways to handle a vulnerability
| Mode | Principle | When to use it |
|---|---|---|
| Deployment by Cyberwatch | Cyberwatch installs the patch on the asset, immediately or within a maintenance window, then checks the fix | Natively supported technology and asset connected with the required privileges |
| Guided manual fix | Cyberwatch indicates the corrective action (package, KB, target version, update command); the fix is carried out outside Cyberwatch | Technology that Cyberwatch cannot deploy, or choice to keep control |
| Fix by a third-party tool | Your patch management tool deploys; Cyberwatch prioritizes upstream and checks downstream | Fleet already managed by a deployment tool |
| Risk acceptance | The vulnerability is ignored, with a comment and a reactivation date | Fix impossible or not relevant, risk covered otherwise |
In all cases, Cyberwatch checks the fix: after each scan, the fixed vulnerabilities disappear from the asset, whatever the means used to fix them.
Remediation matrix by technology
Systems and software
| Technology | Deployment by Cyberwatch | Conditions | Otherwise |
|---|---|---|---|
| Debian, Ubuntu (APT) | Yes | Packages installed by the distribution’s package manager | — |
| Red Hat and derivatives: RHEL, CentOS, AlmaLinux, Rocky Linux… (YUM / DNF, including DNF modules) | Yes | Packages installed by the distribution’s package manager | — |
| SUSE (Zypper) | Yes | Packages installed by the distribution’s package manager | — |
| Snap packages | Yes | On APT, YUM/DNF and Zypper distributions | — |
| Running Linux kernel older than the installed kernel | Reboot | The patch is already installed: only a reboot activates it | Reboot the asset |
| Windows and Microsoft products (KB) | Yes | Windows Update or WSUS configuration, see Windows | Manual fix, or through your deployment tool |
| Third-party Windows software | Yes, through Windows Package Manager (WinGet) | Option enabled, WinGet present on the asset, software covered by Cyberwatch and by WinGet | Manual update or uninstallation from Cyberwatch |
| macOS | No (reboot only) | — | Update by the user or by your endpoint management tool |
| Alpine Linux, Arch Linux | No | — | Manual fix |
| AIX (interim fixes) | No | — | Manual fix |
| SAP (SAP Notes) | No | — | Manual fix |
| Software installed outside the package manager (compiled binaries, in-house applications) | No | — | Manual fix |
| Application libraries (npm, pip, gem, Composer, Maven…) | No | — | Update of the dependency in the application project, then redeployment of the application |
Monitoring modes
Deployment requires Cyberwatch to be able to run commands with privileges on the asset.
| Monitoring mode | Deployment possible | Prerequisites |
|---|---|---|
| Cyberwatch agent | Yes | — |
| Linux agentless connection (SSH) | Yes | Sudoers rights for the connection account, see prerequisites |
| Windows agentless connection (WinRM) | Yes | Account member of the local Administrators group, see prerequisites |
| AWS SSM and Microsoft Azure agentless connections | Yes | See AWS SSM and Microsoft Azure |
| Google Cloud IAP agentless connection | Yes | As with SSH, sudoers rights for the connection account, see Google Cloud IAP |
| Palo Alto Cortex XDR agents | Yes, without deploying or rebooting policy (immediate deployment or at the chosen time) | Script execution permissions of the API role, see Cortex XDR |
| Air gap | No | No traffic between Cyberwatch and the asset: manual fix |
| Read-only connectors (Microsoft Intune, Microsoft Defender, Meraki…) | No | Fix through the source tool |
| Network and industrial devices (SNMP, vendor API), hypervisors | No | Firmware update according to the vendor’s procedure |
| Docker images | No | Rebuild of the image from an up-to-date base image and dependencies |
An asset connected without the required privileges is monitored in “scan only” mode: its vulnerabilities are detected, but the deployment buttons are not offered for it. The mode is re-evaluated at each connection test.
Prepare the deployment
Enable the deployment module
Patch deployment is disabled by default.
- Click on Administration
- Expand the Patch management section
- Enable the Patches deployment option, and the reboot of assets if needed
- For third-party Windows software, enable the Deployment through Windows Package Manager option
Grant rights to users
Only users with the System administrator (or Administrator) role can deploy patches, uninstall software and reboot assets, on the assets of their projects. See Permissions.
Define the maintenance windows
The deployment and reboot policies set the days and times when Cyberwatch can install patches and reboot an asset.
- Manual scheduling: the policy is used to suggest the deployment date when a user schedules patches. Recommended for production.
- Automatic scheduling: Cyberwatch deploys on its own all the deployable patches of the asset each time the window opens. Suited to workstations and non-production environments.
Create at least one policy per environment (production, pre-production, workstations) and assign it to the assets through a Bulk edit from the inventory.
Windows
Cyberwatch installs KBs through the Windows Update service of the asset. It retains the KBs of the Security Updates, Critical Updates, Update Rollups and Updates classifications. The asset therefore downloads the KBs from its usual source, WSUS or Windows Update.
| Situation | Action |
|---|---|
| Assets attached to a WSUS | Approve the above classifications in the WSUS: an unapproved KB cannot be installed. See Windows assets attached to a WSUS |
| Office, .NET, SQL Server… KBs “To be processed manually” on an asset without WSUS | Allow Windows Update to update other Microsoft products, preferably through GPO, see Manually apply a corrective action |
| Third-party software | Install WinGet on the assets (Microsoft documentation) and check that the software appears in the list of covered software and in the WinGet repository |
| Third-party software missing from WinGet | Update it manually, or uninstall it from the Technologies tab of the asset (applications installed through MSI) |
A proposed KB can be a cumulative update: it then fixes several vulnerabilities, including older ones.
Windows assets attached to a WSUS
Who does what
Cyberwatch does not connect to the WSUS: it acts on the asset, through its Windows Update service.
| WSUS | Cyberwatch | |
|---|---|---|
| Identify missing patches | From the updates synchronized and approved on the WSUS | From the Microsoft security bulletins and the build number of the asset, independently of the WSUS |
| Make KBs available | Yes, once approved | No |
| Trigger the installation | According to the Windows Update configuration of the asset (GPO, deadlines) | According to the Cyberwatch deploying policies, or on demand |
Two consequences:
- Cyberwatch can only install the KBs that the WSUS has approved for the asset. It nevertheless offers all the missing KBs for deployment: deploying an unapproved KB fails, as no update is found. If the search on the WSUS fails or returns no update, Cyberwatch queries Windows Update directly, which requires the asset to have access to the Internet;
- a workstation shown as up to date in the WSUS can remain vulnerable in Cyberwatch, for example if a KB is not synchronized or if a reboot is pending (see Explain a discrepancy).
Microsoft has announced the deprecation of WSUS. As the Cyberwatch deployment goes through Windows Update on the asset, it works with or without WSUS: without WSUS, the asset downloads the KBs directly from Windows Update.
Configure the WSUS
- Synchronize the products installed on the fleet: Windows system, but also Office, SQL Server, .NET, Exchange… A KB of a product that is not synchronized is never offered to the asset.
- Automatically approve the classifications used by Cyberwatch (Security Updates, Critical Updates, Update Rollups, Updates) for the relevant computer groups, using an automatic approval rule (Microsoft documentation).
- Also approve the prerequisites, in particular the Servicing Stack Updates: a KB whose prerequisite is missing from the asset does not install. The Microsoft support page of each KB lists its prerequisites.
Choose who triggers the installation
Decide, for each group of assets, which tool triggers the installation, in order to avoid concurrent installations and unexpected reboots.
| Cyberwatch triggers | The WSUS triggers | |
|---|---|---|
| Principle | The WSUS approves and distributes; Cyberwatch installs within its maintenance windows | The assets install the approved KBs on their own, according to the GPO and the WSUS deadlines |
| Windows Update configuration (GPO) | Automatic download without automatic installation, for example “Auto download and notify for install” | Scheduled automatic installation, or installation deadlines on the WSUS |
| Cyberwatch configuration | Deploying policy in automatic or manual scheduling, and rebooting policy | Deploying policy in manual scheduling only |
| Role of Cyberwatch | Prioritization, deployment, verification | Prioritization, verification, and occasional deployment to catch up on a critical KB on the failed assets |
| Suited to | Servers requiring maintenance windows per asset | Workstations and fleets already managed at scale through the WSUS |
Explain a discrepancy between the WSUS and Cyberwatch
| Finding | Probable cause | Action |
|---|---|---|
| KB installed according to the WSUS, still reported by Cyberwatch | Pending reboot: the build number of the asset only changes after a reboot | Reboot the asset then relaunch its analysis. Cyberwatch displays the Reboot required status, and can reboot the asset, only if Windows Update is waiting for a reboot (key HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired). If only the key HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending exists, reboot the asset according to your procedures |
| Recent fix not visible in Cyberwatch | The asset has not been analyzed since the installation | Check the date of the last analysis and relaunch the analysis from the Analyses tab |
| KB reported by Cyberwatch, missing from the WSUS | Product or classification not synchronized, or KB that Microsoft distributes only through Windows Update (missing from the catalog) | Complete the synchronization of the WSUS; see the “How to get this update” section of the Microsoft page of the KB |
| KB reported by Cyberwatch, not applicable according to the WSUS | Missing prerequisite on the asset | Install the prerequisite indicated on the Microsoft page of the KB |
Troubleshoot a failed KB deployment
- Read the deployment result in the script history of the Patch management tab of the asset: it contains the Windows Update error code (
0x8024…) or indicates that no update was found. - Check the most frequent causes:
- the KB is approved for the computer group of the asset on the WSUS;
- its prerequisites are installed or approved;
- the KB is not already installed (Technologies tab of the asset), in which case a reboot is probably pending;
- the Windows Update service (
wuauserv) is enabled and the Windows Update agent is up to date, see Windows prerequisites.
- Install the KB manually through Windows Update on the asset. If the manual installation also fails, the problem lies with Windows Update: search for the error code in the Microsoft documentation. If it succeeds, contact Cyberwatch support.
Linux
Patches are installed by the package manager of the distribution, including dependencies. The asset must therefore access its repositories (internal mirror, proxy or Internet) and these repositories must offer the fixed version.
Deploy the patches
Choose the entry point according to the chosen approach:
| Approach | Entry point | Use |
|---|---|---|
| By vulnerability | Vulnerability details page, Remediation block | Handle a critical CVE across the whole fleet, or by system family |
| By corrective action | Corrective actions page | Handle first the updates that fix the most high-priority vulnerabilities |
| By asset | Asset details page, Patch management tab | Precisely choose the patches of a sensitive server |
| By batch of assets | Inventory, Bulk actions | Fully update assets, now or at the next maintenance window |
For each deployment, two options:
- Schedule: the deployment takes place in the next window of the deploying policy of the asset, or at the chosen time;
- Deploy now: after confirming the number of assets concerned.
The detailed steps are described in Deploy a security fix.
Test first on a sample of representative assets (pre-production, a few workstations) before deploying to production, especially for full system updates.
Track and verify
| Step | What Cyberwatch shows |
|---|---|
| Scheduled deployment | The asset has the Planned patches status and the vulnerabilities concerned have the Fix scheduled status |
| Execution | The result can be viewed in the script history of the Patch management tab of the asset, or for the whole fleet on the Patch history page, accessible through the History button of the Corrective actions page |
| Verification | Cyberwatch relaunches the analysis of the asset: the fixed vulnerabilities disappear, the others remain to be processed |
| Reboot | If the system requests a reboot, the asset switches to the Reboot required status: reboot the asset from Cyberwatch or according to your procedures |
See also Assets status.
Fix without Cyberwatch deployment
Guided manual fix
Corrective actions with the To be processed manually status cannot be deployed by Cyberwatch. Cyberwatch nevertheless provides the elements needed for the fix:
- the technology to update and the target version, on the page of the corrective action;
- for Linux packages, the update command to copy, in the Remediation block of the vulnerability details page (for example
apt-get install --only-upgrade <packages>); - the CSV export of the assets of a vulnerability, whose Corrective action status column distinguishes deployable patches from patches to be processed manually.
Once the fix is applied, relaunch the analysis of the asset from its Analyses tab to confirm the fix without waiting for the next scan.
With a third-party deployment tool (WSUS, SCCM / MECM, Intune, Ivanti…)
Cyberwatch does not drive third-party deployment tools. If your fleet is already managed by one of them, the recommended approach is as follows:
- Prioritize in Cyberwatch: the prioritization policies identify the patches to process first.
- Send the list to the deployment team or tool:
- CSV export of the corrective actions or vulnerabilities;
- ITSM ticket created from Cyberwatch, manually or through an alert: ServiceNow, GLPI, or any other target through the integrations;
- Cyberwatch API for custom automation.
- Deploy with your tool, in your usual maintenance windows.
- Check in Cyberwatch: at the next scan, the fixed vulnerabilities disappear; those that remain indicate a patch that is not approved or that failed in the third-party tool.
To prevent two tools from deploying on the same assets, do not enable the Cyberwatch automatic deployment on the assets managed by another tool.
Accept the risk
When a vulnerability cannot or must not be fixed (obsolete system maintained for business reasons, compensating control in place), ignore it with a justifying comment and an automatic reactivation date (30, 60, 90 days or custom date) to review it regularly. The ignoring policies apply this handling at scale.
When to contact support
This guide covers the natively supported cases. Contact Cyberwatch support in the following situations:
- a deployment fails even though the technology is supported and the prerequisites of this guide are met;
- a vulnerability remains present after a fix has been applied and a new analysis has been run;
- your technology or your monitoring mode does not appear in the matrix;
- you want a native integration with a third-party deployment tool: support forwards the feature request.
Attach to the request: the name of the asset, its operating system, its monitoring mode, the vulnerability or corrective action concerned, and the export of the asset obtained from its Analyses tab with the Export asset information button.