DOC4000 can forward the following types of data:
-
Vulnerability data as one or more CFF files
-
Inventory data as CFF and CSV files
-
Normalization settings as CFF files
-
System settings (rare)
Vulnerability data
Cyber DOC4000 collects information about your assets and compares it to the latest known vulnerability and patch information, identifying assets to investigate.
Inventory data
An inventory item is an asset or component of an asset, such as an installed software product or a hardware component. The PAS Inventory Items asset model uses information from the other asset models and assets to build a set of inventory items in Cyber DOC4000.
Normalization settings
You can define a single, normalized, name or value when manufacturers, products, or engineering units are represented in different ways in your data. For example, some products in your environment could be represented by Microsoft or Microsoft, Inc. Also, you might have different versions of the same product that you want to see as a single unit.
Normalization rules allow you to identify these multiple variations and set a single, normalized value that represents all the variations. Normalized values apply to search results in Vulnerability Management, Inventory, and Sensor Data Integrity.
You can export and import normalization rule sets to maintain consistency between sites with different DOC4000 servers. To accomplish this scenario, export the rule set to a CFF file using data forwarding steps, and then import the rule set from the CFF file using data receiving steps.
System settings
Some information you may want to forward is system information, which is not associated with an asset model. To select this information in the Data Forwarding window on the source DOC4000 installation, check the System check box and select System in the Assets list. Then, you can select the object types and properties you want to forward.
To receive system information on the destination DOC4000 installation, you need an asset to associate with the import. Since system information is not associated with an asset model, you can create any type of asset on the destination DOC4000 installation, and then import the data by selecting the correct import folder that contains the system data files. The system information is stored in the correct way on the destination DOC4000 installation regardless of the asset associated with the data import on that installation.