Learn what’s new or changed for TrueSight Automation Console, including new features, urgent issues, documentation updates, and fixes or patches.
New authentication systems
With this release, TrueSight Automation Console supports the following new authentication systems.
Support for PKI authentication
If your TrueSight Server Automation is configured to use with public key infrastructure (PKI), then you can use it as an authentication type to log on to TrueSight Automation Console. For more information about enabling PKI, see in TrueSight Server Automation documentation.
For using PKI authentication, your TrueSight Server Automation version must be 21.02.
For more information about using PKI while logging on to TrueSight Automation Console, see Accessing and navigating the interface for using with TrueSight Server Automation.
Support for BMC Remedy Single Sign-On
TrueSight Automation Console now supports BMC Remedy Single Sign-On (RSSO) as an authentication system. In this release, the product supports Local, Lightweight Active Directory Protocol, and SAML types of authentication. If your TrueSight Server Automation instance is configured to use Remedy SSO, you can now log on to TrueSight Automation Console using the Remedy SSO credentials.
For more information, see Configuring BMC Remedy Single Sign-on for TrueSight Automation Console.
Support for configuring a notice and consent banner before logging on
Some organizations are required to display a notice and consent banner when users log on to the application. These notices may contain the Standard Mandatory Department of Defense-approved content that users must read and agree before accessing the application. TrueSight Automation Console enables administrators to set up a banner to comply with your organizations standards.
You can configure notices for users only if your TrueSight Server Automation version is 21.02.
For details, see Configuring a notice and consent banner.
Support for managing risks for SUSE, CentOS, and Oracle Linux ULN
You can now import SUSE, CentOS, and Oracle Linux ULN catalogs from Automation Console and create patch policies to identify missing patches on the SUSE, CentOS, and Oracle Linux assets. If your scan file consists of vulnerabilities on the SUSE and Oracle Linux assets, the vulnerabilities are also automatically mapped to the endpoints in the endpoint manager and appropriate remediation content. For CentOS, one needs to manually map vulnerabilities to the endpoints in the endpoint manager.
You can also create a patch or a vulnerability operation for applying missing patches or remediating vulnerabilities on the SUSE, CentOS, and Oracle Linux assets.
For managing risks for Oracle Linux ULN, your TrueSight Server Automation version must be 21.02.
For details about managing missing patches or vulnerabilities, see Using.
Compliance management for assets
Compliance is the process of determining whether the assets in your environment meet a specific standard. That standard might be a regulatory standard, such as DISA or SOX, or an internal standard defined by your organization. Using Automation Console, you can manage compliance for assets.
You can create a compliance scan policy in Automation Console, which scans the specified assets, and displays the compliance posture (a percentage of compliant, non-compliant, and indeterminate assets) of the assets on the Risks > Compliance page. After identifying compliance violations on the scanned assets, you can create remediation operations to resolve the violated rules and make the assets compliant with the standards.
A new Compliance Dashboard shows the compliance posture, non-compliant assets by risk score, SLA, and stages, and other metrics about the compliance evaluations on the assets.
For details, see Compliance policy scans.
Creation of operation templates and operations for NSH Script and Deploy jobs
You can now create operation templates using which operators can create operations that run jobs in TrueSight Server Automation. Currently, NSH script and BLPackage Deploy (Basic) jobs are supported. An operation template can be shared with multiple security groups with a controlled choice of options to create operations of the same type repeatedly, and hence bringing more efficiency in running operations.
For details, see Working with operation templates.
Creation and approval of change requests using ServiceNow
You can now integrate Automation Console with ServiceNow IT Service Management system to create change requests and implement an approval process for remediation operations.
If an administrator enables change creation for your organization, you can create a change request while creating an operation. After the request is approved in ServiceNow, the operation runs according to a schedule. After the operation is complete, the change request is closed. The status of the change request is displayed on the Operations page.
Administrators enable change automation using the TrueSight Orchestration – ITSM Automation runbook.
For details, see Change automation.
Enhancements to exceptions
Vulnerability exceptions provides the following updates:
- Permanent exceptions: You can create exceptions to permanently exclude vulnerabilities on assets from being remediated. When you create a permanent exception, the end date is automatically set to 100 years from the start date.
- Extend exception end date: You can update the end date of an exception, which allows you to either extend or shorten the time period for excluding vulnerabilities from being remediated.
- New Create Date and Updated Date columns on the Manage exceptions page: On the Manage Exceptions page, you can now view the exception created and updated dates in separate columns. This is particularly useful if you want to see when was an exception created as the start and end dates do not provide this information.
For details, see Working with exceptions.
View additional details for missing patches and vulnerabilities
On the Risks > Missing Patches page, when you expand a missing patch name, you can view details such as the impacted asset name, operating system, risk owner, risk score, and SLA.
On the Risks > Vulnerabilities page, when you expand a vulnerability name, you can now view details such as the impacted asset name, operating system, risk owner, risk score, SLA, and the remediation content. This list shows the actionable assets, which are mapped to the remediation content and to endpoints in the endpoint manager.
For details, see Working with risks.
This release provides several changes to the existing features that improve your experience with the product:
- While adding and editing a patch policy and on the Administration > Manage Catalogs page, you can now view Operating System and Operating System Vendor columns, which provide additional information about the imported catalogs.
For details, see Working with catalogs.
- The Remediation Trend widget is renamed to Patch Trend on the Patch Dashboard and Vulnerability Trend on the Vulnerability Dashboard.
For details, see Using dashboards.
- On the Assets > Managed Assets page, the Compliance Violations column now shows the number of compliance policy violations on a given asset.
For details, see Working with assets.