AssetModelImportConn DevGuide
AssetModelImportConn DevGuide
ArcSight ESM
Software Version: 7.6
Legal Notices
Copyright Notice
© Copyright 2001-2021 Micro Focus or one of its affiliates
Confidential computer software. Valid license from Micro Focus required for possession, use or copying. The
information contained herein is subject to change without notice.
The only warranties for Micro Focus products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an additional warranty.
Micro Focus shall not be liable for technical or editorial errors or omissions contained herein.
No portion of this product's documentation may be reproduced or transmitted in any form or by any means, electronic
or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other
than the purchaser's internal use, without the express written permission of Micro Focus.
Notwithstanding anything to the contrary in your license agreement for Micro Focus ArcSight software, you may
reverse engineer and modify certain open source components of the software in accordance with the license terms for
those particular components. See below for the applicable terms.
U.S. Governmental Rights. For purposes of your license to Micro Focus ArcSight software, “commercial computer
software” is defined at FAR 2.101. If acquired by or on behalf of a civilian agency, the U.S. Government acquires this
commercial computer software and/or commercial computer software documentation and other technical data subject
to the terms of the Agreement as specified in 48 C.F.R. 12.212 (Computer Software) and 12.211 (Technical Data) of the
Federal Acquisition Regulation (“FAR”) and its successors. If acquired by or on behalf of any agency within the
Department of Defense (“DOD”), the U.S. Government acquires this commercial computer software and/or commercial
computer software documentation subject to the terms of the Agreement as specified in 48 C.F.R. 227.7202-3 of the
DOD FAR Supplement (“DFARS”) and its successors. This U.S. Government Rights Section 18.11 is in lieu of, and
supersedes, any other FAR, DFARS, or other clause or provision that addresses government rights in computer software
or technical data.
Trademark Notices
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Support
Contact Information
Phone A list of phone numbers is available on the Technical Support
Page: https://softwaresupport.softwaregrp.com/support-contact-information
Page 3 of 15
Chapter 1: Overview
The Asset Model Import FlexConnector enables you to develop a model import connector to
import the asset model data from a file, so you can create and maintain ESM Network Model
data, and keep this data in sync with the data in your Asset Management system. Based on
configuration, files are read by the connector, and converted to XML based on parser
attributes. Upon generation, the XML files are automatically transferred by the connector to
the ESM server.
You configure the connector using the SmartConnector Configuration Wizard. Also, you must
create parser files from the provided template that match the format of the CSV files.
The connector supports two modes of operation:
l Initial read and import
l Ongoing detection and import of updates
During the initial read and import for attributes specified in the CSV files, the connector can
import a full set or subset of attributes for each asset based on CSV file content and
corresponding matching parser configuration.
After the information is imported into ESM, the list of attributes the connector sends to ESM
for existing assets is not updated. If you add or remove attributes to be sent to ESM from the
connector after you import the asset data, you will not get a history of the new attributes.
Updates will only be from the point of time the attributes were added. If you want a history of
the added attributes, re-import the asset data.
Assumptions
You should be familiar with writing a parser for Log File FlexConnector. Refer to the
FlexConnector Developer's Guide for more information about writing a parser.
Attribute Description
Name The asset’s friendly name. This field can default to the asset’s host name or IP address. This name is
listed in the Asset tree in ESM.
Alias The asset’s display name. If an alias is not specified, the asset name is used. Typically used in a
localized environment to display the asset name in the local language.
Parent The URI of the asset’s immediate parent group in the hierarchy, based on ESM’s Asset tree. For
Group example, /All Assets/Customer A/.
Old Parent Used only to move one asset from one group to another. Is the URI of the source group for the
Group asset.
Zone As described in Assets and Changing Assets. Specify the Zone URI of the Asset, as shown in the in
ESM Zones tree.
Category The URI of the category to which the asset belongs. An asset can belong to more than one category.
Assets can be categorized based on business use, criticality, applications, hardware, operating
system, or other criteria. If a category does not exist, it is automatically created for the asset. For
example, for the category Criticality, an asset can belong to the category High (with the Criticality
categories of High, Medium, and Low).
Prerequisites
Before installing the Asset Model Import FlexConnector, the following prerequisites must be
met:
l Ensure that ESM and the Console are installed. For more information, see the ArcSight ESM
Installation and Configuration Guide.
l Local access to the machine where the Asset Model Import FlexConnector is to be installed
and administrator privileges to that machine.
l A minimum of 256 MB of memory and 3 GB of available hard disk space on the host
machine.
l Start the Manager. The command prompt window or terminal box displays a Ready
message when the Manager starts successfully. Monitor the server.std.log file located
in $ARCSIGHT_HOME\logs\default. Although not required, it is helpful to have the Console
running when installing the Asset Model Import FlexConnector to verify a successful
installation.
l Zones must have been created in ESM to use with the assets, using the Network Modeling
Wizard in the ArcSight Console. If the zones are not created, assets are not assigned to
zones, and the zone information for the asset is ignored.
l ArcSight ESM must be up and running to configure the Asset Model Import FlexConnector.
Note:
l Use a non-root account to install the Asset Model Import FlexConnector.
l Do not store your parser files in the same folder as the connector installation files.
1. Using the log-in credentials supplied to you by ArcSight, download the Asset Model Import
FlexConnector installation executable file from the software support site to the machine
where the connector will run.
Chapter 3: Installing and Configuring the Asset Model Import FlexConnector Page 6 of 15
Asset Model Import FlexConnector Developer's Guide
Chapter 3: Installing and Configuring the Asset Model Import FlexConnector
Note: The options for FIPS and remote management are not applicable at this time when “Set
Global Parameters” is selected for this connector.
Folder Enter the complete path to the folder containing the CSV log files. Each folder must contain CSV
Location files of the same format, and associated with the same parser.
Parser File Enter the name of the parser associated with the specific CSV folder. The parser must match for
Name the format of the CSV file. You can create a different parser format for each folder configured.
Use Import and Export to copy the list of folders and parsers to or from a spreadsheet if
needed. Click Next.
5. In the destination type window, verify that ArcSight Manager (encrypted) is selected and
click Next.
Note: When selecting destinations for the Asset Model Import FlexConnector, select
ArcSight Manager (encrypted) only. No other destinations are supported.
6. Enter destination parameters, including the host and port information, and click Next.
Parameter Description
Manager Host Enter the name of the host on which the Manager is installed.
Name
Manager Port Enter the network port from which the Manager is accepting requests. The default port is
8443.
User Name Enter a valid ArcSight user name to log in to configure the SmartConnector. This is the same
user name you created during the Manager installation.
Password Enter a valid ArcSight password to log in to configure the SmartConnector. This is the same
password you created during the Manager installation.
7. Enter connector details. Enter a name for the SmartConnector and provide other
information identifying the connector’s use in your environment. Click Next.
8. Select whether to import a certificate. Click Next.
9. Read the SmartConnector summary and click Next. If the summary is incorrect, click
Previous and make changes.
10. The Wizard now prompts you to choose whether you want to run the SmartConnector as a
process or as a service. If you choose to run the SmartConnector as a service, the Wizard
prompts you to define service parameters for the SmartConnector. Click Next. The Wizard
displays a dialog confirming the SmartConnector’s configuration.
11. Choose Exit and click Next.
12. Click Done.
A parser example that you can use as is or use as a template is created during the configuration
process is located at: $ARCSIGHT_HOME\user\agent\flexagent\mic\asset_flexfile\.
Running SmartConnectors
SmartConnectors can be installed and run in standalone mode, on Windows platforms as a
Windows service, or on UNIX platforms as a UNIX daemon, depending upon the platform
supported.
Note :
Note: "user" indicates the non-root user that you installed the MIC with. This is usually the
"arcsight" user.
Start the service
cd /etc/init.d
./arc_model_asset_flexfile start
On Windows platforms, SmartConnectors also can be run using shortcuts and optional Start
menu entries.
If installed standalone, the SmartConnector must be started manually, and is not automatically
active when a host is re-started. For Windows, you will have to start the Service manually using
Windows "Services". If installed as a service or daemon, the SmartConnector runs
automatically when the host is re-started. For information about connectors running as
services or daemons, see the ArcSight SmartConnector User's Guide.
For connectors installed standalone, to run all installed SmartConnectors on a particular host,
open a command window, go to $ARCSIGHT_HOME\current\bin and run: arcsight agents
To view the SmartConnector log, read the file:
$ARCSIGHT_HOME\current\logs\agent.log
Note: If you want categories to be created automatically on the ESM server side, the property
archive.import.asset.category.auto.create must be set to true in the server.properties
property file. See the ArcSight Console User’s Guide, “Asset Model”, for details on working with
assets. See the ESM Administrator’s Guide, “Editing Properties Files”, for details on how to edit a
properties file.
*the asset can be inactive or active based on the value passed (true or false) to enable or
disable the asset
An example of a CSV file:
addAsset,,,asset_1,199.199.0.1,00:11:22:33:44:51,myhostname_1,myexternalid_
1,myalias_1,myparentgroupuri_
1,,myassetdesc,myzoneuri,mylocationuri,myassetcategory
Where AssetCategory can be multiple categories separated by ";" and Action can be one of the
following:
l addAsset: Creates an asset
l updateAsset: Update an existing asset on the server. The server will update asset
attributes and merge categories.
l removeAsset: Removes the asset
l addCategory: Assigns one or more categories, separated by a semi-colon (;)
l removeCategory: Removes one or more categories, separated by a semi-colon (;)
l addZone: Assigns a zone. An asset can belong to one zone only. If an asset belongs to a
zone, the newly-added zone will replace the existing zone. Do not add assets from more
than one zone in a CSV file. Generate separate CSV files to contain assets from different
zones.
l removeZone: Removes the asset from a zone.
l moveAsset: Removes the asset from the existing parent group and associates it with the
new parent group.
Note: The connector does not validate the data in the CSV file or in the XML archive. The
archive can fail processing based on existing edit checks in ESM.
delimiter=,
token.count=15
token[0].name=Action
token[0].type=String
token[1].name=Inactive
token[1].type=String
token[2].name=InactiveReason
token[2].type=String
token[3].name=AssetName
token[3].type=String
token[4].name=Ip
token[4].type=String
token[5].name=Mac
token[5].type=String
token[6].name=HostName
token[6].type=String
token[7].name=ExternalId
token[7].type=String
token[8].name=Alias
token[8].type=String
token[9].name=ParentGroupUri
token[9].type=String
token[10].name=OldParentGroupUri
token[10].type=String
token[11].name=AssetDescription
token[11].type=String
token[12].name=ZoneUri
token[12].type=String
token[13].name=LocationUri
token[13].type=String
token[14].name=AssetCategory
token[14].type=String
additionaldata.enabled=true
additionaldata.duplicate.keys.allowed=false
event.deviceEventCategory=__stringConstant(Asset)
event.deviceCustomString1Label=__stringConstant(model.sender)
event.deviceCustomString1=__stringConstant(flexcsv)
event.deviceCustomString2Label=__stringConstant(model.template)
event.deviceCustomString2=__stringConstant(mic/asset_flexcsv/asset.vm)
###field mappings###
event.deviceVendor=__getVendor(CSV File)
event.deviceProduct=__stringConstant(Assets)
event.deviceAction=Action
additionaldata.Action=Action
event.externalId=ExternalId
event.flexString1=AssetName
additionaldata.UniqueUserId=AssetName
event.destinationUserId=AssetName
Action Defines the action you can take. See "Default CSV Format" on page 10 for details on
possible actions.
AssetName The asset’s friendly name. This field can default to the asset’s host name or IP address. This
name is listed in the Asset tree in ESM.
Attribute Description
Alias The asset’s display name. If an alias is not specified, the asset name is used. Typically used
in a localized environment to display the asset name in the local language.
ParentGroupUri The URI of the asset’s immediate parent group in the hierarchy, based on the Console’s
Asset tree. For example, “/All Assets/Customer A/”.
OldParentGroupUri Used only to move one asset from one group to another. Is the URI of the source group for
the asset.
ZoneUri As described in Assets and Changing Assets. Specify the Zone URI of the Asset, as shown in
the in ESM Zones tree.
AssetCategory The URI of the category to which the asset belongs. An asset can belong to more than one
category. Assets can be categorized based on business use, criticality, applications,
hardware, operating system, or other criteria. If a category does not exist, it is automatically
created for the asset. For example, for the category Criticality, an asset can belong to the
category High (with the Criticality categories of High, Medium, and Low).
Note: Be sure not to delete all asset folders. Some asset folders are default folders supplied
by ESM. Delete only the asset data managed by this connector.
Highlight the asset folder you need to delete, then right-click and choose Delete Group
from the menu.
5. On the connector side, reconstitute the asset data by recopying it from its original source,
or renaming the backup files to their original file names.