A device profile contains all essential data of a specific device in a dedicated web page. Think of a device profile as something like a Facebook page for an OT device. Just like a Facebook user profile, it may contain pictures, a timeline, links to "friends" (connected devices), and so on.
Opening a device profile
There are various ways how to open a device profile:
- In the device list, select a device and click on "Profile" -- or just double click on the respective table row
- Enter the device ID, serial number, unique MAC or IP address in the quick search and hit Enter
- Click on a device ID in any other profile (network profile, location profile etc.).
- Directly call the device profile's URL (see below).
You can open a device profile from another application by calling its URL, which you can copy to the clipboard by clicking on the link icon in the upper right corner of the profile window.
Device profiles always open a new browser window, allowing you to move the profile around (for example to a second screen) while checking other content. This also makes it easy to inspect multiple device profiles side by side.
A device profile contains several sections, depending on the configuration and metadata for this device (if there is no data available for a given section, the section will not show). All sections except for the header can be expanded or collapsed by clicking on the grey title bar.
The header contains the device ID, followed by the device name in brackets. Below the device ID you see the device type, and below the type is the product model (if available). The header may also contain a product picture if you have set one for the product in question. If no product picture is available, the vendor logo is shown for some vendors, or an icon representing the device type.
General information including the device lifecycle stage, installation date, device description, documentation link. Below this you will see device context information including the device group, OT system association, and device location. Below that follows the physical process association and the location of the affected process. Thereafter you will see data on safety, criticality, security, and network zone.
If any extended (custom) fields have been defined, they will be displayed in this section.
Any tags that users, or OTbase have assigned to this device. OTbase automatically assigns tags reflecting the protocols that have been used to discover the device.
Information about the hardware product, such as vendor, model, and serial number. If the device contains modules (such as I/O interface cards), they will be shown in a table below this information.
If the device is a control system rack, you will see the hardware configuration in this section. Any obsolete firmware versions will be highlighted in orange. If you hover over outdated firmware entries, the current firmware version will be shown as a tooltip.
Data on the network and/or serial point-to-point connections of the device. This data is always displayed both in a table and in an automatically generated network neighborhood diagram. You can zoom the diagram by picking the lower right corner of the diagram box, hold the mouse button, and move the mouse. IP addresses that are obtained via DHCP will be shown in boldface and italics.
Observed data flow for the device if Netflow/SFlow data is available. Data flow is shown as a Sankey diagram, as a fully interactive network diagram, and in tables (including IP address information). Note that you can drill down in the network diagram by double-clicking nodes.
Installed software, or, in the case of embedded devices, installed firmware.
Compliance in respect to one or more policies that are assigned to this device. In the case of non-compliance, the reason (such as missing software, or presence of unauthorized software) is pointed out.
Installed security software, anti-virus products, security patches, and known vulnerabilities for the device.
By default, only vulnerabilities with known exploits are shown. If you want to see the full list of vulnerabilities, uncheck the "KEV only" box. Vulnerabilities with known exploits are always highlighted in orange.
Any open change cases of which the device is part of.
Any problem reports for this device.
Users associated with this device according to their responsibilities as defined in the user management.
Links to any files that are attached to the device (such as documentation, software images, backups, etc.).
The device's configuration history.
Details on the last discovery results.
Navigating device profiles (drill-down), and hyperlinks
A device profile contains a lot of hyperlinks that you can use to access related information which might be useful for the task at hand. The objective of OTbase is to allow you gather all that information with a maximum of five clicks.
As an example, anywhere where other devices are referenced, such as in a connectivity table, you can launch the device profile of these other devices by clicking on the device ID. Or you can click on the model identification to launch the product profile. Or on the location descriptor to launch the location profile. And so on.
As another example, clicking on an IP address of a device in its connectivity section tries to open a direct HTTP connection to the device in a new browser window. This way, if your device has an embedded web server, you can directly access the device's configuration UI. -- Note that the HTTP connection is established from your client PC, not from OTbase Inventory. Therefore, if your client PC is in a network where it cannot route into the target device's network, no connection can be established.