Understanding Assets, Data Owners, and Asset Models - PAS ICS Integrity - 7.3 - Administration & Configuration - Intergraph

ICS Integrity Administration Guide

Language
English
Product
PAS ICS Integrity
Subproduct
ICS
Search by Category
Administration & Configuration
PAS Version
7.3

Integrity provides a wide array of asset models to allow Integrity to incorporate data from many types of systems. Each asset model helps collect configuration data from specific types of systems, such as Honeywell EPKS, and use that information in Integrity. With this data, Integrity displays inventory information, identifies configuration discrepancies, detects unauthorized changes due to malicious attack or inadvertent engineering updates, and enables sustained compliance with regulatory or corporate standards. An asset model is available to Integrity customers who purchase a license for the asset model and configure that model. You can also create or customize your own asset models using the Asset Model Development Kit (AMDK). For example, you can create defect checks that verify control system configuration data and viewer tabs that allow you to review or modify configuration data as needed. For more information, run the InstallPath\DataCollector\AMDK.exe file as an administrator, and then click Help.

Once you load an asset model, you can create one or more assets of the type defined by that asset model. In most cases, such as for ICS systems, each Integrity asset represents one system. For example, each Honeywell EPKS asset represents one Honeywell EPKS system. However, in some cases, such as for the Network Devices and Recon asset models, you create an asset that represents a group of systems such as network devices or Windows computers. In these cases, the term data owner is often used in place of asset. A data owner is the asset you create in Integrity that is associated with a set of data collected for the asset model. Therefore, these two terms often mean the same thing.

The Implementation Guide for an asset model provides information about that version of the asset model as well as detailed guidance for installing and configuring that model. For most asset models, the general implementation process involves:

  1. Verify the system requirements for the asset model.

  2. Collect the needed data from each system of the type supported by the model. Each model often provides collection utilities and scripts.

  3. Load the asset model. This task is also called importing the asset model.

  4. Create an asset for each group of collected data, such as per data owner.

  5. Configure each asset to identify the location of the collected data. Depending on the asset model, the location can be an import folder or a database connection.

  6. Configure additional properties to support references for other assets. For example, some Honeywell EPKS systems may reference other systems, such as Honeywell TPS systems or other Honeywell EPKS systems.

  7. Import the collected data and verify the results.

  8. Schedule data collection and import to keep the data in Integrity up to date.