22.2 enhancements and patches

Review the Automation Console 22.2 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

VersionFixed issuesUpdates and enhancements
22.2.00Known and corrected issues22.2 enhancements

BMC applies upgrades as described in the BMC Helix Upgrade policy Open link . BMC applies upgrades and patches during  Maintenance windows. Open link .


Assign CVE IDs to patches by using the API

For operating systems such as CentOS and Ubuntu, automapping does not work because patch catalogs do not provide CVE IDs. With this release, you can now assign the CVE IDs to patches by using the API so that the vulnerabilities can be automapped to patches. For information about using this API, see Using REST APIs

Use the catalog schedule defined in TrueSight Server Automation

While creating a patch catalog in Automation Console, you can view and use a predefined schedule that is defined in TrueSight Server Automation. For more information, see Working with catalogs.

Additional details for vulnerabilities and remediation from the Risks page

From the Risk Distribution and SLA Distribution widgets on the Vulnerability dashboard, you can view additional details for the vulnerabilities or impacted assets. For more information, see Using the Vulnerability Dashboard.

Also, you can now remediate vulnerabilities from the Risks page. For more information, see Working with risks.

Exclude discovered assets from importing

If you do not want to import all the discovered assets by using the BMC Discovery connector, exclude them by providing a list of host names, IP addresses, IPv4 ranges, or any of these combinations. For more information, see Configuring the BMC Discovery connector.

Close vulnerabilities without creating operations

You can use tools other than Automation Console to remediate vulnerabilities. Such vulnerabilities when imported by the scanner show incorrect status of assets in Automation Console. You can now close such vulnerabilities directly without creating operations. For more information, see Working with risks.

or using TPS), such a vulnerabilities can be closed in TSAC without creating TSSA jobs.

Client certificate authentication for the Tenable.sc collector

You can now configure the Tenable.sc connector to use the client certificate to authenticate with the Tenable.sc server. For more information, see Configuring the Tenable.sc connector.

Remediate network jobs that are not excluded

If a vulnerability is identified on two or more network devices and an exception is present for one of the network devices, then Automation Console remediates only those network devices which are not included in the exception. For more information, see Working with exceptions.

Was this page helpful? Yes No Submitting... Thank you