The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Firepower Management Center provides a tool for importing data from other sources on your network to augment the monitored host information.
There are two ways to use the Host Input API to submit network map information, either by running the nmimport tool on the Management Center, or by using a remote client. In either case, you specify the network map details in a text file with comma-separated values (CSV format). Using the Host Input Import Tool gives general instructions, defines the CSV file format, and describes how to use the nmimport tool. Configuring Host Input Clients describes how to use a Host Import client.
For example, if you are setting up a new Firepower System, you might want to make sure that all the computers listed in your asset management software exist in the network map. You could export the host data from the asset management application, format the results into an appropriately formatted text file, and import the host data using the host input import tool. If the asset management system includes operating system information for each host, you can set up a third-party product map for the asset management system and map each third-party operating system label to the corresponding Cisco label. You can set that map before you run the import, and the system will associate the appropriate Cisco operating system definition with each host.
There are four major steps to using the host input import tool with the Firepower Management Center:
1. If you want to perform impact correlation using third-party host data, you can configure third-party product maps to map service, operating system, or fix definitions to Cisco product or fix definitions, using the Management Center web interface.
2. If you want to import third-party vulnerabilities, you can configure third-party vulnerability maps to map third-party vulnerability identification strings to Cisco vulnerability IDs, using the Management Center web interface. Note that you can also perform this mapping in your import file.
3. Export data from a third-party application and format it as a CSV file, as described in Using the Host Input Import Tool.
4. Submit the CSV file using either the nmimport tool or a Host Input client.
To understand the information in this guide, you should be familiar with the features and nomenclature of the Firepower Management Center and the function of its components (in particular, the network map), and with the various related event data the system generates. Information about these functions, together with definitions of unfamiliar or product-specific terms, may be obtained from the Firepower Management Center Configuration Guide. Additional information about the data fields documented in this guide may be obtained from the Configuration Guide as well.
The following table describes the product version required for various host input functionality:
The following table lists the names used in this book to describe the various data field formats employed in host input calls.
The following describes some of the topics explained in the documentation and where to look for more information.