In order for collectors to provide the
information necessary to generate compliance reports, Sentinel must
first be updated with asset data. What follows is the current
recommended method to populate this data.
- One needs to possess an asset system which generates asset data.
- By utilizing the mapping service in Sentinel 5, asset data can be exported to and distributed to all the agent managers to enrich the event stream. The external data can be delivered to the Sentinel system by the creation of a properly formatted asset.csv file that resides on the Sentinel server machine running Das Query.
Steps to generate and verify asset.csv file:
- Write a script to extract information from the asset sytem to generate asset data as a comma delimited file (no header). See below for the column definition of Asset CSV Columns.
- Launch SDM, go to Mapping->Maps->e-Security
- Drop asset.csv file in
$ESEC_HOME/sentinel/bin/map_data (Solaris) or %ESEC_HOME%\sentinel\bin\map_data
(Windows) on the Sentinel Server (the server running the Das
- After generating the file, it is recommended to use the update functionality of SDM to take a look at how your data looks after being generated into Mapping Data. In the Update Dialog, the "Newâ tab displays the data from the file you selected by using the Browse Button. The "Currentâ tab displays the data that is on the DAS server already. When you click OK on the Update Dialog, SDM will upload the data displayed in the New tab to the DAS server, effectively replacing the data displayed in the Current tab.
It is recommended that the importing of the external asset information happen on a daily basis, depending on how often asset information changes in your environment. Once the file is modified the mapping service distributes the changes to all the active agent managers.
The asset.csv file is stored in the EVT_ASSET table by the mapping service.
The asset data from an external system can be mapped into the Sentinel system by constructing the asset.csv file. The asset.csv file is located in $ESEC_HOME/sentinel/bin/map_data or %ESEC_HOME%\sentinel\bin\map_data (Windows). The file is a comma-separated value file. The asset.csv file contains the following columns:
Asset CSV Columns
Link ID (PhysicalAssetId) or external (100)
Asset CSV Column Descriptions
CustomerId is expected to be an integer,
all the other fields are variable length character strings. The sizes are in parenthesis in the Asset
CSV Columns table above.
CustomerId: Unless you are operating as an
MSSP, set CustomerId to 1.
PhysicalAssetName: Populate this to with
the IP address of your host.
AssetName: May be left blank.
LinkId: May be left blank.
Asset Event Definition
The mapping engine client in agent manager will populate the fields defined in the Asset Event Definition table below. It uses the source IP field (sip) to populate the source asset fields RV56-RV76 and the destination IP field (dip) to populate the destination asset fields RV78-RV98. RV77 and RV99 are filled in automatically with the i.d. of the asset from the EVT_ASSET table. The LinkId field is not mapped â this field could be used to store a key value to access your external data.
Asset Example Data
As we currently have a limitation where we cannot attach a file to a TID, below is an excerpt from an example asset.csv. NOTE, the header in asset.csv is for demonstration purposes - the real asset.csv should not have the header at all. For easier reading, copy the text below into a text file. View it with a text editor and turn off word wrap:
(PhysicalAssetId or external Id)