Release 3.0

October 16, 2024 

What's New?

New Application - Mitigation

With the introduction of a new application, Mitigation, you can now mitigate vulnerabilities on Windows and Linux assets using actions and scripts, creating mitigation jobs.

Mitigation module.

Prerequisites

  • Windows Cloud Agent version 6.0 or later
  • Linux Cloud Agent version 7.0 or later
  • Mitigation License 
  • Asset activation for Mitigation

Despite Patch Management being the core capability in vulnerability management, the Mitigation application plays a key role, as patching might not always be feasible considering the required downtime, or the patch might not be available in the case of zero-day vulnerabilities.

The security and IT teams can use Mitigation capability to enhance cybersecurity resilience by addressing critical vulnerabilities without deploying a patch. This enables organizations to significantly lower their vulnerability exposure and streamline their response to cyber threats. For more information, refer to the Online Help.

Eliminations tab.

Remediation Job Creation 

With this release, you can see a new Eliminations tab on the Patch Management application. Using configuration scripts, you can create the Windows remediation job from the Eliminations tab and remediate vulnerabilities found on Windows assets. The vulnerabilities identified on assets are remediated by deploying a job that includes missing patches and configuration scripts. 

Prerequisites: 

  • Windows Cloud Agent version 5.7.0 or later
  • Patch Management License 
  • Asset activation for Patch Management

Remediation job creation.

Rerun On-demand Jobs

With this release, you can rerun Windows, Linux, and Mac on-demand patch deployment jobs. This enables you to run the same deployment job instead of creating a new one every time.

You can't rerun the job when the current patch deployment job run is in progress. For more information, refer to the Online Help.

Rerun job.

You can view the number of times the job rerun is executed on the Job Progress page.

Job runs details.

Edit On-demand Jobs

With this release, you can edit on-demand jobs. Before this release, you could edit jobs only with Disabled status. However, except for the jobs with Disabled status, you can't edit the job schedule. For more information, refer to the Online Help.

Example: Edit Windows On-demand Job with Assets Responded Status.

Edit on demand job.

API Enhancement

With this release, a new version of the "Get a List of Generated Reports" API, /pm/v2/reports, is introduced. For more information, refer to the PM 3.0.0.0 API Release Notes

New Token

Refer to the following table to learn more about the token added in this release.

Token  Tab Description

activatedModules

Assets

To find assets that are activated for Patch Management or Mitigation application. 

  • Supported values for Windows and Linux: PM and MTG
  • Supported values for Mac: PM

Issues Addressed

The following reported and notable customer issues have been fixed in this release.

Component/Category Description

PM - Job Windows

We fixed the issue where the asset status was shown as unknown.

PM - Public API, Reporting Service

/pm/v1/reports reports API failure was observed, and the latest report status was not shown. We have fixed this issue by introducing a new API version: /pm/v2/reports. For more information, see Patch Management 3.0.0.0 API Release Notes.

PM - Reports

We fixed the patch count discrepancy issue observed in the case of an asset when two different reports were generated. One report was generated for the respective asset and showed a certain number of patches. The second report was generated for multiple assets, including the earlier-mentioned asset.

PM - Job Windows

We fixed the issue where the job manifest was not sent to all assets.

PM - Job Windows

We fixed the issue where a patch scan was not performed for some assets.

PM-UI

We fixed the issue where no results were displayed when searching assets using the failedPatchTitle QQL search token on the Job progress page.

PM-UI

We fixed the issue where no results were displayed when searching jobs using the assetName QQL search token on the Job page.