The Assets page in the application lists the managed, scanned, and discovered assets depending on the endpoint manager, TrueSight Server Automation or TrueSight Network Automation.
For TrueSight Server Automation, the Managed Assets page shows a list of assets that are available in TrueSight Server Automation. When patch policies identify missing patches on assets, the assets with missing patches and other details appear on the Managed Assets page. Missing patches are identified only for assets with Windows or Linux operating systems (Red Hat Enterprise Linux, SuSE, Oracle Enterprise Linux, and CentOS only).
For TrueSight Server Automation, the Managed Assets page shows a list of assets that are available in TrueSight Network Automation. When you configure the TrueSight Network Automation connector, the network devices in the connected Network Automation instance appear on the Managed Assets page. When you add a device in Network Automation, the asset appears in Automation Console after the data collection interval specified in the connector.
On the Managed Assets page, you can add tags to the assets. To enter tag information, you export the assets data to a CSV file or click Import Tags to download a CSV template. Later, you upload the updated CSV file back in Automation Console.
The Scanned Assets tab shows a list of assets imported from a vulnerability scan file, their mapping to endpoints in an endpoint manager (TrueSight Server Automation or TrueSight Network Automation), and the number of vulnerabilities identified for each asset.
After you import a vulnerability scan file in Automation Console, assets are automatically mapped to endpoints managed by the endpoint manager. During auto-mapping, Automation Console matches the FQDN or hostname and then the IP address of an asset in a scan to the endpoint. Vulnerabilities are not automatically mapped to the remediation content unless assets are mapped to the endpoints. If an asset is decommissioned in the endpoint manager and an operation is not created for remediating missing patches or vulnerabilities, the asset gets unmapped in Automation Console. The asset status in Automation Console appears as Manually Unmapped. If the asset is recommissioned in Server Automation, the asset does not get automatically mapped again. You can always manually map the asset in Automation Console.
Automation Console may not always correctly auto-map all the endpoints because the firewalls, load balancers, and proxies can cause discrepancies in mapping. You can manually map each unmapped asset to a single endpoint only. If you map an asset to an endpoint, which is already mapped, the existing mapping is overwritten and the asset is mapped to the new endpoint.
On the Scanned Assets page, you can add tags to the assets. To enter tag information, you export the assets data to a CSV file or click Import Tags to download a CSV template. Later, you upload the updated CSV file back in Automation Console. In addition to the existing filters, tags provide another criterion to select a particular asset or a group of assets while creating a vulnerability remediation operation.
Currently, Automation Console supports integration with BMC Discovery for the TrueSight Server Automation endpoint manager only.The Discovered Assets tab shows the assets that are discovered by BMC Discovery. You configure the BMC Discovery connector to ensure that unmanaged, unscanned, and a total number of discovered assets are sent to Automation Console. If you change the BMC Discovery endpoint in the connector later, the data discovered from the previous BMC Discovery instance is also retained.
The total number of assets for each category appears at the top of the page. You can perform a basic or advanced search using filters to look for specific data.
Where to go from here
To view a list of discovered assets, assets with vulnerabilities and missing patches, and map assets, see Working with assets.