Manage Inventory for Secure Workload
Inventory is the IP addresses of all the workloads on your network, annotated with labels and other data that describes them. Your inventory includes workloads running on bare metal or virtual machines, in containers, and in the cloud. If applicable, it may also include workloads running on partner networks.
Collecting inventory data is an iterative process. Data from different sources for a single IP address can be merged, and new and changed IP addresses can be updated. Over time, management of your inventory should become increasingly dynamic.
You will work with and group your inventory using searches, filters, and scopes, based on the labels and annotations that are associated with each inventory item. Policies are applied to groups of workloads that are defined by the filters and scopes you define for your inventory.
Options for working with inventory vary depending on your role, but may include Search, Filters, and Upload.
|
Due to recent GUI updates, some of the images or screenshots used in the user guide may not fully reflect the current design of the product. We recommend using this guide in conjunction with the latest version of the software for the most accurate visual reference. |
|
Feature Name |
Release |
Feature Description |
Where to Find |
|---|---|---|---|
|
Inventory Enhancements |
3.9 |
You can manage and track the inventory of workloads, devices, and resources within the network, as well as the associated labels and subnets. |
Rules for Creating Inventory Filters. |
|
Integration of Cisco Vulnerability Management for Deep CVE Insights with Cisco Risk Score for Prioritization |
3.9 Patch 2 |
You can use the Cisco Security Risk Scores of the CVEs to create inventory filters, microsegmentation policies to block communication from the impacted workloads, and virtual patching rules to publish the CVEs to Cisco Secure Firewall. |
|
|
Visibility and Enforcement of Well-known IPv4 Malicious Traffic |
3.9 Patch 2 |
You can now identify traffic to and from the workloads to well-known malicious IPv4 addresses. Additionally, you can create policies to block traffic to these malicious IPs by using a predefined, read-only inventory filter titled Malicious inventories. |