When you configure data forwarding, you define sets of data to export. Each set of data is known as a data group, and it includes data for the assets you define. After transferring the files to the destination Integrity installation, you then use data receiving to import the data from a data group to the receiving destination Integrity installation.
Data Forwarding Planning
If your Integrity deployment consists of sites that are disconnected from the enterprise level Integrity installation, you can configure data forwarding and receiving if you want to transfer data from the sites to the enterprise level.
When you configure data forwarding, you define a data group for each site that you want to forward to the top level installation of Integrity in your environment. In the data group, you define the assets and object types you want to forward. Integrity creates and writes a set of CFF files and a NewFiles.txt file to the export folder using the data group name as a subfolder. Some assets or object types might create additional files, such as CSV files. Copy everything from the data forwarding folders to the destination Integrity installation. After transferring the files to the destination Integrity installation, you can import those files to the other Integrity server or data collector where you configured data receiving for that set of assets.
-
If you are using data forwarding in a multi-site environment (site and enterprise), the following requirements apply:
-
The asset names must match in both environments and databases.
-
The Cyber Integrity hierarchy from the enterprise level must include all forwarded assets from the site level.
-
The enterprise and site installations should use the same asset model versions for forwarded data.
-
For Inventory Items select both assigned and native properties to forward.
-
-
If you are using the Vulnerability Management module in your deployment, you must use a specific folder structure to ensure that the enterprise level receives vulnerabilities from all the sites. For more information, see Vulnerability Management Folder Structure Requirements.
One step in your planning is to decide on a method to securely and regularly transfer the files from sites to destinations. Some options to consider include:
-
Use a secure file transfer application, such as Data Collection Control Center or Data Transfer Utility
-
Write a script to transfer files using SFTP
-
Manually transfer files or use an in-house application
The Data Forwarding link in the Admin Utility allows you to configure the properties for forwarding data from a source installation of Integrity. For each data group you create, you select the assets, object types and properties to forward and specify where to store those files. Integrity creates the schedule for creating those data files. Then, you enable the schedule and make any needed changes.
The Data Receiving link in the Admin Utility allows you to configure the properties for receiving forwarded data at a destination installation of Integrity. For each destination, create a data group and define the location where you plan to copy data forwarding files. Integrity creates the schedule for importing those data files. Then, you enable the schedule and make any needed changes. After you enable the schedule, Integrity imports the latest data files when it detects the NewFiles.txt file in the configured folder location. In most cases, you should need a single data receiving schedule to import data from separate sites or plants. In a few cases, you might have multiple schedules to accommodate importing data that is collected a different intervals. If you have more than one schedule for data receiving, make sure to allow enough time for each schedule to complete.
The last step is to implement your chosen method to transfer the files from sites to destinations.
Data Receiving Planning
After you configure data forwarding, you create a data group (schedule) in each destination installation of Integrity where you want to consolidate asset data you forward from the source Integrity installations. Use the Data Receiving link in the Admin Utility on the destination installation of Integrity to create a data group and define the folder where the source data is stored. The data for the assets is a set of folders containing CFF files and a NewFiles.txt file. Some assets or object types might create additional files, such as CSV files. Copy everything from the data forwarding folders to the destination Integrity installation. Integrity creates the import schedule as disabled and with the schedule set to Auto, which checks for the NewFiles.txt file, and imports the data when it finds that file after you enable the schedule.
In most cases, you should need a single data receiving schedule to import data from separate sites or plants. In a few cases, you might have multiple schedules to accommodate importing data that is collected at different intervals. If you have more than one schedule for data receiving, make sure to allow enough time for each schedule to complete.
-
If you are using data forwarding in a multi-site environment (site and enterprise), the following requirements apply:
-
The asset names must match in both environments and databases.
-
The Cyber Integrity hierarchy from the enterprise level must include all forwarded assets from the site level.
-
The enterprise and site installations should use the same asset model versions for forwarded data.
-
-
If you are using the Vulnerability Management module in your deployment, you must use a specific folder structure to ensure that the enterprise level receives vulnerabilities from all the sites. For more information, see Vulnerability Management Folder Structure Requirements.