Esm admin guide_5.2

ArcSight ESM
Administrator’s Guide
ArcSight™ ESM Version 5.2
January 2012

ArcSight ESM Administrator’s Guide ArcSight™ ESM Version 5.2
Copyright © 2012 Hewlett-Packard Development Company, LP. All rights reserved.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent
with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and
Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard
commercial license.
The information contained herein is subject to change without notice. The only warranties for HP 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. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Follow this link to see a complete statement of copyrights and acknowledgements:
http://www.arcsight.com/copyrightnotice
The network information used in the examples in this document (including IP addresses and hostnames) is
for illustration purposes only.
This document is confidential.
Revision History
Document template version: 1.0.2.9
Contact Information
Date Product Version Description
01/15/2012 ArcSight ESM Version 5.2 new features
Phone 1-866-535-3285 (North America)
+44 (0)870 141 7487 (EMEA)
Support Web Site http://www.support.openview.hp.com
Protect 724 Community https://protect724.arcsight.com

Confidential ArcSight ESM Administrator’s Guide 3
Contents
Chapter 1: Basic Administration Tasks ................................................................................ 9
Running ArcSight ESM ..................................................................................................... 9
Starting the ArcSight Manager .................................................................................... 9
ArcSight Manager Decoupled Process Execution .................................................... 10
Starting the ArcSight Console ................................................................................... 10
Setting up a Custom Login Message .................................................................... 11
Starting ArcSight SmartConnectors ........................................................................... 11
Stopping the ArcSight Manager ................................................................................. 12
Reconnecting to the ArcSight Manager ....................................................................... 12
Configuring ArcSight Manager or ArcSight Web as a Service ......................................... 12
ArcSight Manager Service Setup on Windows ........................................................ 12
Starting and Stopping the ArcSight Manager Service on Windows ............................ 12
Removing the ArcSight Manager Service on Windows ............................................. 13
ArcSight Manager or ArcSight Web Service Setup on Unix Platforms ........................ 13
Reducing Impact of Anti-Virus Scanning ........................................................................... 14
License Tracking and Auditing ......................................................................................... 14
ArcSight System Tasks .................................................................................................. 14
Chapter 2: Configuration ................................................................................................... 17
Managing and Changing Properties File Settings ................................................................ 17
Property File Format ................................................................................................ 17
Defaults and User Properties .................................................................................... 18
Editing Properties .................................................................................................... 18
Dynamic Properties ................................................................................................. 19
Example .......................................................................................................... 20
Changing Manager Properties Dynamically ........................................................... 21
Changing the Service Layer Container Port ........................................................... 22
Securing the ArcSight Manager Properties File ............................................................. 22
Adjusting Console Memory ............................................................................................. 23
Adjusting Pattern Discovery Memory ................................................................................ 23
Installing New License Files Obtained from ArcSight ........................................................... 23
Installing in Silent Mode ........................................................................................... 24
Configuring ArcSight Manager Logging ............................................................................. 24
Sending logs and diagnostics to HP Support ................................................................ 25

4 ArcSight ESM Administrator’s Guide Confidential
Guidelines for using the Send Logs utility ............................................................. 25
Gathering logs and diagnostic information ............................................................ 26
Understanding SSL Authentication ................................................................................... 33
Terminology ........................................................................................................... 34
Tools for SSL Configuration ...................................................................................... 38
Keytoolgui ....................................................................................................... 38
keytool ............................................................................................................ 42
tempca ............................................................................................................ 43
How SSL Works ...................................................................................................... 43
SSL certificates ....................................................................................................... 44
Types .............................................................................................................. 44
Comparing Self-signed and CA-signed certificates ................................................. 45
Using a Demo Certificate ......................................................................................... 45
Using a Self-Signed Certificate .................................................................................. 46
When clients communicate with one ArcSight Manager .......................................... 46
When clients communicate with multiple ArcSight Managers ................................... 49
Using a CA-Signed SSL Certificate ............................................................................. 51
Create a Key Pair for a CA-Signed Certificate ........................................................ 51
Send for the CA-Signed Certificate ...................................................................... 52
Import the CA Root Certificate ............................................................................ 52
Import the CA-Signed Certificate ........................................................................ 53
Restart the Manager .......................................................................................... 55
Accommodating Additional ArcSight Components .................................................. 56
Removing a Demo Certificate ............................................................................. 56
Replacing an Expired Certificate ................................................................................ 56
Establishing SSL Client Authentication ....................................................................... 57
Setting up SSL Client-Side Authentication on ArcSight Console running in Default Mode .
57
Setting up SSL Client Authentication on ArcSight Web ........................................... 64
Setting up Client-side Authentication on Partition Archiver and SmartConnectors ....... 69
Migrating from one certificate type to another ............................................................. 71
Migrating from Demo to Self-Signed .................................................................... 71
Migrating from Demo to CA-Signed ..................................................................... 71
Migrating from Self-Signed to CA-Signed ............................................................. 72
Verifying SSL Certificate Use .................................................................................... 72
Sample output for verifying SSL certificate use ..................................................... 72
Using Certificates to Authenticate Users to ArcSight ..................................................... 73
Using the Certificate Revocation List (CRL) ................................................................. 73
Reconfiguring the ArcSight Console after Installation .......................................................... 74
Reconfiguring ArcSight Manager ...................................................................................... 74
Changing ArcSight Manager Ports .............................................................................. 74
Changing ArcSight Web Session Timeouts .................................................................. 75
Manager Password Configuration ..................................................................................... 75
Enforcing Good Password Selection ........................................................................... 75

Password Length .............................................................................................. 75
Restricting Passwords Containing User Name ........................................................ 75
Requiring Mix of Characters in Passwords ............................................................. 76
Checking Passwords with Regular Expressions ...................................................... 76
Password Uniqueness ........................................................................................ 77
Setting Password Expiration ..................................................................................... 77
Restricting the Number of Failed Log Ins .................................................................... 78
Re-Enabling User Accounts ....................................................................................... 78
Properties Related to Domain Field Sets ........................................................................... 79
Advanced Configuration for Asset Auto-Creation ................................................................ 79
Asset Auto-Creation from Scanners in Dynamic Zones .................................................. 80
Create Asset with either IP Address or Host Name ................................................. 80
Preserve Previous Assets ................................................................................... 81
Changing the Default Naming Scheme ....................................................................... 82
Compression and Turbo Modes ........................................................................................ 82
Compressing ArcSight SmartConnector Events ............................................................ 82
Understanding ArcSight Turbo Modes ......................................................................... 83
Configuring the ArcSight Database Monitor ....................................................................... 84
Configuring Database Monitor e-mail message recipients .............................................. 84
Configuring the check for free space in Oracle tablespaces ............................................ 84
Sending Events as SNMP Traps ....................................................................................... 85
Configuration of the SNMP trap sender ....................................................................... 85
Asset Aging .................................................................................................................. 86
Excluding Assets From Aging .................................................................................... 87
Task to Disable Assets of a Certain Age ...................................................................... 87
To Delete an Asset .................................................................................................. 87
Amortize Model confidence with scanned asset age ...................................................... 87
Configuring Actors ........................................................................................................ 88
Tuning Guide for Supporting Large Actor Models ......................................................... 90
Permissions Required to Use Actors and Actor-Related Data .......................................... 91
About Exporting Actors ............................................................................................ 92
Chapter 3: Database Administration ................................................................................. 93
Changing Oracle Initialization Parameters ......................................................................... 93
Monitoring Available Free Space in Tablespaces ................................................................. 94
Setting Up Database Threshold Notification ................................................................. 94
Resetting the Oracle Password .................................................................................. 94
Backing up ArcSight Databases ....................................................................................... 95
Oracle Cold Backup ................................................................................................. 95
Oracle Hot Backup .................................................................................................. 95
Exporting Data ....................................................................................................... 96
Recovering ArcSight Databases ....................................................................................... 96
Speeding up partition compression .................................................................................. 96

Partition logs ................................................................................................................ 97
Chapter 4: Managing Resources ........................................................................................ 99
Appendix A: ArcSight Commands .................................................................................... 101
Running an ArcSight Command ......................................................................................101
Command Descriptions .................................................................................................102
Appendix B: Troubleshooting .......................................................................................... 147
General ......................................................................................................................147
Query and Trend Performance Tuning .............................................................................150
Persistent Database Hints .......................................................................................150
server.defaults.properties Entries for Trends ..............................................................150
Troubleshooting Checklist after Restarting the Manager ...............................................151
Reports for Monitoring Trend Performance .................................................................151
Disable these Trends on High Throughput Systems .....................................................151
How do you know when a trend is caught up? ............................................................152
How long does it take a trend to catch up? ................................................................152
Enhancing the Performance Globally for all Database Queries .......................................152
SmartConnectors .........................................................................................................153
Console ......................................................................................................................153
Manager .....................................................................................................................155
ArcSight Web ..............................................................................................................157
Database ....................................................................................................................158
SSL ............................................................................................................................158
Cannot connect to the SSL server: IO Exception in the server logs when connecting to the serv-
er ........................................................................................................................158
Cannot connect to the SSL server ............................................................................159
PKIX exchange failed/could not establish trust chain ...................................................159
Issuer certificate expired .........................................................................................159
Cannot connect to the Manager: Exception in the server log ........................................159
Certificate is invalid ................................................................................................159
Issue with Internet Explorer and ArcSight Web in FIPS Mode .......................................160
Appendix C: Monitoring Database Attributes ................................................................... 161
Understanding Database Checks ....................................................................................161
Message text .........................................................................................................162
Disabling Database Checks ............................................................................................162
List of Database Check Tasks .........................................................................................163
Appendix D: The Logfu Utility ......................................................................................... 167
Running Logfu .............................................................................................................168
Example .....................................................................................................................170
Troubleshooting ...........................................................................................................170

Menu ..........................................................................................................................172
Typical Data Attributes ..................................................................................................172
Intervals .....................................................................................................................173
Appendix E: Creating Custom E-mails Using Velocity Templates ..................................... 175
Overview ....................................................................................................................175
Notification Velocity templates .......................................................................................175
Commonly used elements in Email.vm and Informative.vm files ...................................175
The #if statement ............................................................................................175
Contents of Email.vm and Informative.vm .................................................................176
How the Email.vm and Informative.vm Template Files Work ........................................177
Understanding the Customization Process ..................................................................177
Customizing the template files .................................................................................178
Sample Output ......................................................................................................179
Appendix F: The Archive Command Tool ......................................................................... 181
Archive Command Modes ..............................................................................................181
Remote Mode ........................................................................................................182
Standalone Mode ...................................................................................................182
Exporting Resources to an Archive ..................................................................................183
Importing Resources from an Archive ..............................................................................184
About Importing v3.x Content to a v4.x ESM System ..................................................184
Syntax for Performing Common Archive Tasks .................................................................187
Appendix G: TLS Configuration to Support FIPS Mode ..................................................... 189
NSS Tools Used to Configure Components in FIPS Mode ....................................................190
Types of Certificates Used in FIPS Mode ..........................................................................190
Using a Self-Signed Certificate .......................................................................................190
Using a Certificate Authority (CA) Signed Certificate ..........................................................191
Steps Performed on the Manager .............................................................................191
Steps Performed on the Web ...................................................................................195
Steps Performed on the Console ..............................................................................200
Some Often-Used SSL-related Procedures .......................................................................203
Generating a Key Pair in a Component’s NSS DB ........................................................203
On the Manager ...............................................................................................203
On the Console ................................................................................................204
On ArcSight Web .............................................................................................205
Verifying Whether the Key pair Has Been Successfully Created ...............................205
Viewing the Contents of the Certificate ...............................................................206
Exporting a Certificate ............................................................................................206
From the Manager ............................................................................................206
From the Console .............................................................................................206
From the Web .................................................................................................206

Importing a Certificate into NSS DB ..........................................................................207
On the Manager ...............................................................................................207
On the Console ................................................................................................208
On ArcSight Web .............................................................................................208
Importing an Existing Key Pair into the NSS DB .........................................................208
Setting up Server-Side Authentication .............................................................................209
Setting up Client-Side Authentication ..............................................................................209
Changing the Password for NSS DB ................................................................................211
Listing the Contents of the NSS DB .................................................................................212
Veiwing the Contents of a Certificate ..............................................................................212
Setting the Expiration Date of a Certificate ......................................................................212
Deleting an Existing Certificate from NSS DB ...................................................................213
Replacing an Expired Certificate .....................................................................................213
Using the Certificate Revocation List (CRL) ......................................................................214
Migrating an Existing Default Mode ESM Installation to FIPS Mode ......................................214
Appendix H: Monitoring System Health ........................................................................... 215
Overview ....................................................................................................................215
What to Monitor .....................................................................................................215
ArcSight Appliances ................................................................................................216
ArcSight ESM ........................................................................................................217
ESM Component Configuration .......................................................................................218
Configuring SmartConnectors ..................................................................................218
Configuring the Connector Appliance ........................................................................218
Configuring Logger .................................................................................................219
Configuring ESM ....................................................................................................219
ESM Content Configuration ............................................................................................219
Configure Critical Device Not Reporting Resources ......................................................219
Configure White List Filters ...............................................................................220
Configure Critical Device Not Reporting Rule ........................................................222
Configure Connector Monitoring Resources ................................................................222
Configuring Active Lists for Connector Information and Up or Down Status ..............224
Rules Relating for Connector Up or Down Status ..................................................224
Index .................................................................................................................................................... 227

Chapter 1
Basic Administration Tasks
This chapter describes the various tasks that you can perform to effectively manage an
ArcSight ESM installation, performing additional configuration and maintenance operations
for ArcSight Manager and the database.
The following topics are covered here:
Running ArcSight ESM
Unless ArcSight ESM is configured to run as a service, you run ArcSight Manager, Console,
and SmartConnectors using the Start menu. For Linux and Solaris, you need to start the
ArcSight Manager from a command or console window, or set up ArcSight Manager as a
daemon. The remainder of this section provides more information about command line
options you can use to start up, shut down, configure, or reconfigure ESM components. In
addition, it provides information about setting up ArcSight Manager as a daemon (on Unix
platforms) or as a service (on Windows), if you didn’t originally configure ArcSight Manager
that way.
Starting the ArcSight Manager
To start ArcSight Manager from the command line, if it’s not configured to run either as a
daemon or a service:
1 Open a command window or terminal box.
2 Change directories to the ArcSight Manager bin directory:
3 Type in the following line and press Enter.
“Running ArcSight ESM” on page 9
“Starting the ArcSight Manager” on page 9
“Starting the ArcSight Console” on page 10
“Starting ArcSight SmartConnectors” on page 11
“Stopping the ArcSight Manager” on page 12
“Reconnecting to the ArcSight Manager” on page 12
“Configuring ArcSight Manager or ArcSight Web as a Service” on page 12
“Reducing Impact of Anti-Virus Scanning” on page 14
“License Tracking and Auditing” on page 14
“ArcSight System Tasks” on page 14

1 Basic Administration Tasks
./arcsight manager
When it starts, the ArcSight Manager displays a stream of messages in the command
window or terminal box to reflect its status. The command window displays the word
“Ready” when the Manager has started successfully. If you are starting the Manager as a
service, you can monitor whether or not it has successfully loaded by viewing the
server.std.log file, located in <ARCSIGHT_HOME>logsdefault on Windows. On
Unix systems, you can use the command:
cd ARCSIGHT_HOME;tail -f logs/default/server.std.logOn Windows systems, you can use a
“tail” equivalent tool to run the same command, such as those available from
http://www.cygwin.com, which provides Unix environments and tools for Windows.
ArcSight Manager Decoupled Process Execution
On UNIX-based systems, ArcSight Manager uses decoupled process execution to perform
specific tasks, for example to compile rulesets, either on initial startup or when the
real-time rules group changes. To do so, ArcSight Manager uses a standalone process
executor (instead of using “in process” or “direct process” execution). ArcSight Manager
sends commands to be executed via the file system. The process executor uses the
<ARCSIGHT_HOME>/tmp directory, so you should restrict system level access for this
directory.
The process executor is used, by default, on all Unix platforms. The ArcSight Manager
scripts ensure that the Process Executor runs as a daemon before the ArcSight Manager is
started. This has some implications with regards to troubleshooting ArcSight Manager
startup and runtime problems. The ArcSight Manager, if configured to use the Process
Executor, does not start unless it detects the presence of a running Process Executor. The
Process Executor runs within its own watchdog, in the same fashion as the ArcSight
Manager, so if the process stops for any reason, it restarts automatically. The process
executor is transparent to users regarding the way that ArcSight Manager is started or
stopped.
The stdout and stderr of the executed process are written into the following two files:
<ARCSIGHT_HOME>/tmp/[commandfile-name].stdout
<ARCSIGHT_HOME>/tmp/[commandfile-name].stderr
Starting the ArcSight Console
Before you start ArcSight Console or SmartConnectors, be sure ArcSight Manager is
installed and has completed a successful startup. To start up the ArcSight Console:
1 Open a command window or shell window on <ARCSIGHT_HOME>/bin.
2 Type in the following line and press Enter.
./arcsight console
Closing the command prompt or terminal box in which ArcSight Manager was
started, or pressing CTRL-C keys in the window, initiates a controlled and
graceful shut down of the ArcSight Manager.

Setting up a Custom Login Message
You can configure the ArcSight Manager to display a custom message before allowing users
to log in to the Console or ArcSight Web. Set the following property in
server.properties:
auth.login.banner=config/loginbanner.txt
This property configures the Manager to display the text from the file
<ARCSIGHT_HOME>/config/loginbanner.txt whenever a user runs the Console.
(Changes to the properties file take effect the next time the Manager is started.)
Create a text file named loginbanner.txt in the <ARCSIGHT_HOME>/config
directory. This feature is often used to display a legal disclaimer message. Users must close
the message window before they can log in.
The ArcSight Web console displays the custom banner as well, provided that the browser
used supports JavaScript and has JavaScript enabled. To configure a custom banner for
Web Console:
1 Create a custom logo image in .gif or .png format (such as MyLogo.gif). The image
should be approximately 138 x 39 pixels.
2 On the Web server machine, copy this custom logo image file to the
<ARCSIGHT_HOME>/webapp/images directory.
3 Copy the following properties from the example.styles.properties file located
at <ARCSIGHT_HOME>/config/web directory to styles.properties file in the
same directory. Create a styles.properties file from the example file, if one does
not already exist.
# logo image for login page
loginLogoImg = <demo-logo-login.png>
4 Replace 'demo-logo-login.png' with your custom logo image file name. For example,
loginLogoImg=MyLogo.gif
5 Close the Web Console.
6 Restart Web server and log into the Web console.
You should see this newly added custom Web logo image in Web console Login
Window.
Starting ArcSight SmartConnectors
Before you start ArcSight SmartConnectors, make sure ArcSight Manager is running. It’s
also a good idea for the ArcSight Console to also be running, so that you can see the status
of the configured SmartConnectors and view messages as they appear on the Console. To
start up an ArcSight SmartConnector:
1 Open a command window or terminal box.
2 Type in the following line and press Enter:
When you uninstall the Web, style.properties and your custom logo
image files are deleted. Make sure to save these files so that you can
use them when you reinstall the Web

./arcsight agents
Stopping the ArcSight Manager
When not running as a service, press Ctrl-C in the command window or terminal box
where the ArcSight Manager is running to initiate a controlled shutdown of ArcSight
Manager.
Reconnecting to the ArcSight Manager
If the ArcSight Console loses its connection to the ArcSight Manager—because the Manager
was restarted, for example—a dialog box appears in the ArcSight Console stating that your
connection to the ArcSight Manager has been lost. Click Retry to re-establish a connection
to the ArcSight Manager or click Relogin.
Configuring ArcSight Manager or ArcSight Web as a
Service
The ArcSight Manager (or ArcSight Web) can be configured as a Windows Service or Unix
daemon. When you start the ArcSight Manager as a service (or daemon) you can monitor
whether or not it has successfully started by viewing the server.std.log file located in
<ARCSIGHT_HOME>/logs/default.
ArcSight Manager Service Setup on Windows
If the ArcSight Manager was not originally configured as a service, you can do so at any
time using the Manager service tool, managersvc. To set up ArcSight Manager as a service
in Windows:
From a command window in the <ARCSIGHT_HOME>bin directory, enter the following
command:
arcsight managersvc –i
On a 64-bit machine enter:
arcsight managersvc64 -i
Starting and Stopping the ArcSight Manager Service on
Windows
To start or stop the ArcSight Manager service:
1 Right-click the My Computer icon, and select Manage. The Computer Management
window appears.
Closing the command prompt or terminal box shuts down the ArcSight
Manager.
The connection to the ArcSight Manager cannot be re-established while the
ArcSight Manager is restarting. In some cases, a connection cannot be
established without resetting one or both machines.
Clicking Retry may display connection exceptions while the ArcSight Manager
is restarting, or as the connection is re-established.

2 Within the Computer Management window, expand the Services and Applications
folder.
3 Click Services.
4 Right-click the ArcSight Manager service name and select Start to begin the service
or Stop to end the service
Removing the ArcSight Manager Service on Windows
Stopping the ArcSight Manager service does not remove it from your system. To remove
the service you must do the following:
Within a Windows command prompt, type in the following command from the
<ARCSIGHT_HOME>bin directory:
arcsight managersvc –r
On 64-bit machine enter:
arcsight managersvc64 -r
Check to ensure that the service was removed. If it was not, reboot the Windows system to
completely remove the service.
Doing an uninstall should automatically remove the service too. For the Manager service to
start automatically at system boot the option for it must be selected in the Manager setup.
ArcSight Manager or ArcSight Web Service Setup on Unix
Platforms
The following provides a brief overview of how to set up ArcSight Manager or ArcSight Web
as a daemon, the “service” equivalent on Unix platform machines. After installation,
ArcSight Manager can be controlled using /etc/init.d/arcsight_manager
start|stop, (or arcsight_web for ArcSight Web) following the standard method of
starting daemon services in Unix. Change the configuration file
/etc/arcsight/arcsight_manager.conf (or arcsight_web.conf for ArcSight
Web) to reflect the installation directory and other settings. In addition, the
/etc/init.d/arcsight_* scripts are hooked into the Unix startup procedure, making
the ArcSight Manager or Web start and shut down in lock step with the host OS.
To set up ArcSight Manager or ArcSight Web as a Unix daemon, open a terminal box on
<ARCSIGHT_HOME>/bin and run the appropriate wizard:
./arcsight managersetup
./arcsight websetup
Once everything is configured properly, test your configuration setup the next time you
start the ArcSight Manager using /etc/init.d/arcsight_manager (or
arcsight_web).

Make sure to start ArcSight Manager this way at least once before relying on it to start
correctly during system boot or startup.
Reducing Impact of Anti-Virus Scanning
Files in certain directories are updated frequently; for example, the log directory. When an
anti-virus application monitors these directories, it can impact the system in these ways:
 Place a large and constant load on the CPU of the machine.
 Slow down ESM as frequent scanning can impede writes to disk.
Therefore, we recommend that you exclude the following directories (and any
subdirectories under them) in <ARCSIGHT_HOME> from the virus scan list:
 caches/server
 logs
 system
 tmp
 user, but include the user/agent/lib directory in the scan
 archive
License Tracking and Auditing
ESM automatically maintains a license audit history that allows you to see how many
licenses are in use. When users log into the Console they receive a warning notifying them
if they have exceeded their current license. ESM creates an internal audit event for each
licensable component to help users track which areas have been exceeded. There are
licensing reports on individual features. These reports are located in /All Reports/ArcSight
Administration/ESM/Licensing/. The reports provide a summary for the number of Actors,
Assets, Users, Devices, and EPS identified over the last week.
ArcSight System Tasks
These system tasks are scheduled to run automatically one or more times per day,
depending on the task. You can control some of these schedules indirectly, for example by
changing the retention period.
AUP Updater: This task runs in the manager and pushes to connectors any updated AUP
packages it might have.
Dependent Resource Validator: This task runs validations on resources in the system
and disables the ones that have problems.
Event Partition Statistics Updator: This task updates statistics on the partitioned event
tables, acting on today's partition.
Partition Archiver: This task archives event partitions based on your retention policy.
The script output goes to
<ARCSIGHT_HOME>/logs/default/server.script.log. The stdout output of
the ArcSight Manager goes to
<ARCSIGHT_HOME>/logs/default/server.std.log. ArcSight recommends
that you tail these two files to identify the cause of any startup failures.

Partition Compressor: This task compresses event partitions based on your retention
policy.
Partition Manager: This task creates/drops partitions based on your retention policy.
For information on the partition-related tasks refer to the “Configuring Partition
Management” topic in the “Installing ArcSight Database” chapter of the ESM Installation
and Configuration Guide.
PurgeStaleMarkSimilarConfigs: This task does maintenance work on the 'mark similar'
annotation criteria, removing the ones that are stale.
Resource Search Index Updater: This task updates the resource search index.
Sortable Fields Updater: This task keeps sortable event fields in sync, based on the
current indices in the database.
Table Stats Updator: This task updates statistics on the non-partitioned schema tables,
which includes the resource tables.

Chapter 2
Configuration
This chapter describes the various tasks that you can perform to manage the component
configuration. The following topics are covered in this chapter:
Managing and Changing Properties File Settings
Various components of ESM use properties files for configuration. Many sections of this
documentation require you to change properties in those files. Some of the properties files
are also modified when you use one of the configuration wizards that come with ESM.
Property File Format
Generally, all properties files are text files containing pairs of keys and values. The keys
determine which setting is configured and the value determines the configuration value.
For example, the following property configures the port on which ArcSight Manager listens:
servletcontainer.jetty311.encrypted.port=8443
Blank lines in this file are ignored as well as lines that start with a pound sign ( # ). Lines
that start with a pound sign are used for comments.
“Managing and Changing Properties File Settings” on page 17
“Adjusting Console Memory” on page 23
“Adjusting Pattern Discovery Memory” on page 23
“Installing New License Files Obtained from ArcSight” on page 23
“Configuring ArcSight Manager Logging” on page 24
“Understanding SSL Authentication” on page 33
“Reconfiguring the ArcSight Console after Installation” on page 74
“Reconfiguring ArcSight Manager” on page 74
“Manager Password Configuration” on page 75
“Compression and Turbo Modes” on page 82
“Configuring the ArcSight Database Monitor” on page 84
“Sending Events as SNMP Traps” on page 85
“Asset Aging” on page 86
“Configuring Actors” on page 88

2 Configuration
Defaults and User Properties
Most configuration items in various components consist of at least two files. The first,
generally referred to as the defaults properties file, contains the default settings that ESM
provides. These files should never be modified, but can be used as a reference. Updates to
the components overwrite this file to include new settings.
The second file, generally referred to as the user properties file, contains settings that are
specific to a particular installation. Settings in the user properties file override settings in
the defaults properties file. Typically, the user properties file for a component is created
and modified automatically when you configure the component using its configuration
wizard. Because the user properties file contains settings you specify to suit your
environment, it is never replaced by an upgrade.
The following table lists the most important properties files.
Editing Properties
When you edit a *.properties file, first look for the *.defaults.properties file.
Copy the property you want to edit from *.defaults.properties to *.properties
and change the setting to your new value in *.properties. When the same property is
defined differently in each file, the system uses the value in *.properties. This ensures
that when you install an upgrade, and the *.defaults.properties file is updated, the
properties you customized are retained unchanged in *.properties.
You can edit the properties using a regular text editor, for example vi or emacs on Unix
platforms or MS Notepad on Windows.
If you configured the Console and SmartConnectors using default settings in the
configuration wizard, a user properties file is not created automatically for that component.
If you need to override a setting on such a component, use a text editor to create this file
in the directory specified in the above table.
When you edit a property on a component, you must restart the component for the new
values to take effect except for the Manager properties listed in the next section.
If you change a communication port, be sure to change both sides of the connection. For
example, if you configure a Manager to listen to a different port than 8443, be sure to
Default Properties User Properties Purpose
config/
server.defaults.properties
config/server.properties ArcSight Manager
Configuration
config/
console.defaults.properties
config/console.properties ArcSight Console
Configuration
config/
client.defaults.properties
config/client.properties ArcSight Common Client
Config
config/agent/
agent.defaults.properties
user/agent/agent.properties SmartConnector
Configuration

2 Configuration
configure all the Manager’s clients (Consoles, SmartConnectors, ArcSight Web, and so on)
to use the new port as well.
Dynamic Properties
When you change the following properties in the server.properties file on the
Manager, you do not need to restart the Manager for the changes to take effect:
 auth.auto.reenable.time
 auth.enforce.single.sessions.console
 auth.enforce.single.sessions.web
 auth.failed.max
 auth.password.age
 auth.password.age.exclude
 auth.password.different.min
 auth.password.length.max
 auth.password.length.min
 auth.password.letters.max
 auth.password.letters.min
 auth.password.maxconsecutive
 auth.password.maxoldsubstring
 auth.password.numbers.max
Protocol Port Configuration
TCP 8443 ArcSight Console to ArcSight Manager communication
TCP 8443 ArcSight SmartConnector to ArcSight Manager
communication
TCP 9443 ArcSight Web
9090 ESM Service Layer Container Port
TCP 1521 ArcSight Manager to ArcSight Database (Oracle
communication
TCP 389 ArcSight Manager to LDAP server (w/o SSL if enabled)*
TCP 636 ArcSight Manager to LDAP server (w/ SSL if enabled)*
TCP 25 ArcSight Manager to SMTP server (for Notifications)
TCP 110 ArcSight Manager to POP3 server (for Notifications)
TCP 143 ArcSight Manager to IMAP server (for Notifications)
UDP 1645 or 1812 ArcSight Manager to RADIUS server (if enabled)
UDP/TCP 53 ArcSight Console to DNS Server communication
(nslookup tool)
UDP/TCP 43 ArcSight Console to Whois Server communication (whois
tool)
ICMP none ArcSight Console to Target communication (ping tool)

2 Configuration
 auth.password.numbers.min
 auth.password.others.max
 auth.password.others.min
 auth.password.regex.match
 auth.password.regex.reject
 auth.password.unique
 auth.password.userid.allowed
 auth.password.whitespace.max
 auth.password.whitespace.min
 external.export.interval
 process.execute.direct
 servletcontainer.jetty311.log
 servletcontainer.jetty311.socket.https.expirationwarn.days
 ssl.debug
 web.accept.ips
 whine.notify.emails
 xmlrpc.accept.ips
After you make the change, you use the manager-reload-config command to load
those changes to the Manager. Every time the manager-reload-config command is
successful, a copy of the server.properties file it loaded is placed in
<ARCSIGHT_HOME>/config/history for backup purposes. The server.properties
file in <ARCSIGHT_HOME>/config/history is suffixed with a timestamp and does not
overwrite the existing versions, as described in the following example.
Example
Manager M1 starts successfully for the first time on September 27, 2010, at 2:45 p.m. A
backup copy of its server.properties file is written to
<ARCSIGHT_HOME>/config/history with this timestamp:
server.properties.2010_09_27_14_45_27_718
On September 28, 2010, the M1 administrator adds the following property to the
server.properties file:
notification.aggregation.max_notifications=150
When the administrator runs the manager-reload-config command at 1:05 p.m. the
same day, it runs successfully because this property can be loaded dynamically.
As soon as the updated server.properties file is loaded in M1’s memory, a backup
copy of the updated server.properties file is written to
<ARCSIGHT_HOME>/config/history with appropriate timestamp.
Now, <ARCSIGHT_HOME>/config/history contains these two backup files:
On September 29, 2010, the M1 administrator adds this property to the

2 Configuration
notification.aggregation.time_window=2d
As this property can be also loaded dynamically, similar to the previous change, once the
updated server.properties is loaded in M1’s memory, a backup copy of the
server.properties file is written to <ARCSIGHT_HOME>/config/history with
appropriate timestamp.
Now, <ARCSIGHT_HOME>/config/history contains these three backup files:
On September 30, 2010, the M1 administrator updates the whine.notify.emails
property in the server.properties file. When he runs the manager-reload-config
command, the command fails because this property cannot be loaded dynamically. As a
result, these things happen:
 The updated server.properties file is not loaded into M1’s memory, however,
changes made to it are not reverted.
 M1 continues to use the properties that were loaded on September 29th.
 No backup copy is made. The <ARCSIGHT_HOME>/config/history directory
continues to contain the same three backup files:
The changes made on September 30th are not effective until M1 is restarted.
Changing Manager Properties Dynamically
To change any of the properties listed previously, do these steps:
1 Change the property in the server.properties file and save the file.
2 (Optional) Use the –diff option of the manager-reload-config command to
view the difference between the server properties the Manager is currently using and
the properties loaded after you run this command:
arcsight manager-reload-config –diff
3 Run this command in <ARCSIGHT_HOME>/bin to load the new values for the
properties you changed:
arcsight manager-reload-config
If this command fails with a warning, it indicates that you are changing properties that
require a Manager restart before those changes can take effect. When you get such a
warning none of the property changes, including the ones that can be reloaded without
restarting the Manager, are applied. You can do one of the following in this situation:
The -diff option compares all server properties—default and user
properties. For all options available with the manager-reload-config
command, see Appendix A‚ ArcSight Commands‚ on page 101.

2 Configuration
 Revert changes to properties that cannot be loaded without restarting the Manager
and rerun the arcsight manager-reload-config command.
 Force an update of all properties using the –as option, as follows:
arcsight manager-reload-config -as
When you use the -as option, the properties that can be changed without restarting the
Manager take effect immediately. The properties that require a Manager restart are
updated in the server.properties but are not effective until the Manager is restarted.
For example, if you change auth.password.length.min to 7 and search.enabled to
false, you get the above warning because only auth.password.length.min can be
updated without restarting the Manager. If you force an update of the server.properties file,
auth.password.length.min is set to 7, but search.enabled continues to be set to true
until the Manager is restarted.
Changing the Service Layer Container Port
By default the service layer container port is 9090. You can change this port:
1 Modifying the following files located in the Manager’s <ARCSIGHT_HOME>:
 /arcsight-dm
/plugins/com.arcsight.dm.plugins.tomcatServer_1.0.0/conf/ser
ver.xml.
 /config/proxy.rule.xml
 /config/rewriteProxy.rule.xml
Make sure to replace the references to port 9090 with an unused port number.
2 Restart the Manager.
Securing the ArcSight Manager Properties File
The ArcSight Manager’s server.properties file contains sensitive information such as
database passwords, keystore passwords, and so on. Someone accessing the information
in this file can do a number of things, such as tampering with the database and acting as a
pseudo ArcSight Manager. As a result, the server.properties file must be protected so
that only the user account under which the ArcSight Manager is running is able to read it.
This can be accomplished by issuing a chmod command in Unix and Linux, for example:
chmod 600 server.properties
This operation is performed during the ArcSight Manager installation. As a result, only the
owner of the file (which must be the user that runs the ArcSight Manager) may read or
write to the file. For all other users, access to the file is denied.
Be careful in using the –as option to force reload properties. If an invalid
static change is made, it may prevent the Manager from starting up once it
reboots.
You can also protect the server.properties file on Windows systems with
an NTFS file system using Microsoft Windows Access Control Lists (ACLs).

2 Configuration
Adjusting Console Memory
Because the ArcSight Console can open up to ten independent event-viewing channels,
out-of-memory errors may occur. If such errors occur, or if you simply anticipate using
numerous channels for operations or analysis, please make the following change to each
affected Console installation.
In the bin/scripts directory, in the console.bat (Windows) or console.sh (Unix)
configuration files, edit the memory usage range for the Java Virtual Machine.
Adjusting Pattern Discovery Memory
By default, Pattern Discovery limits its memory usage to about 4 GB of memory. However,
if the search for patterns involves too many transactions and events, the task can run out
of memory and abort. You can control the memory limit indirectly by changing the
maximum number of transactions and events the Pattern Discovery task can hold in
memory. The settings for these values are in the server.defaults.properties file in
the config folder.
 patterns.transactionbase.max — The maximum number of transactions
allowed in memory. If you exceed this number, these transactions are stored as page
file. The default is 10000.
 patterns.maxSupporterCost — The maximum number of supporters allowed in
memory. If you exceed this number, the pattern discovery task aborts. The default is
80000.
 patterns.maxUniqueEvents — The maximum number of unique events allowed
in memory. If you exceed this number, the pattern discovery task aborts. The default is
20000.
If the pattern discovery task aborts, a message to that effect appears in the console. Run
the pattern discovery task again after increasing the pattern discovery memory usage
limits. You can increase the memory usage limit by increasing the three values
proportionally. For example, to add 25 percent more memory capacity, you would change
the values to:
 patterns.transactionbase.max=12500
 patterns.maxSupporterCost=100000
 patterns.maxUniqueEvents=25000
You can edit the properties file using a regular text editor. After changing any of these
values, restart the manager for them to take effect.
Installing New License Files Obtained from ArcSight
To change the license file you obtained from ArcSight, please follow the steps below:
1 On the system where ArcSight Manager is installed, copy the package (.zip file) to
the <ARCSIGHT_HOME> directory (the directory that contains the ArcSight Manager
installation).
2 Run the following command from the Manager’s /bin directory:
You receive new license files packaged as .zip files and sent via e-mail from
ArcSight.

2 Configuration
./arcsight deploylicense
This wizard replaces the license currently installed with the one included in the file. The
Manager detects the new license automatically.
Installing in Silent Mode
To install the license file in silent mode, you are required to create a properties file and use
it. To do so:
1 Open a command prompt/shell window.
2 From the Manager’s bin directory, run the following command to open the sample
properties file:
./arcsight deploylicense -g
3 Copy and paste the text generated by the command above into a text file.
4 Set the following properties:
LicenseChoice=1
LicenseFile.filename=<name_of_the_license_zip_file>
replaceLicenseQuestion =yes
5 Save this text file as properties.txt in the Manager’s <ARCSIGHT_HOME>.
6 From the Manager’s bin directory, run:
./arcsight deploylicense -f properties.txt -i silent
Configuring ArcSight Manager Logging
ArcSight Manager outputs various types of information to log files. By default, the logs are
located in:
<ARCSIGHT_HOME>/logs/default/
Various ArcSight Manager utilities write logging information to different sets of log files.
Each of those sets can consist of multiple files.
The number and size of the log files are configurable, a typical setting is 10 files with 10
megabytes each. When a log file reaches a maximum size, it is copied over to a different
location. Depending on your system load, you may have to change the default settings. To
make changes to the logging configuration, change the log channel parameters. The
default log channel is called file.
For the main ArcSight Manager log file, called server.log, the following
server.properties settings are used:
# Maximum size of a log file.
log.channel.file.property.maxsize=10MB
# Maximum number of roll over files.
log.channel.file.property.maxbackupindex=10

2 Configuration
The first setting affects the size of each individual log file; the second setting affects the
number of log files created. The log file currently in use is always the log file with no
number appended to the name. The log file with the largest number in its extension is
always the oldest log file. All of the log files are written to the
<ARCSIGHT_HOME>/logs/default directory.
ArcSight Manager and its related tools write the following log files:
Sending logs and diagnostics to HP Support
Customer Support may request log files and other diagnostic information to troubleshoot
problems. The Send Logs utility automatically locates the log files and compresses them.
You can send the compressed files to Customer Support.
 You can run this utility as a wizard directly from the Console interface (GUI) in addition
to the command-line interface of each component.
 Optionally, gather diagnostic information such as session wait times, thread dumps,
and database alert logs about your ArcSight system, which helps Customer Support
analyze performance issues on your ArcSight components.
 When you run this utility from the Console, Manager, or Web, you can gather logs and
diagnostic information for all components of the system.
Guidelines for using the Send Logs utility
Keep these guidelines in mind when using the Send Logs utility:
 You can be connected as any valid user on an ArcSight component to collect its local
logs; however, you must have administrator access to collect logs from other
components. For example, if you are connected as user ‘joe’ to the Console, you can
Log File Description
server.log* The main ArcSight Manager log.
server.status.log* System status information, such as memory usage etc.
server.channel.log* Active Channel logs.
server.std.log* All output that ArcSight Manager prints on the console (if
run in command line mode)
server.pulse.log* ArcSight Manager writes a line to this set of logs every ten
seconds. Used to detect service interruptions.
server.sql.log* If database tracing is enabled, the SQL statements are
written to this set of log files.
execproc.log* Log information about externally executed processes (only
on some platforms)
serverwizard.log* Logging information from the arcsight managersetup
utility.
archive.log* Logging information from the arcsight archive utility.
You can also use the arcdt command to run specific diagnostic utilities
from the Manager command line. For more information, see Appendix A‚
ArcSight Commands‚ on page 101.

2 Configuration
collect its logs. But if you need to collect logs for the Manager and the database, you
must connect to the Console as the ArcSight administrator.
 SmartConnectors must be running version 4037 or later to remotely (using a Console
or the Manager) collect logs from them.
 You can only collect local logs on SmartConnectors or ArcSight Database. That is, if
you run the Send Logs utility on ArcSight Database, only the database log files are
gathered.
 You can run the Send Logs utility on a component that is down. That is, if the ArcSight
Database is down, you can still collect its logs using this utility.
If the Manager is down, you can only collect its local logs. However, if you need to
collect the database logs as well, use the arcdt command on the Manager. For more
information, see Appendix A‚ ArcSight Commands‚ on page 101.
 All log files for a component are gathered and compressed. That is, you cannot select
a subset of log files that the utility should process.
 The Send Logs utility generates a compressed file on your local system that you can
send to Customer Support by e-mail, if they request it.
 You can review the compressed file to ensure that only a desired and appropriate
amount of information is sent to support.
 You can remove or sanitize information such as IP addresses, host names, and e-mail
addresses from the log files before compressing them. The options are:
 Send log as generated
This option, the default, does not remove any information from the logs files.
 Only remove IP address
This option removes IP addresses, but not host names or e-mail addresses, from
the logs files.
 Remove IP address, host names, e-mail addresses
This option removes all IP addresses and enables you to specify a list of host-
name suffixes for which all host names and e-mail addresses are removed from
the logs.
For example, if you specify ‘company.com’ as a host-name suffix to remove, the
Send Logs utility removes all references to domains such as ‘www.company.com’
and e-mail addresses such as ‘john@company.com’ from the logs.
Gathering logs and diagnostic information
When you run the Send Logs utility on ArcSight SmartConnectors or ArcSight database, it
gathers logs and diagnostic information (if applicable) for only those components.
However, when you run this utility on ArcSight Console, Manager, or ArcSight Web, you can
gather logs and diagnostic information for all or a selected set of ArcSight components.
To run this utility on SmartConnectors, enter this in <ARCSIGHT_HOME>/bin:
./arcsight agent sendlogs
To gather logs and diagnostic information for all or a selected set of components, do one of
the following:
 On the ArcSight Console, click Tools | SendLogs.
 Enter this command in <ARCSIGHT_HOME>/bin on Console, Manager, or Web:
./arcsight sendlogs

2 Configuration
The above action starts the Send Logs wizard. In the wizard screens, perform these steps:
1 Decide whether you want the wizard to gather logs only from the component on which
you are running it or from all components.
If you select Use current settings to gather logs. logs for all components are
gathered thus: If this is the first sendlogs is run after installation, then all the logs are
gathered. If this is not the first sendlogs is run, then it uses the same setting as the
previous run.
a Enter the Manager’s login information.
b Go to Step 2 on page 30.
If you selected Change/Review settings before gathering logs., you get the
option to select the components for which you want logs gathered.
Select whether you want only the local (the component from where you ran the Send
Logs utility) logs selected or you want logs from other components collected too.
The Send Logs wizard remembers most of the choices you make when you
run it for the first time. Therefore, for subsequent runs, if you choose to use
the previous settings, you do not need to re-enter them.

2 Configuration
Local logs only:
If you selected Local logs only, you are prompted to either choose a time range or
include all time ranges.
If you selected Include all time ranges, go to Step 2 on page 30.
If you selected Choose a specific time range, you are prompted to enter a start
time and end time - a time range for which the wizard gathers the logs.
Go to Step 2 on page 30.
Logs from other components (Requires Manager credentials):
If you select Logs from other components (Requires Manager credentials),
you are prompted to choose the components.

2 Configuration
a Select the components and the time range for which you want to gather logs. In
addition, select whether you want to run the diagnostic utilities to gather
additional information for those components.
If you choose to specify the diagnostic utilities to run, you are prompted to select
the utilities from a list in a later screen. The diagnostic utilities you can select are
described in Appendix A‚ arcdt‚ on page 105.
b If you chose to gather logs from the SmartConnectors, select those
SmartConnectors in the next screen.
At a minimum, the SmartConnectors should be running version 4037 or
later.

2 Configuration
c If you chose to select the diagnostic utilities you want to run earlier in this wizard,
select them in the next screen.
d Go to Step 2 on page 30.
2 Select whether you want to sanitize the logs before sending. For more information
about sanitizing options, see “Guidelines for using the Send Logs utility” on page 25.
If you choose Keep Log sanitization settings, go to Step 3 on page 32.

2 Configuration
If you choose Change/Review Logs sanitization settings, you are prompted to
select what you want to sanitize.
If you chose one of the first two options, go to Step 3 on page 32.
If you selected Remove IP addresses, host names, and e-mail addresses
(Slower), you are prompted to enter what you want removed. Click Add to add a
suffix to remove. Highlight an entry and click Remove to remove it from the list.

2 Configuration
3 Enter the Customer Support incident number.
The Send Logs utility uses this number to name the compressed file it creates. Use the
incident number that Customer Support gave you when you reported the issue for
which you are sending the logs. Doing so helps Customer Support relate the
compressed file to your incident.
In case you do not have an incident number at this time, you can continue by entering
a meaningful name for the compressed file to be created. Once you obtain the incident
number from Customer Support, you can rename the file with the incident number you
received.
4 Click Next to start the compression.
Most of the values you entered during the first run of the Send Logs
wizard are retained. The next time you run this wizard, you need to enter
only a few settings.

2 Configuration
5 Click Finish in the last screen.
Understanding SSL Authentication
Secure Socket Layer (SSL) technology is used for communication between ArcSight
Manager and its clients—Console, SmartConnectors, and ArcSight Web. SSL is also used
between ArcSight Web and the web browsers that communicate with it.
SSL enables the Manager (referred to as a “server”) to authenticate to its clients and
communicate information over an encrypted channel, thus providing the following benefits:
 Authentication—Ensuring that clients send information to an authentic server and not
to a machine pretending to be that server.
 Encryption—Encrypting information sent between the clients and the server.
 Data Integrity—Hashing information to prevent intentional or accidental modification.
By default, clients submit a valid user name and password to authenticate with the server;
however, these clients can be configured to use SSL client authentication.
Note that SSL is not used between ArcSight Manager and the ArcSight Database.

2 Configuration
Terminology
These terms are used in describing and configuring SSL:
 Certificate
A certificate contains the public key, identifying information about the machine such as
machine name, and the authority that signs the certificate. SSL certificates are defined
in the ISO X.509 standard.
 Key pair
A key pair is a combination of a private key and the public key that encrypts and
decrypts information. A machine shares only its public key with other machines; the
private key is never shared. The public and private keys are used to set up an SSL
session. For details, see “How SSL Works” on page 43.
 SSL server-SSL client
An SSL session is set up between two machines—a server and a client. Typically, a
server must authenticate to its clients before they send any data. However, in client-
side SSL authentication, the server and its clients authenticate each other before
communicating.
ArcSight Manager is an SSL server, while SmartConnectors, Console, and browsers are
SSL clients. ArcSight Web is an SSL client to the Manager and an SSL server to the web
browsers that connect to it.
 keystore
A keystore is an encrypted repository on the SSL server that holds the SSL certificate
and the server’s private key. The following table lists the ArcSight component, the
name of the keystore on that component, and its location.
[1] When client-side authentication is used, a keystore exists on both the server and
the client.
[2] Make sure you do not change the keystore file name.
The keytoolgui utility, used to perform a number of SSL configuration
tasks, refers to a combination of an SSL certificate and private key as the
key pair.
The keytoolgui utility is discussed in “Tools for SSL Configuration” on
page 38.
Log File
keystore File
Name[2]
Location of keystore
Manager keystore <ARCSIGHT_HOME>/config/jetty
ArcSight Web webkeystore <ARCSIGHT_HOME>/config/jetty
Clients[1] (for
client-side
authentication)
keystore.client <ARCSIGHT_HOME>/config

2 Configuration
 truststore
truststore is an encrypted repository on SSL clients that contains a list of certificates of
the issuers that a client trusts.
When an issuer issues a certificate to the server, it signs the certificate with its private
key. When the server presents this certificate to the client, the client uses the issuer’s
public key from the certificate in its truststore to verify the signature. If the signature
matches, the client accepts the certificate. For more details, see how SSL handshake
occurs in “How SSL Works” on page 43.
The following table lists the ArcSight component, the name of the truststore on that
component, and its location.
[1] The utilities that exist on the Manager machine such as archive are treated as
clients of the Manager. The cacerts file on the Manager is used for authenticating the
Manager to these clients.
[2] When client-side authentication is used.
[3] When client-side authentication is used, ArcSight Web contains two truststores—
cacerts for connections to the Manager and webtruststore for connections to browsers.
The keytoolgui utility, used to view a truststore, is discussed in “Tools
for SSL Configuration” on page 38.
Component truststore File Name Location of truststore
Clients cacerts <ARCSIGHT_HOME>/jre/lib/security
Manager cacerts[1] <ARCSIGHT_HOME>/jre/lib/security
ArcSight Web cacerts <ARCSIGHT_HOME>/jre/lib/security
Manager truststore[2] <ARCSIGHT_HOME>/config/jetty
ArcSight Web webtruststore[2][3] <ARCSIGHT_HOME>/config/jetty

2 Configuration
 Alias
Certificates and key pairs in a keystore or a truststore are identified by an alias.
 truststore password
The *.defaults.properties file contains the default truststore password for each
ArcSight component. The password is in clear text and typically, you do not need to
change it. To change or obfuscate it, use the changepassword utility, as described in
Appendix A‚ ArcSight Commands‚ on page 101. The following table lists the property
name where the obfuscated truststore passwords are stored.
*For client-side authentication
** If config/client.properties or user/agent/agent.properties does
not exist, create it using an editor of your choice.
 keystore password
Use a keystore password to encrypt the keystore file and use a truststore password to
encrypt a truststore file. Without this password, you cannot open these files.
You specify a keystore password when creating a key pair, which is discussed in later
sections of this chapter. The password is obfuscated and stored in the ArcSight
component’s *.properties file. The following table lists the property file and the
property name where the keystore password is stored for each component. The
Truststore Property File Property Name
Client client.properties** ssl.truststore.password
Manager* server.properties servletcontainer.jetty311.truststore
.password.encrypted
ArcSight Web webserver.properties servletcontainer.jetty311.truststore
.password.encrypted
Connector agent.properties** ssl.truststore.password

2 Configuration
following table lists the property name where the obfuscated keystore passwords are
stored.
*For client-side authentication
** If config/client.properties or user/agent/agent.properties does
not exist, create it using an editor of your choice.
 Cipher suite
A set of authentication, encryption, and data integrity algorithms used for securely
exchanging data between an SSL server and a client.
The following cipher suites are enabled by default:
 TLS_RSA_WITH_AES_128_CBC_SHA
 SSL_RSA_WITH_3DES_EDE_CBC_SHA
 SSL_RSA_WITH_RC4_128_MD5
 SSL_RSA_WITH_RC4_128_SHA
Other supported cipher suites are:
 TLS_DHE_RSA_WITH_AES_128_CBC_SHA
 TLS_DHE_DSS_WITH_AES_128_CBC_SHA
 SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA
 SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA
 SSL_RSA_WITH_DES_CBC_SHA
 SSL_DHE_RSA_WITH_DES_CBC_SHA
 SSL_DHE_DSS_WITH_DES_CBC_SHA
 SSL_RSA_EXPORT_WITH_RC4_40_MD5
 SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
 SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
 SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
 SSL_RSA_WITH_NULL_MD5
 SSL_RSA_WITH_NULL_SHA
 SSL_DH_anon_WITH_RC4_128_MD5
 TLS_DH_anon_WITH_AES_128_CBC_SHA
 SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
 SSL_DH_anon_WITH_DES_CBC_SHA
 SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
 SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
Keystore Property File Property Name
Client* client.properties** ssl.keystore.password.encrypted
Manager server.properties server.privatekey.password.encrypted
ArcSight Web webserver.properties server.privatekey.password.encrypted
Connector agent.properties** ssl.keystore.password.encrypted

2 Configuration
Although in most cases you do not need to change cipher suites, you can configure
them in the properties file for an ArcSight component:
 Manager—config/server.properties
 Arcsight Web—config/webserver.properties
 Clients—config/client.properties
 Connectors—user/agent/agent.properties
Cipher suites are set as a comma-delimited list in the ssl.cipher.suites property.
During the SSL handshake, the client provides this list as the cipher suites that it can
accept, in descending order of preference. The server compares the list with its own
set of acceptable cipher suites, picks one to use based on its order of preference, and
communicates it to the client.
Tools for SSL Configuration
Keytoolgui
The keytoolgui utility enables you to perform a number of SSL configuration tasks on
Windows. Some of these tasks are:
 Creating a new keystore
 Creating a new key pair
 Creating a request for a CA-signed certificate (.csr file)
 Exporting and Importing a key pair
 Exporting and Importing a certificate
The keytoolgui utility is available on all components and is located in the
<ARCSIGHT_HOME>/bin/scripts directory of the component.
To run keytoolgui, run this command in <ARCSIGHT_HOME>/bin:
./arcsight keytoolgui
On SmartConnectors, use:
./arcsight agent keytoolgui
Using Keytoolgui to Export a Key Pair
1 To start it, run the following from the Manager’s bin directory:
2 Click File->Open keystore and navigate to the component’s keystore.
3 Enter the password for the keystore when prompted. The default password is
“changeit” (without quotes).
Not all ESM versions or ArcSight Express models support the FIPS mode.
PKCS#11 token support may not be available for all ESM versions and ArcSight
Express models.
Be sure to have X11 enabled on UNIX to run this tool.

2 Configuration
4 Right-click the key pair and select Export.
5 Select Private Key and Certificates radio button and click OK.
6 Enter the password for the key pair when prompted. The default password is
“changeit” (without quotes).
7 Enter a new password for the exported key pair file, then confirm it and click OK.
8 Navigate to the location on your machine to where you want to export the key pair.
9 Enter a name for the key pair with a .pfx extension in the Filename text box and click
Export. You see an Export Successful message.
10 Click OK.
Using Keytoolgui to Import a Key Pair
1 Start the keytoolgui from the component to which you want to import the key pair. To
do so, run the following command from the component’s <ARCSIGHT_HOME>/bin
directory.
2 Select File->Open keystore and navigate to your component’s keystore.
3 Enter the keystore password when prompted. The default password is changeit.
4 Select Tools->Import Key Pair and navigate to the location of the key pair file,
select it and click Choose.
5 Enter the password for the key pair file when prompted and click OK.
6 Select the key pair and click Import.
7 Enter an alias for the key pair and click OK.
8 Enter a new password for the key pair file to be imported, confirm it, and click OK. You
see a message saying Key Pair Import Successful.
9 Click OK.
10 Select File->Save keystore to save the changes to the keystore and exit the
keytoolgui.
Using Keytoolgui to Export a Certificate
1 Start the keytoolgui from the component from which you want to export the
certificate. To do so, run the following command from the component’s
<ARCSIGHT_HOME>/bin directory.
2 Select File->Open keystore and navigate to your component’s truststore.
3 Enter the truststore password when prompted. The default password is “changeit”
without the quotes.
4 Right-click the certificate and select Export.

2 Configuration
e Make sure to select Head Certificate as Export Type and DER Encoded as the
Export Format in the following dialog and click OK:
f Navigate to the location where you want to export the certificate, and enter a
name for the certificate with a .cer extension and click Export.
g You see the following message:
5 If the component into which you want to import this certificate resides on a different
machine than the machine from which you exported the certificate (the current
machine), copy this certificate to the to the other machine.
Using Keytoolgui to Import a Certificate
1 Start the keytoolgui from the component into which you want to import the certificate.
To do so, run the following command from the component’s <ARCSIGHT_HOME>/bin
directory.
2 Click File->Open keystore and navigate to the truststore
(<ARCSIGHT_HOME>/jre/lib/security) of the component.

2 Configuration
3 Select the store named cacerts and click Open.
4 Enter the password for the truststore when prompted. The default password is
‘changeit’ (without quotes).
5 Click Tools->Import Trusted Certificate and navigate to the location of the
certificate that you want to import.
6 Click Import.
7 You see the following message. Click OK.
8 The Certificate details are displayed. Click OK.
9 You see the following message. Click Yes.
10 Enter an alias for the Trusted Certificate you just imported and click OK.
Typically, the alias Name is same as the fully qualified host name.
11 You see the following message. Click OK.
12 Save the truststore file.

2 Configuration
Creating a keystore Using Keytoolgui
directory.
2 Click File->New keystore.
3 Select JKS and click OK.
4 Click File->Save keystore.
Generating a Key Pair Using Keytoolgui
directory.
2 Click File->Open keystore and navigate to your keystore.
3 Click Tools->Generate Key Pair and fill in the fields in the General Certificate dialog
and click OK.
4 Enter an alias for the newly created key pair and click OK.
5 Save the keystore by clicking File->Save keystore.
keytool
The keytool utility is the command-line version of keytoolgui that you can use to
manipulate the keystores and truststores directly. Use the keytool utility on UNIX
environments without X11 or whenever a command-line option is more suitable.
Use keytool -help for a complete list of all command options and their arguments.
To use keytool, enter this command:
arcsight keytool [option] –store <store value>
where <store value> can be:
 managerkeys—Manager keystore
 managercerts—Manager truststore
 webkeys—Web keystore
 webcerts—Web truststore
 ldapkeys—Manager LDAP Client keystore
 ldapcerts—Manager LDAP Client truststore
 clientkeys—Client keystore
 clientcerts—Client truststore
On SmartConnector hosts, use:
arcsight agent keytool [option] –store <store value>
The following is an example for creating a 2048-bit, RSA key-pair with the mykey alias that
expires in 10 years (3650 days).

2 Configuration
arcsight keytool -v -genkeypair -alias mykey -validity 3650 
-keyalg rsa -keysize 2048 -store managerkeys
The following is an example for exporting the above key-pair as a "self-signed" RFC-1421
compliant ASCII certificate.
arcsight keytool -exportcert -alias mykey -v -store managerkeys 
-rfc -file export_mykey.pem
You can also SCP your keystore file to a computer where the ArcSight Console is installed
and use keytoolgui to make changes before uploading back to the remote server.
tempca
The tempca utility enables you to manage the SSL certificate in many ways. To see a
complete list of parameters available for this utility, enter this in <ARCSIGHT_HOME>/bin:
./arcsight tempca
On SmartConnectors, use:
./arcsight agent tempca
A few frequently performed operations using this utility are:
 Viewing the type of certificate in use on the Manager:
./arcsight tempca –i
 Removing the Demo certificate from the list of trusted certificates:
./arcsight tempca -rc
How SSL Works
When a client initiates communication with the SSL server, the server sends its certificate to
authenticate itself to the client. The client validates the certificate by verifying:
 The hostname is identical to the one with which the client initiated communication.
 The certificate issuer is in the list of trusted certificate authorities in the client’s
truststore (<ARCSIGHT_HOME>/jre/lib/security/cacerts) and the client is
able to verify the signature on the certificate by using the CA’s public key from the
certificate in its truststore.
 The current time on the client machine is within the validity range specified in the
certificate to ensure that the certificate is valid.
If the certificate is validated, the client generates a random session key, encrypts it using
the server’s public key, and sends it to the server. The server decrypts the session key
using its private key. This session key is used to encrypt and decrypt data exchanged
between the server and the client from this point forward.

2 Configuration
The following figure illustrates the handshake that occurs between the client and Manager.
With client-side authentication, the server requests the client’s certificate when it sends its
certificate to the client. The client sends its certificate along with the encrypted session key.
SSL certificates
To replace an expired certificate, delete the expired certificate from the truststore, cacerts,
first and then import the new certificate into cacerts. Since the common name (CN) for the
new certificate is identical to the CN in the old certificate, you are not permitted have both
the expired and the new certificate in the cacerts.
To delete a certificate from the truststore, start the keytoolgui and navigate to the
certificate, right-click on the certificate, and select Delete.
Use the keytoolgui to import the new certificate into the truststore or cacerts.
Types
You can use three types of SSL certificates:
 CA-signed
 Self-signed (applicable to default mode only)

2 Configuration
 Demo (applicable to default mode only)
CA-signed certificates are issued by a third party you trust. The third party may be a
commercial Certificate Authority (CA) such as VeriSign and Thawte or you might have
designated your own CA. Because you trust this third party, your clients’ truststores might
already be configured to accept its certificate. Therefore, you may not have to do any
configuration on the client side. The process to obtain a CA-signed certificate is described
in “Create a Key Pair for a CA-Signed Certificate” on page 51.
You can create your own self-signed certificates. A self-signed certificate is signed using the
private key from the certificate itself. Configure clients to trust each self-signed certificate
you create.
ArcSight includes a built-in “demo” Certificate Authority that can issue a temporary demo
certificate during the Manager installation. This CA is provided only to enable you to
complete installation in the absence of a signed certificate. However, ArcSight does not
recommend using a certificate issued by this CA in production environments. If your
Manager was installed with a Demo certificate, configure your clients to accept this
certificate.
Comparing Self-signed and CA-signed certificates
Self-signed certificates are as secure as CA-signed, however, CA-signed certificates scale
better as illustrated in this example:
If you have three SSL servers that use self-signed certificates, configure your clients to
accept certificates from all of them (the three servers are three unique issuers). If you add
a new server, configure clients again. However, if these servers use a CA-signed certificate,
configure the clients once to accept the certificate. If the number of Managers grows in the
future, you do not need to do any additional configuration on the clients.
Using a Demo Certificate
To use a demo certificate:
1 On the Manager:
a Run this command in <ARCSIGHT_HOME>/bin:
b In the Manager Configuration Wizard, select Demo key pair in the screen that
prompts you to select the certificate type.
2 On SmartConnectors:
runagentsetup
b In the SmartConnector Configuration Wizard, select Yes, the ArcSight Manager
is using a demo certificate.
3 On a Console:
You can use a demo certificate in default mode only.

2 Configuration
consolesetup
b In the Console Configuration Wizard, select Yes, the ArcSight Manager is
using a demo certificate.
4 On ArcSight Web server:
webserversetup
b In the Web Configuration Wizard, select Demo key pair in the screen that
prompts you to select the certificate type.
5 On web browsers connecting to ArcSight Web, you do not need to set anything;
however, the browsers display a security dialog every time they connect. To stop a
browser from displaying this dialog:
a In <ARCSIGHT_HOME>/bin, run this command on the Manager machine to
export the demo CA’s certificate:
arcsight tempca –dc
A file named demo.crt is created in your current working directory.
b Import the demo.crt file into your web browser.
See your Web browser’s documentation for details.
Using a Self-Signed Certificate
The procedure you follow depends on the number of ArcSight Managers with which your
clients communicate.
When clients communicate with one ArcSight Manager
To use a self-signed certificate for deployments in which clients communicate with only one
ArcSight Manager, perform these steps:
1 On the Manager, create a self-signed key pair:
a In <ARCSIGHT_HOME>/bin, run this command:
Steps to create a self-signed key pair may be different for a new ArcSight
Manager installation as the Configuration Wizard is launched
automatically during the installation process.

2 Configuration
b In the Manager Configuration Wizard, select Replace with new Self-Signed
key pair. and click Next.
c Enter information about the SSL certificate, as shown in this example. Click Next.
d Enter the SSL keystore password for the certificate. Click Next.

2 Configuration
Remember this password. You use it to open the keystore.
e Step through the Configuration Wizard.
At the end of the Configuration Wizard, these three things happen:
i The Manager’s keystore, <ARCSIGHT_HOME>/config/jetty/keystore,
is replaced with the one created using this procedure.
ii A selfsigned.cer certificate file is generated in the
<ARCSIGHT_HOME>/config/jetty directory.
iii The newly generated self-signed certificate is added to the Manager’s
truststore file, <ARCSIGHT_HOME>/jre/lib/security/cacerts.
2 Export the Manager’s certificate from
<ARCSIGHT_HOME>/jre/lib/security/cacerts.
3 Make sure to copy the Manager’s certificate to the any machine on which the clients
connecting to the Manager are installed.
4 Import the Manager’s certificate to the <ARCSIGHT_HOME>/jre/lib/security
directory on all clients. See “Using Keytoolgui to Import a Certificate” on page 40.
The self-signed certificate does not take effect until the Manager
is restarted later in this procedure.
This step overwrites your existing cacerts with the new one that contains
the information about the Trusted Certificate Authority (CA) that signed
your self-signed certificate. However, the new cacerts file does not take
effect until the client is restarted later in this procedure.
Make sure you have imported the Manager’s certificate to all existing
clients before proceeding further. Otherwise, after you perform the next
steps, only clients with the new Manager’s certificate can connect to the
Manager.

2 Configuration
5 Restart the Manager process so that the Manager can start using the self-signed
certificate. Restart all clients.
6 When installing a new client, repeat Steps 2-4 of this procedure.
7 On the ArcSight Web server, perform the steps listed in section “Setting up SSL Client
Authentication on ArcSight Web” on page 64.
8 On the ArcSight Console, perform the steps listed in section “Setting up SSL Client-Side
Authentication on ArcSight Console running in Default Mode” on page 57.
When clients communicate with multiple ArcSight Managers
To use self-signed certificate for a deployment in which clients communicate with more
than one ArcSight Managers, perform these steps for each Manager:
1 Follow Step 1 from the previous procedure on all Managers.
2 Copy the selfsigned.cer file from all Managers to the
<ARCSIGHT_HOME>/jre/lib/security directory on one of your clients.
To prevent a certificate file from overwriting another when you copy multiple
certificate files with the same name to the same location, rename each certificate file
as you copy. For example, copy the certificate file from ManagerA and rename it to
SelfSigned_MgrA.cer.
3 On that client, use the keytoolgui utility to import certificates into the truststore
(cacerts):
a In <ARCSIGHT_HOME>/bin, run this command:
b Click File->Open keystore.
c In <ARCSIGHT_HOME>/jre/lib/security, select the store named cacerts.
Use the password ‘changeit’ (without quotes) to open cacerts.
d Click Tools->Import Trusted Certificate:
i Select the self-signed certificate for a Manager and click Import.
ii You see the following message. Click OK.
The Certificate details are displayed. Click OK.
By following this procedure you append the self-signed certificate to the
existing client truststore, cacerts. Doing so prevents overwriting cacerts,
which happens if you follow the previous procedure.

2 Configuration
iii You see the following message. Click OK.
iv Enter an alias for the Trusted Certificate you just imported and click OK.
Typically, the alias Name is same as the fully qualified host name.
v You see the following message. Click OK.
vi Save the truststore file.
vii Repeat Steps i through vi for all self-signed certificates you copied.
e On the client, enter this command in <ARCSIGHT_HOME>/bin to stop the client
from using the currently in-use Demo certificate:
For SmartConnectors, run:
./arcsight agent tempca –rc
4 Repeat this cacerts procedure on all other clients.
5 Restart the Manager service so that the Manager can start using the self-signed
certificate.
6 Restart the client.
7 When installing a new client, copy the cacerts file from any client you updated earlier
in this procedure.

2 Configuration
Using a CA-Signed SSL Certificate
Using certificate signed by a Certificate Authority means replacing your demo or self-signed
certificate. You should obtain two CA-signed certificates—one for the Manager and the
other for ArcSight Web, unless both components are installed on the same machine. Follow
the procedure described in this section to obtain and import the certificates to the Manager,
and if appropriate, to ArcSight Web.
Obtaining and deploying a CA-signed certificate involves these steps:
1 Create a Key Pair for a CA-Signed Certificate.
2 Send for the CA-Signed Certificate.
3 Import the CA Root Certificate.
4 Import the CA-Signed Certificate.
6 Accommodating Additional ArcSight Components.
Create a Key Pair for a CA-Signed Certificate
To Create a key pair:
1 On the Manager machine, run this command to launch the keytoolgui utility in
<ARCSIGHT_HOME>/bin:
2 Click File->New keystore to create a new keystore.
3 Select JKS for the keystore Type, it supports Java keystore:
4 Click Tools->Generate Key Pair to create the key pair. This can take some time.
5 Enter key pair information such as the length of time for its validity (in days). Click OK.
For Common Name (CN), enter the fully qualified domain name of the Manager.
Ensure that DNS servers, used by the clients connecting to this host, can resolve this
host name.
For Email(E), provide a valid e-mail address as the CAs typically send an e-mail to this
address to renew the certificate.
When you click OK it will ask you for a new password. Use the password of your
existing keystore to save this keystore. Also, the Manager may fail to start if the

2 Configuration
password of the Key pair does not match the password of the keystore, which is
encrypted in server.properties. If you do not remember the password, run the
Manager setup Wizard and change the password of your existing keystore before you
proceed. You will reuse this file after receiving the reply from the CA.
6 Specify an alias name of mykey for referring to the new key pair.
7 Click File->Save as and save the keystore with a name such as keystore.request.
For ArcSight Web, save the file with a name such as webkeystore.request.
Send for the CA-Signed Certificate
To send for the CA-signed certificate, first create a certificate signing request (CSR).
1 In the keytoolgui utility, right-click the mykey alias name and select Generate CSR
to create a Certificate Signing Request.
2 Choose a path and filename, and click Generate. 
After you enter a file name, the CSR file is generated in the current working directory.
3 Send the CSR to the selected Certificate Authority (CA).
After verifying the information you send, the CA electronically signs the certificate
using its private key and replies with a certification response that contains the signed
certificate.
Import the CA Root Certificate
When you get the response from the certificate authority, it should include instructions for
getting the root CA certificate. You can skip this step if renewing a CA-signed certificate
issued by the same root certificate authority. You import the CA root certificate into the
truststore file.
1 Save the Root CA certificate as a file rootca.cer.
2 Repeat the following procedure on all the machines where the Manager is installed:
a Launch the keytoolgui utility on the Manager machine.
b Click File > Open keystore.
c Select the Truststore file located at
<ARCSIGHT_HOME>/jre/lib/security/cacerts. Use the default password
changeit to open cacerts.
d Click Tools >Import Trusted Certificate, and pick the rootca.cer file.
e You see the following warning message: 
“Could not establish a trust path for the certificate. The certificate information will
now be displayed after which you may confirm whether or not you trust the
certificate.”
f Click OK to finish.
• If the CA root certificate has a chain, follow the same procedure to import
all intermediate CA certificates into the Truststore.
• Update the CA root certificate on other ArcSight components, as well.
- Repeat step 2 on one of Consoles.
- Copy the updated cacerts to any Logger or Connector Appliance, and
other PCs that have installed Consoles, Connectors, or ArcSight Web.
• Restart all services after the new cacerts is copied.

2 Configuration
Import the CA-Signed Certificate
When the CA has processed your request, it sends you a file with the signed certificate. You
import this certificate into the Manager’s keystore.
The SSL certificate you receive from the Certificate Authority must be a 128-bit X.509
Version 3 certificate. The type of certificate is the same one that is used for common web
servers. The signed certificate must be returned by the CA in base64 encoded format. It
looks similar to this:
-----BEGIN CERTIFICATE-----
MIICjTCCAfagAwIBAgIDWnWvMA0GCSqGSIb3DQEBBAUAMIGHMQswCQYDVQQGEwJaQT
EiMCAGA1UECBMZRk9SIFRFU1RJTkcgUFVSUE9TRVMgT05MWTEdMBsGA1UEChMUVGhh
d3RlIENlcnRpZmljYXRpb24xFzAVBgNVBAsTDlRFU1QgVEVTVCBURVNUMRwwGgYDVQ
QDExNUaGF3dGUgVGVzdCBDQSBSb290MB4XDTAyMDkyNzIzMzI0MVoXDTAyMTAxODIZ
MzI0MVowaDELMAkGA1UEBhMCrVMxDTALBgNVBAgTBGJsYWgxDTALBgNVBAcTBGJsYW
gxDTALBgNVBAoTBGJsYWgxDTALBgNVBAsTBGJsYWgxHTAbBgNVBAMTFHppZXIuc3Yu
YXJjc2lnaHQuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCZRGnVfQwG1b
+BgABd/p8UhsaNov5AjaagAoBmouJCwgW2vwN4JViC
CSBkDpiqVF7K11Sx4ZVSXX4+VQ6k4gT5G0kDNvQeN05wWkzEMygMB+ZBnYqPA/XtWR
ZtjxvH
MoqS+JEqHruiMLITC6q0reUB/txby6+S9zNo/fUG1pkIcQIDAQABoyUwIzATBgNVHS
UEDDAKBggrBgEFBQcDATAMBgNVHRMBAg8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAFY3
7E60+P4b3zTLnaG7EVM57GtkED6PwCIilB6ixjvNL4MNGRubPa8kyaZp5fEDoNUPQV
QxnpABjzTalRfYgjNFJ6ltI6ZKjBO5kim9UBeCnKiNNzhIyDyFwbHXOPB/JaLIV+jG
ugYNS7hf/ay0BXKlfueO07EgjhhB/mQFs2JB
-----END CERTIFICATE-----
Before proceeding, make sure the name of the issuer that signed your certificate exists as
a Trusted CA in cacerts. (Use keytoolgui to check your cacerts.)
Follow these steps to import the signed certificate:
1 If the returned file has the .CER or .CRT file extension, save it to the
<ARCSIGHT_HOME>/config/jetty directory and skip to step 4.
2 Using any text editor, copy and paste the text string to a file. Include the line "-----
BEGIN CERTIFICATE-----" and line "-----END CERTIFICATE-----", and make sure there
are no extra spaces before or after the string.
3 Save it to a file named ca_reply.txt on the Manager in the
<ARCSIGHT_HOME>/config/jetty directory.
4 On the Manager machine, run this command in <ARCSIGHT_HOME>/bin:
5 Click File->Open keystore and select the keystore (keystore.request or
webkeystore.request) you saved in Step 7 in “Create a Key Pair for a CA-Signed
Certificate” on page 51. Provide the password you used to save the keystore in that
step.
6 Right-click the key pair you created at the beginning of the process and named mykey.
7 Select Import CA Reply from the menu.
8 Select the CA reply certificate file and click Import.

2 Configuration
If the CA reply file contains a chain of certificates, the keytoolgui utility tries to
match the reply’s root CA to an existing Trusted Certificate in your cacerts truststore. If
this operation fails, the Certificate Details dialog appears for manual verification.
Acknowledge the certificate by clicking OK and answering Yes to the subsequent
challenge. Answer No if the certificate is not trustworthy for some reason.
After the key pair you generated has been updated to reflect the content of the CA
reply, the keystore named keystore.request contains both the private key and the
signed certificate (in the alias mykey).
9 Select File > Save. The keystore is now ready for use by the ArcSight Manager or
ArcSight Web.
10 Make a backup of the existing keystore by renaming it: Rename
<ARCSIGHT_HOME>/config/jetty/keystore to
<ARCSIGHT_HOME>/config/jetty/keystore.old.
If, for any reason, the new keystore does not work properly, you can revert back to the
demo keystore by replacing keystore.old with the new keystore.
For ArcSight Web, rename the file to webkeystore.old.
11 Copy <ARCSIGHT_HOME>/config/jetty/keystore.request to
<ARCSIGHT_HOME>/config/jetty/keystore.
For ArcSight Web, copy webkeystore.request to webkeystore.
12 For successful reconfiguration and Manager startup, enter the keystore passwords into
the appropriate properties file. 
Enter the password into the webserver.properties file for ArcSight Web using the
following command (all on one line):
arcsight changepassword 
-f <ARCSIGHT_HOME>/config/webserver.properties 
-p server.privatekey.password
Enter the password into the server.properties file for the Manager using the
following command (all on one line):
arcsight changepassword 
-f <ARCSIGHT_HOME>/config/server.properties 
-p server.privatekey.password
After entering this command the system displays the previous password as asterisks
and asks you to enter and then confirm your new password. These commands enter
the password into the properties file in an encrypted format.
13 If your Manager clients trust the CA that signed your server certificate, go to “Restart
the Manager” on page 55.
Otherwise, perform these steps to update the client’s cacerts (truststore):
a Obtain a root certificate from the CA that signed your server certificate and copy it
to your client machine.
b For one client, use the keytoolgui utility to import the certificate into the
truststore (cacerts):
Also perform these steps on the Manager to update the Manager’s
cacerts so that Manager clients such as the archive utility can work.

2 Configuration
i In <ARCSIGHT_HOME>/bin, run this command:
ii Click File->Open keystore.
iii Select the store named cacerts. Use the password changeit to open
cacerts.
iv Click Tools->Import Trusted Certificate and select the certificate you
copied in Step 10a of this procedure.
v You see the following message. Click OK.
vi Enter an alias for the Trusted Certificate you just imported and click OK.
vii Right-click the alias ca in the truststore and choose Delete from the menu.
viii Save the keystore.
c Copy the <ARCSIGHT_HOME>/jre/lib/security/cacerts file from the
client in the previous step to all other clients.
14 If your ArcSight Web browser clients trust the CA that signed your ArcSight Web
certificate, go to Restart the Manager.
Otherwise, perform these steps:
a Obtain a root certificate from the CA that signed your ArcSight Web certificate.
b Import the certificate into your web browser. See your browser’s documentation
for details.
Restart the Manager
When you restart the Manager, clients it cannot communicate with it until their keystores
are populated with the new certificate.
The Manager may fail to start if the password of the Key pair does not match the
password of the keystore, which is encrypted in server.properties. If you do not
remember the keystore password, run the Manager setup wizard and change the
password of your existing keystore.
2 Restart all clients.

2 Configuration
3 To verify that the new certificate is in use:
a From the command line navigate to <ARCSIGHT_HOME> and enter the
command: arcsight tempca -i
The output shows which CA issuer signed the SSL CA-signed certificate, certificate
type, status of a validation of the certificate, and so on.
b Point a web browser to https://<manager_hostname>:8443. to test it.
Accommodating Additional ArcSight Components
Perform these extra steps to use CA-signed certificates with additional ArcSight
components such as ArcSight Web, the ArcSight Console, or SmartConnectors.
 Adding additional Managers
You do not need to add the CA root certificate to the Truststore-cacerts file again.
However, you must copy the cacerts file from the existing Manager to the new
Manager.
 Other ArcSight Components (Console, ArcSight Web, and SmartConnectors).
When installing a new Console, you must copy the 'cacerts' file from the existing
Console, which has been updated in the Phase 3, to the newly installed Console. This
configuration procedure of Manager Ca-signed SSL certificate can be applied on the
ArcSight Web server unless both components are installed on the same machine.
For ArcSight Web, use the webserversetup utility after the certificate is updated to
confirm the certificate is valid, as follows:
a Login as an arcsight user on the ArcSight Web server machine.
b Execute the following command from <ARCSIGHT_HOME>/bin:
./arcsight webserversetup
c Restart the ArcSight Web server.
Removing a Demo Certificate
You can remove the demo certificate by using the tempca script located in
<ARCSIGHT_HOME>/bin. Issue the following command on all Manager and Console
installations:
arcsight tempca -rc
For SmartConnectors, run the tempca script using the following command:
arcsight agent tempca -rc
Replacing an Expired Certificate
When a certificate in your truststore/cacerts expires, you need to replace it with a new one.
To replace the certificate:
1 Delete the expired certificate from the truststore/cacerts.
To delete a certificate from the truststore or cacerts, start the keytoolgui and navigate
to the certificate, right-click on the certificate, and select Delete.
2 Replace the certificate by importing the new certificate into truststore/cacerts as the
case may be. Use the keytoolgui to import the new certificate into the truststore or
cacerts. See “Using a Demo Certificate” on page 45, “Using a Self-Signed Certificate”

2 Configuration
on page 46, or “Using a CA-Signed SSL Certificate” on page 51 section (depending on
the type of certificate you are importing) for steps on how to import the certificate.
Since the common name (CN) for the new certificate is identical to the CN in the old
certificate, you are not permitted to have both the expired as well as the new certificate co-
exist in the truststore, cacerts.
Establishing SSL Client Authentication
By default, clients (SmartConnectors, Consoles, and ArcSight Web) authenticate using user
name and password. The clients can optionally use SSL authentication for clients. If SSL
client authentication is enabled, you can optionally disable user name and password login,
as described in the next section.
When client-side authentication is used, the SSL clients contain a keystore and the SSL
server contains a truststore.
Setting up SSL Client-Side Authentication on ArcSight Console
running in Default Mode
To enable client-side authentication for ArcSight Console running in default mode, perform
these steps in addition to the ones you perform for setting up server authentication:
1 On each Console, generate a key pair. For CA-signed certificate follow the steps in
section “Create a Key Pair for a CA-Signed Certificate” on page 51.:
a From the Console’s <ARCSIGHT_HOME>/bin directory start the keytoolgui by
running the following command:
b Open File->New keystore. This opens the New keystore Type dialog.
c Select JKS and click OK.
d Click Tools->Generate Key Pair and fill in the fields in the following dialog:
Before you enable client-side authentication, make sure that you log in to the
Console and create a new user or modify an existing user such that you set
the user’s external_id to the one specified in the certificate created on the
Console. The external id should be set to the users name set as the CN
(Common Name) setting when creating the certificate.
The Common Name field in the following screen should be the external ID of
the user logging in to the Manager that this console connects to.

2 Configuration
e Enter an alias for the key pair in the following dialog and click OK:
f Enter a password for the keystore and confirm it and click OK.
g You see the following message.
2 Export the key pair you just generated.
If you plan to install the Console, Manager, and Web on the same machine,
make sure that this alias is unique. Also, do not use the machine name or IP
address for the alias. ArcSight Web and Console cannot have identical CNs
when installed on the same machine as the Manager.
When you install ArcSight Web, set the CN of the ArcSight Web’s key pair you
generate to the name or IP address of the machine on which you are installing
it. Hence, if both Web and Console are on the same machine, and if you use
the machine name or IP address for the CN for both the Web and the Console,
then ArcSight Web gives you an error when configuring.

2 Configuration
a In the keytoolgui right-click the key pair you just generated and select Export.
b Make sure to select Head Certificate as Export Type and DER Encoded as the
c Enter a name for the certificate and click Export.

2 Configuration
d You see the following message:
e If your Console is on a different machine than the Manager, copy this certificate to
the Manager’s machine.
3 If you are using self-signed certificate skip this step and continue with step 4.
Import the signed certificate response in the keystore of all Consoles.
 Import the signed certificate response in the Console’s keystore,
keystore.client. Follow the steps in section “Import the CA Root Certificate”
on page 52.
 Use the changepassword tool to set an encrypted keystore password in the
client.properties file:
arcsight changepassword -f config/client.properties -p
ssl.keystore.password
4 Save the keystore in the Console’s <ARCSIGHT_HOME>/config directory by clicking
on File->Save keystore.
a Enter a password for the keystore and confirm it.
b Enter keystore.client (name for the keystore) in the File Name text box and
click Save.
5 Change the following properties in the Console’s
<ARCSIGHT_HOME>/config/client.properties file and save the file:
ssl.keystore.password=<set-this-to-password-set-when-you-saved-
the-keystore>

2 Configuration
ssl.keystore.path=config/keystore.client
ssl.client.auth=true
Do not change the keystore name to anything other than keystore.client.
6 Use the changepassword tool to set an encrypted keystore password in the
7 Import Console’s certificate into the Manager’s truststore.
If your Manager trusts the CA that signed your Console’s certificates, go to the next
step. Otherwise perform these steps to update the Manager’s truststore.
a Start the keytoolgui by entering arcsight keytoolgui command from the
Manager’s bin directory.
b Click File->Open keystore and navigate to Manager’s
<ARCSIGHT_HOME>/config/jetty/truststore.
c Enter changeit when prompted for the password and click OK.
d Click Tools->Import Trusted Certificate.

2 Configuration
e Navigate to the Console’s certificate that you exported earlier and click Import.
f You see the following message. Click OK.
g Review the certificate details and click OK.
h Click Yes in the following dialog.
i Enter an alias for the certificate.
j You get the following message if the import was successful.
k Click OK and save the changes to the truststore.
8 Export the Console’s private key. If you use ArcSight Web, you are required to import
the Console’s private key into the Web browser you use with ArcSight Web.
a Start the keytoolgui from the Console’s bin directory.

2 Configuration
b Click on File->Open keystore and navigate to the Console keystore you
created.
c Right-click on the Console’s key pair and select Export.
d Select Private Key and Certificates as Export Type and PKCS#12 as the
Export Format if not already selected and click OK.
e Enter the password that you had set for the Console’s keystore when prompted
and click OK.
f Enter a new password for the keystore and confirm the password and click OK.

2 Configuration
g Enter a name for the Console’s private key with a .pfx extension and click Export.
h You receive a message saying Export Successful. Click OK and exit the keytoolgui.
9 Exit keytoolgui.
11 Restart ArcSight Console.
Setting up SSL Client Authentication on ArcSight Web
To enable client-side authentication for clients running in default mode, perform these
steps in addition to the ones you perform for setting up server authentication:
1 Generate a key pair on ArcSight Web. For CA-signed certificate follow the steps in
section “Create a Key Pair for a CA-Signed Certificate” on page 51
a From the Web’s <ARCSIGHT_HOME>/bin directory start the keytoolgui by
b Open File->New keystore. This opens the New keystore Type dialog.
c Select JKS and click OK.

2 Configuration
d Click Tools->Generate Key Pair and fill in the fields in the following dialog:
e Enter an alias for the key pair and click OK.
2 Export the key pair you just generated.
a In the keytoolgui right-click the key pair you just generated and select Export
Key pair.
b Make sure to select Head Certificate as Export Type and DER Encoded as the
Make sure to use the machine name or IP address on which ArcSight Web is
installed for the CN name.

2 Configuration
c Enter a name for the certificate and click Export.
d You see the following message:
e If your ArcSight Web is on a different machine than the Manager, copy this
certificate to the Manager’s machine.
3 Save the keystore in the Web’s <ARCSIGHT_HOME>/config directory by clicking on
File->Save keystore.
a Enter a password for the keystore and confirm it.
b Give the keystore a name and click Save.
4 If you are using self-signed certificate skip this step and continue with step 5.
Import the signed certificate response in the keystore of ArcSight Web.
 Import the signed certificate response in the Web’s keystore. Follow the steps in
section “Import the CA Root Certificate” on page 52.
 Use the changepassword tool to set an encrypted keystore password in the
5 Add the following properties in the Web’s
<ARCSIGHT_HOME>/config/client.properties file and save the file:
ssl.keystore.password=<password-set-when-you-saved-the-
keystore>
ssl.keystore.path=config/jetty/webkeystore

2 Configuration
6 Import Web’s key pair into the Manager’s truststore.
If your Manager trusts the CA that signed your client’s certificates, go to the next step.
Otherwise perform these steps to update the Manager’s truststore.
a Start the keytoolgui by entering arcsight keytoolgui command from the
Manager’s bin directory.
b Click File->Open keystore and navigate to
<ARCSIGHT_HOME>/config/jetty/truststore.
c Enter changeit when prompted for the password and click OK.
e Navigate to the Web’s certificate that you exported earlier and click Import.
f You see the following message. Click OK.

2 Configuration
g Review the certificate details and click OK.
h Click Yes in the following dialog.
i Enter an alias for the certificate.
j You get the following message if the import was successful.
k Click OK and save the changes to the truststore.
7 Import Console’s certificate into webtruststore.
a Start the keytoolgui from ArcSight Web’s bin directory.
b Click File->Open keystore and navigate to the Web’s
<ARCSIGHT_HOME>/config/jetty/webtruststore.
c Enter “changeit” (without quotes) when prompted for password.
e Navigate to the Console’s certificate and click Import.
f Click OK in the next message box prompting you that “Could not establish a trust
path for the certificate...”
g View the certificate details and click OK.
h Click Yes when prompted whether you want to accept the certificate as trusted.
i Enter an alias for the console’s certificate and click OK.
j You see a message saying “Trusted Certificate Import Successful.”
k Click OK.

2 Configuration
l Save changes to the webtruststore and exit the keytoolgui.
8 Import the following into the web browser that you use with ArcSight Web:
 Web’s certificate you exported in Step 2 on page 65 above.
 Console’s private key you created in Step 8 on page 62 in section “Setting up SSL
Client-Side Authentication on ArcSight Console running in Default Mode” on
page 57.
See your web browser’s documentation for steps to do the above.
10 Restart ArcSight Web.
Setting up Client-side Authentication on Partition Archiver and
SmartConnectors
In order to enable client-side authentication on clients (Partition Archiver and/or
SmartConnectors) running in default mode, perform these steps:
1 Create a new client keystore in the ArcSight Database’s (for Partition Archiver) or the
SmartConnector’s /config directory.
a Start the keytoolgui from the client’s bin directory by running the following:
On SmartConnector:
./arcsight agent keytoolgui
On Partition Archiver:
arcsight keytoolgui
b Go to File->New keystore.
c Select JKS for type of keystore and click OK.

2 Configuration
d Save the keystore by clicking File->Save keystore As, navigate to the config
directory, enter keystore.client in the File Name box and click Save.
e Set a password for the keystore and click OK.
2 Create a new key pair in the config/keystore.client of the ArcSight Database
or SmartConnector. (If you already have a keypair that you would like to use, you can
import the existing key pair into the client’s config/keystore.client. See section
“Using Keytoolgui to Import a Key Pair” on page 39 for details.)
a In keytoolgui, click Tools->Generate Key Pair.
b In the Generate Certificate dialog enter the details requested and click OK.
c Enter an alias for the key pair and click OK.

2 Configuration
d Set a password for the key pair and click OK.
e You see the following message after the key pair is created. Click OK.
You should now see a key pair with the alias you set for it in the keystore.
3 Create a client SSL configuration text file in the config directory and name it
client.properties for partition archiver or in the user/agent directory and
name it agent.properties for a connector. The contents of this file (whether client
or agent) should be as follows:
auth.null=true
ssl.client.auth=true
cac.login.on=false 
ssl.keystore.path=config/arcsightkeystore.client
ssl.keystore.password=<client.keystore_password>
4 Export the client’s (Partition Archiver or Connector) certificate using keytoolgui. See
section “Using Keytoolgui to Export a Certificate” on page 39 for details.
5 Import the CA’s certificate of the client’s certificate (in case you are using CA-signed
certificate) or the client’s certificate itself (in case you are using a self-signed
certificate) into the Manager’s truststore, /config/jetty/truststore. see section
“Using Keytoolgui to Import a Certificate” on page 40 for details.
7 Restart the client (Partition Archiver or Connector).
Migrating from one certificate type to another
When you migrate from one certificate type to another on the Manager, you have to update
all Consoles, SmartConnectors, and ArcSight Web installations.
Migrating from Demo to Self-Signed
To migrate from a demo to self-signed certificate:
1 Follow the steps described in “Using a Self-Signed Certificate” on page 46.
2 Follow the instructions in “Verifying SSL Certificate Use” on page 72 to ensure that a
self-signed certificate is in use.
Migrating from Demo to CA-Signed
To migrate from a demo to CA-Signed certificate:
1 Follow the steps described in “Using a CA-Signed SSL Certificate” on page 51.
2 Follow the instructions in “Verifying SSL Certificate Use” on page 72 to ensure that CA-
signed certificate is in use.
Make sure that this password is identical to the password that you set for
/config/keystore.client when creating it.

2 Configuration
Migrating from Self-Signed to CA-Signed
To migrate from a self-signed to CA-signed certificate:
1 Follow the steps described in “Using a CA-Signed SSL Certificate” on page 51.
2 Follow the instructions in “Verifying SSL Certificate Use” on page 72 to ensure that a
CA-signed certificate is in use.
Verifying SSL Certificate Use
After the migration, run this command in <ARCSIGHT_HOME>/bin on the client to ensure
the certificate type you intended is in use:
./arcsight tempca –i
In the resulting output, a sample of which is available below, do the following:
1 Review the value of the line: Demo CA trusted.
The value should be “no.”
If the value is “yes,” the demo certificate is still in use. Follow these steps to stop using
the demo certificate:
a In <ARCSIGHT_HOME>/bin, enter the following command to make the client
stop using the currently in use demo certificate:
For SmartConnectors, run:
./arcsight agent tempca –rc
b Restart the client.
2 Verify that the Certificate Authority that signed your certificate is listed in the output.
For a self-signed certificate, the Trusted CA is the name of the machine on which you
created the certificate
Sample output for verifying SSL certificate use
This is a sample output of the arcsight tempca –i command run from a Console’s bin
directory on the Windows platform:
ArcSight TempCA starting...
SSL Client
truststore C:arcsightConsolecurrentjrelibsecuritycacerts
Type JKS
Demo CA trusted no
Trusted CA DigiCert Assured ID Root CA
[digicertassuredidrootca]
Trusted CA TC TrustCenter Class 2 CA II
[trustcenterclass2caii] .
.
.
Demo CA
keystore C:arcsightConsolecurrentconfigkeystore.tempca
Exiting...

2 Configuration
Using Certificates to Authenticate Users to ArcSight
Instead of using a user name and password to authenticate a user to ArcSight Manager or
ArcSight Web, you can configure these systems to use a digitally-signed user certificate.
This section tells you how to do that. You can use Manager’s this capability in environments
that make use of Public Key Infrastructure (PKI) for user authentication.
The Manager and ArcSight Web accept login calls with empty passwords and use the
Subject CN (Common Name) from the user’s certificate to identify the user.
You must enable SSL client authentication as described in the previous section to use
digitally-signed user certificates for user authentication.
To configure the Manager or ArcSight Web to use user certificates, do the following:
1 On the Console, make sure that External ID field in the User Editor for every user is set
to a value that matches the CN in their user certificate.
2 Restart the system you are configuring.
3 Restart the Consoles.
When you start the Console, the user name and password fields are grayed out. Simply
select the Manager to which you want to connect and click OK to log in.
Using the Certificate Revocation List (CRL)
ArcSight ESM supports the use of CRL to revoke a CA-signed certificate that has been
invalidated. The CA that issued the certificates also issues a CRL file containing a signed list
of certificates that it had previously issued, and that it now considers invalid. ArcSight
Manager checks the client certificates against the list of certificates listed in the CRL and
denies access to clients whose certificates appear in the CRL.
Before you use the CRL feature, make sure:
 Your certificates are issued/signed by a valid Certificate Authority or an authority with
an ability to revoke certificates.
 The CA’s root certificate is present in the Manager’s
<ARCSIGHT_HOME>/config/jetty/truststore directory.
The Manager validates the authenticity of the client certificate using the root certificate
of the signing CA.
 You have a current CRL file provided by your CA.
The CA updates the CRL file periodically as and when additional certificates get
invalidated.
To use the CRL feature:
1 Make sure you are logged out of the Console.
2 Copy the CA-provided CRL file into your Manager’s
<ARCSIGHT_HOME>/config/jetty/crls directory.
Before you enable client-side authentication, make sure that you log in to the
Console and create a new user or modify an existing user such that you set
the user’s external_id to the one specified in the certificate created on the
Console. The external id should be set to the users name set as the CN
(Common Name) setting when creating the certificate.

2 Configuration
After adding the CRL file, it takes approximately a minute for the Manager to get
updated.
Reconfiguring the ArcSight Console after Installation
You can reconfigure ArcSight Console at anytime by typing arcsight consolesetup
within a command prompt window.
Run the ArcSight Console Configuration Wizard by entering the following command in a
command window in the <ARCSIGHT_HOME>/bin directory:
./arcsight consolesetup
To run the ArcSight Console Setup program without the graphical user interface, type:
./arcsight consolesetup -i console
The ArcSight Console Configuration Wizard appears.
Reconfiguring ArcSight Manager
To reconfigure ArcSight Manager settings made during installation, run the ArcSight
Manager Configuration Wizard by typing the following command in a terminal box or
command prompt window:
The arcsight managersetup command opens the ArcSight Manager Configuration Wizard,
but you can also run the ArcSight Manager Setup program silently by typing:
./arcsight managersetup -i console
The ArcSight Manager Configuration Wizard appears to help you re-configure ArcSight
Manager.
To change advanced configuration settings (port numbers, database settings, log location,
and so on) after the initial installation, change the server.properties file. ArcSight’s
default settings are listed in the server.defaults.properties file. You can override
these default settings by adding the applicable lines from
server.defaults.properties to the server.properties file. These files are
located in <ARCSIGHT_HOME>/config.
Changing ArcSight Manager Ports
In order for every component of ArcSight to communicate, any ArcSight SmartConnectors
and ArcSight Consoles must be aware of what IP address the ArcSight Manager is running
on. Also, the ArcSight SmartConnectors and ArcSight Consoles must use the same HTTP or
HTTPS port numbers the ArcSight Manager is currently using.
ArcSight Manager uses a single port (by default, 8443) that any firewalls between the
ArcSight Manager, ArcSight Console, and any ArcSight SmartConnectors must allow
communication through. Port 8443 is the default port used when initially installing
ArcSight, however, you can change this default port number using the ArcSight Manager
Configuration Wizard. For more information, refer to the ArcSight ESM Installation and
Configuration Guide.

2 Configuration
Changing ArcSight Web Session Timeouts
The session timeout affects the web browser pages (i.e., Knowledge Base, reports, and so
forth) that appear within ArcSight Web. After the session has elapsed, or timed out, you
must log back into ArcSight Web to start a new session. You can change the Web default
session timeout in this file in the Manager’s
<ARCSIGHT_HOME>/config/jetty/server.xml file.
The ArcSight Web default session timeout can be changed in this file in ArcSight Web’s
<ARCSIGHT_HOME>/config/jetty/webserver.xml file.
In the above .xml files you see the following lines:
<session-config>
<session-timeout>15</session-timeout>
</session-config>
The value specified, in this case 15, is the session timeout in minutes. Simply change this
number to the session timeout desired and save the file.
Manager Password Configuration
ArcSight Manager supports a rich set of functionality for managing users passwords. This
section describes various password configuration options. Generally, all the settings are
made by editing the server.properties file. See “Managing and Changing Properties
File Settings” on page 17.
Enforcing Good Password Selection
There are a number of checks that ArcSight Manager performs when a user picks a new
password in order to enforce good password selection practices.
Password Length
The simplest one is a minimum and, optionally, a maximum length of the password. The
following keys in server.properties affect this:
auth.password.length.min=6
auth.password.length.max=20
By default, the minimum length for passwords is six characters and the maximum length is
20 characters and can contain numbers and/or letters.
Configuring the above properties to a value of -1 sets the password length to unlimited
characters.
Restricting Passwords Containing User Name
Another mechanism that enforces good password practices is controlled through the
following server.properties key:
auth.password.userid.allowed=false
When this key is set to false (the default), a user cannot include their user name as part of
the password.

2 Configuration
Requiring Mix of Characters in Passwords
Good passwords consist not only of letters, but contain numbers and special characters as
well. This makes them a lot harder to guess and, for the most part, prevents dictionary
attacks.
By default, the minimum length for passwords is six characters and the maximum length is
20 characters and can contain numbers and/or letters.
The following properties control the distribution of characters allowed in new passwords:
auth.password.letters.min=-1
auth.password.letters.max=-1
auth.password.numbers.min=-1
auth.password.numbers.max=-1
auth.password.whitespace.min=0
auth.password.whitespace.max=0
auth.password.others.min=-1
auth.password.others.max=-1
The *.min settings can be used to enforce that each new password contains a minimum
number of characters of the specified type. The *.max settings can be used to limit the
number of characters of the given type that new passwords can contain. Letters are all
letters from A-Z, upper and lowercase, numbers are 0-9; “whitespace” includes spaces,
etc.; “others” are all other characters, including special characters such as #$%@!.
Additionally, the following server.properties key lets you restrict the number of
consecutive same characters allowed.
auth.password.maxconsecutive=3
For example, the default setting of 3 would allow "adam999", but not "adam9999" as a
password.
Furthermore, the following server.properties key enables you to specify the length of
a substring that is allowed from the old password in the new password.
auth.password.maxoldsubstring=-1
For example, if the value is set to 3 and the old password is “secret”, neither “secretive”
nor “cretin” is allowed as a new password.
Checking Passwords with Regular Expressions
To accommodate more complex password format requirements, ArcSight Manager can also
be set up to check all new passwords against a regular expression. The following
server.properties keys can be used for this purpose:
auth.password.regex.match=
auth.password.regex.reject=
The auth.password.regex.match property describes a regular expression that all
passwords have to match. If a new password does not match this expression, ArcSight

2 Configuration
Manager rejects it. The auth.password.regex.reject property describes a regular
expression that no password may match. If a new password matches this regular
expression, it is rejected.
For more information on creating an expression for this property, see http://www.regular-
expressions.info/. The following are a few examples of regular expressions and a
description of what they mean.
 auth.password.regex.match= /^D.*D$/
Only passwords that do not start or end with a digit are accepted.
 auth.password.regex.match= ^(?=.*[A-Z].*[A-Z])(?=.*[a-z].*[a-
z])(?=.*[0-9].*[0-9])(?=.*[â-zA-Z0-9].*[â-zA-Z0-9]).{10,}$
Only passwords that contain at least 10 characters with the following breakdown are
accepted:
 At least two upper case letters
 At least two lower case letters
 At least two digits
 At least two special characters (no digits or letters)
 auth.password.regex.reject= ^(?=.*[A-Z].*[A-Z])(?=.*[a-z].*[a-
z])(?=.*[0-9].*[0-9])(?=.*[â-zA-Z0-9].*[â-zA-Z0-9]).{12,}$
The passwords that contain 12 characters with the following breakdown are rejected:
 At least two upper case letters
 At least two lower case letters
 At least two digits
 At least two special characters (no digits or letters)
Password Uniqueness
In some environments, it is also desirable that no two users use the same password. To
enable a check that ensures this, the following server.properties key can be used:
auth.password.unique=false
If set to true, ArcSight Manager checks all other passwords to make sure nobody is already
using the same password.
Setting Password Expiration
ArcSight Manager can be set up to expire passwords after a certain number of days,
forcing users to choose new passwords regularly. This option is controlled by the following
key in server.properties:
Backslash ( ) characters in regular expressions must be duplicated
(escaped)—instead of specifying , type .
This feature may not be appropriate for some environments as it allows valid
users of the system to guess other user’s passwords.

2 Configuration
auth.password.age=60
By default, a password expires 60 days from the day it is set.
When this setting is used, however, some problems arise for user accounts that are used
for automated log in, such as the user accounts used for Manager Forwarding Connectors.
These user accounts can be excluded from password expiration using the following key in
server.properties:
auth.password.age.exclude=username1,username2
This value is a comma-separated list of user names. The passwords of these users never
expire.
ArcSight Manager can also keep a history of a user’s passwords to make sure that
passwords are not reused. The number of last passwords to keep is specified using the
following key in server.properties:
auth.password.different.min=1
By default, this key is set to check only the last password (value = 1). You can change this
key to keep up to last 20 passwords.
Restricting the Number of Failed Log Ins
ArcSight Manager tracks the number of failed log in attempts to prevent brute force
password guessing attacks. By default, a user's account is disabled after three failed log in
attempts. This feature is controlled through the following key in server.properties:
auth.failed.max=3
Change this to the desired number or to -1 if you do not wish user accounts to be
disabled, regardless of the number of failed log in attempts.
Once a user account has been disabled, ArcSight Manager can be configured to
automatically re-enable it after a certain period of time. This reduces administrative
overhead, while effectively preventing brute force attacks. This mechanism is controlled by
the following key in server.properties:
auth.auto.reenable.time=10
This value specifies the time, in minutes, after which user accounts are automatically re-
enabled after they were disabled due to an excessive number of incorrect log ins. Set the
property key to -1 to specify that user accounts can only be re-enabled manually.
Re-Enabling User Accounts
Under normal circumstances, user accounts that have been disabled—for example, as a
result of too many consecutive failed log ins—can be re-enabled by any user with sufficient
permission. Check the Enabled check box for a particular user in the User Inspect/Editor
panel in the ArcSight Console.
If the only remaining administrator user account is disabled, a command line tool can be
run on the system where ArcSight Manager is installed to re-enable user accounts. First,
ensure that the ArcSight Manager is running. Then, from the command line, run the
following command:
./arcsight reenableuser username

2 Configuration
where username is the name of the user you want to re-enable. After this procedure, the
user can log in again, using the unchanged password.
Properties Related to Domain Field Sets
Domain field sets are a construct in the ESM schema that make it possible to distinguish
between events that pertain to different business verticals, such as credit card
transactions, online banking, or stock transactions.
The domain field sets feature is separately licensed, and requires some additional
configuration on both the Manager and relevant SmartConnectors. See Chapter 18‚ Domain
Field Sets‚ on page 497 in the ArcSight Console User’s Guide for details on this feature.
The following properties related to Domain Field Sets are configurable in the
server.properties file on the Manager:
 domain.event.relevance.percentage
Use this property to set the percentage of additional data fields in an event that must
match the pre-defined domain fields in order for the event to be tied to the domain.
For example, if you set this property to
domain.event.relevance.percentage=0.8, and the additional data in the
event has five fields, if four out of these five fields match the fields defined for a
domain, the event is considered to have an 80% match. Since you set this property to
.8 (or 80%), the event becomes tied to that domain and those four fields are
persisted. The fifth field, which does not match, is dropped. If all five fields match, all
of them are persisted. On the other hand, if only three fields match, the percentage is
less than the 80% minimum you specified, so the event is not tied to the domain and
all fields (even those that match) are dropped.
Each event that the connector sends to the Manager can be identified as belonging to
a particular pre-configured domain. For events that contain additional data, the fields
in the additional data are matched with the fields that are defined for a domain. ESM
determines whether the event should be tied to a domain based on the percentage of
additional data fields that match the domain fields.
 domain.ad.keywords.csv
You can specify which Additional Data field names to exclude when processing
additional data in an event. You can specify the field names to exclude by setting them
in this property. Separate field names with a comma. For example, to exclude integer
and date, set domain.ad.keywords.csv=Integer,Date.
Advanced Configuration for Asset Auto-Creation
Assets are automatically created for all components and, if applicable, for assets arriving
from scan reports sent by vulnerability scanners via scanner SmartConnectors. This is done
by the asset auto-creation feature.
If the profile of events in your network causes asset auto creation feature to create assets
in your network model inefficiently, you can modify the asset auto creation default settings
in the user configuration file, server.properties.
The server.properties file is located at
$ARCSIGHT_HOME/config/server.properties.
For more about working with properties files, see the topic “Managing and Changing
Properties File Settings”

2 Configuration
Asset Auto-Creation from Scanners in Dynamic Zones
The following properties relate to how assets are created from a vulnerability scan report
for dynamic zones.
Create Asset with either IP Address or Host Name
By default, an asset is not created in a dynamic zone if there is no host name present. The
property set by default is:
scanner-event.dynamiczone.asset.nonidentifiable.create=false
You can configure ESM to create the asset as long as it has either an IP address or a host
name. In server.properties, change scanner-
event.dynamiczone.asset.nonidentifiable.create from false to true. ESM
discards conflicts between an IP address and host name (similar IP address, but different
host name and/or MAC address).
When this property is set to true, the following takes place:
Creating an asset if no host name is present can result in an
inaccurate asset model.
Setting scanner-event.dynamiczone.asset.nonidentifiable.create to
true means that assets are created if the asset has either an IP address or a
host name.
This could lead to disabled assets or duplicated assets being created. Change
this configuration only if you are using a dynamic zone to host ostensibly
static assets, such as long-lived DHCP addresses.
Example
Action taken if no
conflicts
Action taken if previous
asset with similar
information
IP=1.1.1.1
hostname=myhost
mac=0123456789AB
Asset created Asset created, previous
asset is deleted.
ip=1.1.1.1
hostname=myhost
mac=null
asset is deleted.
ip=1.1.1.1
hostname=null
mac=0123456789AB
asset is deleted.
ip=1.1.1.1
hostname=null
mac=null
asset is deleted.
ip=null
hostname=myhost
mac=null
asset is deleted.
ip=null
hostname=null
mac=0123456789AB
Asset not created. Either
host name or IP address is
required.
required.

2 Configuration
Preserve Previous Assets
This setting applies when ESM creates assets from a vulnerability scan report for dynamic
zones. By default, if a previous asset with similar information already exists in the asset
model, ESM creates a new asset and deletes the old one.
To preserve the previous asset rather than delete it when a scan finds a new asset with
similar information, you can configure ESM to rename the previous asset. In
server.properties, change scanner-
event.dynamiczone.asset.ipconflict.preserve from false to true.
When ESM is configured with scanner-
event.dynamiczone.asset.nonidentificable.create=false and scanner-
event.dynamiczone.asset.ipconflict.preserve=true, it takes the following
actions:
ip=null
hostname=myhost
mac=0123456789AB
required.
required.
Preserving previous assets results in a larger asset model.
Setting event.dynamiczone.asset.ipconflict.preserve to true means
that assets are continually added to the asset model and not removed. Use
this option only if you know you must preserve all assets added to the asset
model.
Example
Action taken if previous asset with similar
information and preserve = true
IP=1.1.1.1
hostname=myhost
mac=0123456789AB
Asset created, previous asset is renamed.
ip=1.1.1.1
hostname=myhost
mac=null
ip=1.1.1.1
hostname=null
mac=0123456789AB
ip=1.1.1.1
hostname=null
mac=null
No action taken. Either host name or MAC address
is required.
ip=null
hostname=myhost
mac=null
Example
Action taken if no
conflicts
Action taken if previous
asset with similar
information

2 Configuration
Changing the Default Naming Scheme
By default, ESM names assets that come from scanners using the naming scheme outlined
in the topic “Asset Names” in the ArcSight ESM User’s Guide.
You can reconfigure this naming scheme. For example, if you want the asset name for an
asset in a static zone to appear this way in the ESM UI:
myhost_1.1.1.1
In this case, change the default
$destinationAddress - $!destinationHostName
to
$!destinationHostName_$destinationAddress
Compression and Turbo Modes
Compressing ArcSight SmartConnector Events
ArcSight SmartConnectors can send event information to the ArcSight Manager in a
compressed format using HTTP compression. The compression technique used is standard
GZip, providing compression ratio of 1:10 or higher, depending on the input data (in this
case, the events the ArcSight SmartConnector is sending). Using compression lowers the
overall network bandwidth used by ArcSight SmartConnectors dramatically, without
impacting their overall performance.
By default, all ArcSight SmartConnectors have compression enabled. To turn it off, add the
following line to the <ARCSIGHT_HOME>/user/agent/agent.properties file:
compression.enabled = false
ip=null
hostname=null
mac=0123456789AB
ip=null
hostname='myhost'
mac=0123456789AB
Static Zone Dynamic Zone
Property: scanner-event.auto-
create.asset.name.template
scanner-event.auto-
create.dynamiczone.asset.name
.template
Value: $destinationAddress -
$!destinationHostName
$destinationHostName
Example: 1.1.1.1 - myhost myhost
Example
Action taken if previous asset with similar
information and preserve = true

2 Configuration
ArcSight SmartConnectors determine whether the ArcSight Manager they are sending
events to supports compression (ArcSight Manager version 2.2 or later).
Understanding ArcSight Turbo Modes
If your configuration, reporting, and analytic usage permits, you can accelerate the transfer
of sensor information through SmartConnectors by choosing one of the "turbo" modes. The
default transfer mode is called Complete, which passes all the data arriving from the
device, including any additional data (custom, or vendor-specific).
ArcSight SmartConnectors can be configured to send more or less event data, on a per-
SmartConnector basis, and the ArcSight Manager can be set to read and maintain more or
less event data, independent of the SmartConnector setting. Some events require more
data than others. For example, operating system syslogs often capture a considerable
amount of environmental data that may or may not be relevant to a particular security
event. Firewalls, on the other hand, typically report only basic information.
ArcSight defines the following Turbo Modes:
When Turbo Mode is not specified (mode 3, Complete), all event data arriving at the
SmartConnector, including additional data, is maintained. (Versions of ArcSight prior to 3.0
ran in Turbo Mode 3.) Turbo Mode 2, Faster, eliminates the additional custom or vendor-
specific data, which is not required in many situations. Turbo Mode 1, Fastest, eliminates all
but a core set of event attributes, in order to achieve the best throughput. Because the
event data is smaller, it requires less storage space and provides the best performance. It is
ideal for simpler devices such as firewalls.
The ArcSight Manager processes event data using its own Turbo Mode setting. If
SmartConnectors report more event data than the Manager needs, the Manager ignores
the extra fields. On the other hand, if the Manager is set to a higher Turbo Mode than a
SmartConnector, the Manager maintains fields that are not filled by event data. Both
situations are normal in real-world scenarios, because the Manager configuration reflects
the requirements of a diverse set of SmartConnectors.
Event data transfer modes are numbered (1 for Fastest, 2 for Faster, 3 for Complete), and
possible Manager-SmartConnector configurations are therefore:
1-1 Manager and SmartConnector in Fastest mode
1-2 SmartConnector sending more sensor data than Manager needs
1-3 SmartConnector sending more sensor data than Manager needs
2-1 SmartConnector not sending all data that Manager is storing*
2-2 Manager and SmartConnector in Faster mode
2-3 Default: Manager does not process additional data sent by SmartConnector
3-1 Manager maintains Complete data, SmartConnector sends minimum*
Turbo Modes
1 Fastest Recommended for firewalls
2 Faster Manager default

2 Configuration
3-2 Manager maintains additional data, but SmartConnector does not send it
3-3 Manager and SmartConnector in Complete mode
*When the SmartConnector sends minimal data (Turbo Mode 1), the Manager can infer
some additional data, creating a 2-1.5 or a 3-1.5 situation.
Configuring the ArcSight Database Monitor
The Database Monitor is an ArcSight Manager component that monitors the ArcSight
Database for critical conditions. The Database Monitor performs the following check tasks
to ensure that the ArcSight Database can always be used by the ArcSight Manager:
Free space in Oracle tablespaces: This check sends an e-mail message if the free space in
any of the Oracle tablespaces falls below a specified threshold.
Database failure: This check sends an e-mail message if the connection to the database is
lost or if the ArcSight Manager detects a fatal, unrecoverable situation in the database,
such as lack of disk space.
If a critical condition occurs, the ArcSight Manager stops accepting incoming events from
ArcSight SmartConnectors and, in some cases, also stops Console sessions. A message is
printed to server.std.log and server.log and sent to a list of administrators via e-mail. The
message contains a URL you can use to reactivate ArcSight Manager after the problem has
been addressed. In many cases, however, the ArcSight Manager can detect that the
problem has been resolved and resumes normal operations automatically.
For more information about database checks performed to monitor configuration and
runtime attributes of your database, see Appendix C‚ Monitoring Database Attributes‚ on
page 161.
Configuring Database Monitor e-mail message recipients
Use the ArcSight Manager Configuration Wizard to configure Database Monitor e-mail
message recipients. Run the ArcSight Manager Configuration Wizard by typing arcsight
managersetup in a command prompt window or terminal box. The ArcSight Notifier is
not used for Database Monitor notifications, since the ArcSight Manager could already be in
such a fatal state that the Notifier may not be able to function properly.
Configuring the check for free space in Oracle tablespaces
You can set the threshold for checking free space in a tablespace. An e-mail message is
sent if the free space in a tablespace falls below the threshold specified. The threshold is
specified as a percentage. In <ARCSIGHT_HOME>configserver.properties, set
the threshold:
databaseinfo.oracle.freespace.percentage.threshold=5
You can also explicitly exclude certain tablespaces from the check in
server.properties. By default, the system tablespace is excluded:
databaseinfo.oracle.freespace.exclude.tablespaces=SYSTEM

2 Configuration
Sending Events as SNMP Traps
ArcSight can send a sub-stream of all incoming events (that includes rule-generated
events) via SNMP to a specified target. A filter is used to configure which events are sent.
ArcSight’s correlation capabilities can be used to synthesize network management events
that can then be routed to your enterprise network management console.
Configuration of the SNMP trap sender
The SNMP trap sender is configured using the ArcSight Manager configuration file. The
<ARCSIGHT_HOME>/config/server.default.properties file includes a template
for the required configuration values. Copy those lines into your
<ARCSIGHT_HOME>/config/server.properties file and make the changes there.
After making changes to this file, you need to restart the ArcSight Manager.
properties: The following provides a description of specific SNMP configuration parameters:
snmp.trapsender.enabled=true
Set this property to true in order to enable the SNMP trap sender.
snmp.trapsender.uri=
/All Filters/Arcsight System/SNMP Forwarding/SNMP Trap Sender
The filter (specified by URI, all on one line) is used to decide whether or not an event is
forwarded. There is no need to change the URI to another filter, as the "SNMP Trap
Sender" filter can be changed through the ArcSight Console. Changes to the filter specified
immediately affect the SNMP trap sender. By default, the "SNMP Trap Sender" filter logic is
Matches Filter (Correlated Events)—that is, only rules-generated events are forwarded.
snmp.destination.host=
snmp.destination.port=162
The host name and the port of the SNMP listener that wants to receive the traps.
snmp.read.community=public
snmp.write.community=public
The SNMP community strings needed for the traps to make it through to the receiver. The
read community is reserved for future use, however, the write community must match the
community of the receiving host. This depends on your deployment environment and your
receiving device. Please consult your receiving device's documentation to find out which
community string to use.
snmp.version=1
snmp.fields=
event.eventId,
event.name,
Setting the Manager to send SNMP v3 traps is not FIPS compliant. This is
because SNMP v3 itself uses MD5 algorithm. However, SNMPv1 and v2 are
compliant.

2 Configuration
event.eventCategory,
event.eventType,
event.baseEventCount,
event.arcsightCategory,
event.arcsightSeverity,
event.protocol,
event.sourceAddress,
event.targetAddress
These event attributes should be included in the trap. The syntax follows the
SmartConnector SDK as described in the FlexConnector Developer’s Guide. All the ArcSight
fields can be sent. The identifiers are case sensitive, do not contain spaces and must be
capitalized except for the first character. For example:
The SNMP field types are converted as:
Additional data values are accessible by name, for example:
snmp.fields=event.eventName,additionaldata.myvalue
This sends the Event Name field and the value of myvalue in the additional data list part
of the SNMP trap. Only the String data type is supported for additional data, therefore all
additional data values are sent as OCTET STRING.
Asset Aging
The age of an asset is defined as the number of days since it was last scanned or modified.
So, for example, if an asset was last modified 29 hours ago, the age of the asset is taken as
1 day and the remaining time (5 hours, in our example) is ignored in the calculation of the
asset’s age. You can use asset aging to reduce asset confidence level as the time since the
last scan increases.
ArcSight Field SDK/SNMP trap sender identifier
Event Name eventName
Device Severity deviceSeverity
Service service
ArcSight SNMP
STRING OCTET STRING
INTEGER INTEGER32
Address IP ADDRESS
LONG OCTET STRING
BYTE INTEGER

2 Configuration
Excluding Assets From Aging
To exclude certain assets from aging, you can add those assets to a group and then set the
property asset.aging.excluded.groups.uris in the server.properties file to
the URI(s) of those groups.
For example, to add the groups MyAssets and DontTouchThis (both under All Assets) add
the following to the server.properties file:
#Exclude MyAssets and DontTouchThis from aging
asseet.aging.excluded.groups.uris=/All Assets/MyAssets,/All
Assets/DontTouchThis
Task to Disable Assets of a Certain Age
By default, asset aging is disabled. There is a new scheduled task that disables any
scanned asset that has reached the specified age. By default, once the assets aging feature
is turned on this task runs every day half an hour after midnight (00:30:00). Add the
following in the server.properties file to define asset aging:
#-----------------------------
# Asset aging
#-----------------------------
# Defines how many days can pass before a scanned asset is defined
as old
# after this time the asset will be disabled
# Default value: disabled
asset.aging.daysbeforedisable = -1
To Delete an Asset
To delete the asset instead of disabling it, you have to set the property
asset.aging.task.operation to delete in server.properties file:
# Delete assets when they age
asset.aging.task.operation = delete
Amortize Model confidence with scanned asset age
The IsScannedForOpenPorts and IsScannedForVulnerabilities sub-elements
in the ModelConfidence element are factored by the age of an asset. They are extended to
include an optional attribute, AmortizeScan. If AmortizeScan is not defined (or
defined with value -1), the assets are not amortized. A "new" asset gets the full value while
and "old" asset gets no points. You can edit the AmortizeScan value (number of days) in
the Manager’s /config/server/ThreatLevelFormula.xml file:
<ModelConfidence>
<Sum MaxValue="10" Weight="10">
<!-- If target Asset is unknown, clamp modelConfidence to 0 -
->
<HasValue FIELD="targetAssetId" Value="-10" Negated="Yes" />
<HasValue FIELD="targetAssetId" Value="4" Negated="NO" />
When setting the asset.aging.excluded.groups.uris property keep
in mind that the assets in this group are not disabled, deleted or amortized.

2 Configuration




<IsScannedForOpenPorts Value="4" Negated="NO" 
AmortizeScan="-1" />
<IsScannedForVulnerabilities Value="4" Negated="NO"
AmortizeScan="-1" />
</Sum>
</ModelConfidence>
For this example, the value is modified as follows:
Configuring Actors
Configuring the Actors feature requires a one-time setup procedure and minimal
maintenance if authentication systems are added, modified, or removed from your
network. This setup procedure maps the user authentication systems you use in your
network environment and the account IDs for each user on those systems.
1 Install the Actor Model Import connector appropriate for your IDM. For
complete instructions about how to install the connector, see the relevant
SmartConnector installation and configuration guide, such as the SmartConnector™
Configuration Guide for Microsoft Active Directory Actor Model. Once installed, the
connector polls the IDM and imports the user data into the Actor model.
2 Identify the authenticators in your environment. In preparation for configuring
the authenticator mapping table, open the dashboard for automatically identifying the
user authentication data stores running in your environment and their type:
/All Dashboards/ArcSight Administration/ESM/Configuration
Changes/Actors/Actor Administration
This dashboard is populated by the following query viewer, which looks for events with
a value in the Authenticator field: /All Query Viewers/ArcSight
Administration/ESM/Configuration Changes/Actor/Actor
Authenticators
The example below shows the value of the Attributes field for an active directory
system configured as Active Directory:<domain>.com. Use this exact value,
Asset Age 
(in days)
AmortizeScan Value
0 4
60 2
120 0
240 0

2 Configuration
including punctuation, spaces, and capitalization, to populate the account
authenticators mapping table described in the next step.
3 Configure the Authenticators mapping table. Using the information gathered in
step 2, fill out the account authenticators mapping table provided at /All Active
Lists/ArcSight System/Actor Data Support/Account Authenticators.
The data you enter here must exactly match the values displayed in the Actor
Administration dashboard.
a In the Navigator panel, go to Lists > Active Lists. Right-click the active list
/All Active Lists/ArcSight System/Actor Data Support/Account
Authenticators and select Show Entries.
b In the Account Authenticator Details tab in the Viewer screen, click the add icon
( ).
c For each account authenticator data store, enter the following data:
Column Description
Device Vendor The vendor that supplies the authentication data store,
such as Microsoft.
Device Product Provide the application name of the authentication
system, such as Active Directory.
Agent Address The IP address of the reporting SmartConnector.
Agent Zone
Resource
The zone in which the reporting SmartConnector
resides.
Authenticator Enter the exact value(s) returned for Authenticator in
the Actor Administration dashboard from the previous
step, including punctuation, capitalization, and spaces.
Using the example shown in the previous step, the
value you would enter in this column would be:
Active Directory: arcsight.com

2 Configuration
When you are finished, the Account Authenticators table should look something like
this:
Tuning Guide for Supporting Large Actor Models
If your actor model contains tens of thousands of members, follow the guidelines in this
section to allow adequate processing capacity for best results.
1 Shut down the Manager
2 Increase settings in server.properties. Increase the following default values
to support managing large blocks of actors by setting following properties in the
config/server.properties file:
3 Adjust Java Heap Memory Size in the arcsight managersetup utility.
Supporting 50,000 actors requires an additional 2 GB of Java heap memory in the
Manager. An additional 300 MB is needed for each category model you construct that
uses 50,000 actors. This additional memory is not in use all the time, but is needed for
certain operations.
For instructions about how to run the managersetup utility, see the Administrator’s
Guide.
4 Re-start the Manager.
5 Proceed with importing the actor model.
For details about starting and stopping the Manager, see “Basic Administration Tasks” in the
Administrator’s Guide
For details about working with the server.properties file, see “Managing and
Changing Properties File Settings” in the Administrator’s Guide.
Server Property
Name
Default
Setting
[units] Comments
dbconmanager.provider.oracle.pool.maxcheckout
600
[seconds]
The maximum time for a database connection before the
process is terminated.
This setting comes into play when you want to delete a large
block of actors from the ArcSight Console. The default value
should be increased by a factor of 3-6x, for example, 1800 to
3600.

2 Configuration
Permissions Required to Use Actors and Actor-Related
Data
By default, Admin users have full read/write access to the actors feature and the other
resources that actors depend on. The Admin can grant permissions for actors and the other
resources upon which the actors feature depends to other users.
To create actors, actor channels, and category models:
 Read and write on /All Actors
 Read and write on /All Session Lists/ArcSight System/Actor Data and
/All Session Lists/ArcSight System/Actor Data Support
 Read on /All Field Sets/ArcSight System/Actor Field Sets/Actor
Base
 Read on the filters used to define the event ACLS for that user group, for example,
All Filters/ArcSight System/Core
 Read and write on the group in which the new resource is being created
To view actors and category models, and monitor actor channels:
 Read on /All actors
 Read on /All Session Lists/ArcSight System/Actor Data and /All
Session Lists/ArcSight System/Actor Data Support
 Read on /All Field Sets/ArcSight System/Actor Field Sets/Actor
Base
To use actor global variables provided in standard content rules, active channels, and
reports that leverage actor data:
Read access on the following resources and groups:
 /All Fields/ArcSight System/Actor Variables (either directly, or inherited
from /All Fields/ArcSight System)
 /All Actors
 /All Session Lists/ArcSight System
 /All Active Lists/ArcSight System/Actor Data Support (for the
authenticator active list)
 /All Filters/ArcSight Foundation
 The appropriate group that gives all the queries used by a query viewer that leverages
actor data
 The appropriate group that contains a query viewer that leverages actor data
 The appropriate group(s) for the filters used by any queries and query viewers that
leverage actor data
In addition to these permissions on the actor-related resources themselves, read
permissions are needed for any resources (such as filters, user-created actor global
variables, and so on) upon which these actor-related resources rely.
Best practice: Log out and log back in again for permission changes
to take effect
As a best practice whenever an admin changes another user’s permissions,
the other user should log out and log back in again. This ensures that the new
permissions are registered with the Manager, and the user can see the
changes.

2 Configuration
For details about how to assign permissions to user groups, see “Granting or Removing
Resource Permissions” on page 659.
About Exporting Actors
If you need to export your entire actor model to image another Manager, you can do it
using the export_system_tables command-line utility using the -s parameter, the
parameter used to specify export of session list data. The -s parameter captures the
special session list infrastructure that is part of the Actor Resource Framework in addition
to the actor resources themselves.
For instructions about how to use the export_system_tables command-line utility, see
the Administrator’s Guide.

Chapter 3
Database Administration
This chapter describes the different tasks that you can perform in order to effectively
manage and maintain the ArcSight Database. The topics covered in this chapter include:
Changing Oracle Initialization Parameters
Almost all database parameters can be changed after an instance is created. Some of these
parameters are dynamic, whereas many others are static. You can change a dynamic
parameter while the instance is running. However, to change a static parameter, you have
to change its setting in the initialization parameter file and restart the database to have the
modified parameter setting take effect.
Changing these parameters is recommended only for experienced database administrators.
An instance created using an ArcSight template uses a binary version of the initialization
parameter file when the database starts up. The binary version (also known as SPFILE) is,
by default, on UNIX:
$ORACLE_HOME/dbs/spfile$ORACLE_SID.ora
and, on Windows:
“Changing Oracle Initialization Parameters” on page 93
“Monitoring Available Free Space in Tablespaces” on page 94
“Setting Up Database Threshold Notification” on page 94
“Resetting the Oracle Password” on page 94
“Oracle Cold Backup” on page 95
“Oracle Hot Backup” on page 95
“Exporting Data” on page 96
“Recovering ArcSight Databases” on page 96
“Backing up ArcSight Databases” on page 95
“Partition logs” on page 97
To enhance database security and lessen your risk and vulnerability, if you did
not use the ArcSight DB Installer to create and configure the ArcSight
Database, it is highly recommended that you change the default passwords for
the SYS and SYSTEM Oracle user accounts and lock the three accounts
DBSNMP, TRACESVR, and OUTLN. In addition, you should delete the following
automatically-created Oracle user accounts: ADAMS, BLAKE, CLARK, JONES,
and SCOTT. These accounts may have been generated by the Oracle installer.

3 Database Administration
%ORACLE_HOME%databaseSPFILE%ORACLE_SID%.ORA
The ArcSight Installer also generates a text version of the initialization parameter file (also
known as PFILE), which is, by default, on UNIX:
$ORACLE_HOME/admin/$ORACLE_SID/pfile/ini.ora
and, on Windows:
%ORACLE_HOME%..adminpfile%ORACLE_SID%.ora
When making changes to dynamic parameters, the binary initiation parameter file is
updated automatically. However, Oracle does not synchronize the text version with the
binary version automatically. Log in as SYS (use the command, arcdbutil sql and type
in / as sysdba when prompted for the user name) and run the following command to
update the text version:
CREATE PFILE='InitParamFilePath' FROM SPFILE
Where InitParamFilePath is the text version. After making changes to static
parameters by editing the text version, re-start the database. You log in as SYS (use the
command, arcdbutil sql and type in / as sysdba when prompted for the user
name) and run the following command to update the binary version:
STARTUP PFILE='InitParamFilePath';
If you have the full Oracle license, you can run the sql / as sysdba command directly
instead of using arcdbutil.
Without following these procedures, changes to either version are lost when the database
is re-started.
Monitoring Available Free Space in Tablespaces
Write scripts to alert when the file systems reach a threshold—say 85%. You can use
standard df -k command on Unix systems.
Setting Up Database Threshold Notification
The ArcSight Manager can be configured to automatically notify the administrator when an
ArcSight tablespace is nearly full. The default threshold setting is in the file
configserver.defaults.properties (under <ARCSIGHT_HOME> on the Manager
host):
databaseinfo.freespace.warning.threshold=5
This example reflects the default setting, which sends an alert when the amount of free
space in any of the ArcSight tablespaces for data or indexes falls to 5% or below.
To override the default threshold, copy this line from the read-only file
server.defaults.properties to server.properties and change the threshold
value.
Resetting the Oracle Password
Depending upon your Oracle settings, you may need to reset your password from time to
time. Oracle can be set to expire passwords, which lock out the ArcSight Manager. To reset

or renew the password for the ArcSight Database user (arcsight by default), log in to
Oracle with / as sysdba and run the following command:
ALTER USER arcsight IDENTIFIED BY ArcSightPassword ACCOUNT UNLOCK
Oracle database passwords must start with a letter followed by letters, digits, ‘_’, ‘#’, or ‘$.’
If you change the password for the ArcSight Database user, reconfigure the ArcSight
Manager and Partition Archiver to use the new password.
To reconfigure ArcSight Manager password, run the ArcSight Manager Configuration Wizard
by typing the following command in a command window on the Manager host in
<ARCSIGHT_HOME>bin:
arcsight managersetup
If you change the password for the ArcSight Database user, run the command 
arcsight database pc to update the password so that Partition Archiver can continue
to log in.
Backing up ArcSight Databases
Database backups are needed as insurance in case of database failure. There are two types
of Oracle database backup methods, cold backup and hot backup.
Oracle Cold Backup
Oracle Cold Backup means bringing down the Oracle database and backing up all the files
comprising the Oracle database. Until all database files are backed up/copied, the Oracle
database should remain closed. The advantage of a cold image backup is that it is a clean
consistent backup which when restored starts up Oracle to the status it was just before
going down. The other major advantage is, since it brings down Oracle, it initializes the
shared pool, data buffer cache and other memory structures.
Every week a cold Backup should be done by bringing down Oracle. This can be done at
the primary site or the remote site. If done on the primary site then irrespective of the
database size, the database has to be down for a maximum of 10 minutes before it is
started up if the Veritas database edition for Oracle is used.
Veritas’s Quick IO provides this functionality by taking a cold backup of the Oracle database
and mounting a read-only file system (Viz., /snap) which has only the changes to the
original database files. So even if the database is very large, it needs to be down only for a
short time before it is brought up.
Oracle Hot Backup
Oracle Hot Backup is also an image backup of Oracle database files. But it only includes
Oracle datafiles as part of its backup. This kind of backup is taken when the database is up
and running. The database has to be operating in archivelog mode before hot backup can
be done. This backup when restored needs a database recovery applied to it from the
online logs and archive logs after the database is mounted. Oracle tracks the changes
applied during the backup process by generating a lot of redo log files. An Oracle hot
backup should be done every day on the primary or target system.

Exporting Data
Along with these two backup methods, you should perform a full database export to
/dev/null, not as a substitute backup strategy but to guarantee that no blocks in the
database are corrupt. This is suggested since export is the only method to guarantee full
table scans of all the objects in the Oracle database.
Database events in initarcsight.ora can be set, but they signal corruption only when
such blocks are actually being accessed. Scheduling of these jobs is the job of the
Administrator on site. Jobs to be scheduled are:
 Analyze (compute/estimate statistics)
 Backups
 Export
 Any index rebuilds or defragmentation exercise
Recovering ArcSight Databases
Database recovery from system failures or disk crashes comprises recovering the database
to a consistent state by applying the archived logs. Thus, for the database to be able to
recovered, it has to be operating in ARCHIVELOG mode.
The default database behavior is to operate in NOARCHIVELOG mode so recovery is not
possible while operating in this mode. In case of a crash, the database has to be either
recreated (when the data is lost) or restored from a cold backup (when the transactions
that were applied to the database since the cold backup was done is lost).
All production databases should operate in ARCHIVELOG mode although there is an
overhead involved by way of archive log disk writes. Also in ARCHIVELOG mode you can
take hot backups (when the database is up and running) as opposed to cold backups
(when the database is down for the duration of the backup).
The process of recovering the ArcSight Database is no different than recovering any other
Oracle database. However, if you require assistance, you can contact your Customer
Support representative for advice and implementation strategies. If you are using your own
Oracle software license, contact Oracle.
Speeding up partition compression
Starting in ArcSight ESM v3.0 SP2 Patch2, the NOLOGGING option is disabled by default to
allow event data backup and use of DataGuard. As a result, redo log entries are generated
for all database operations (including data compression by Partition Compressor), making
the compression process appear somewhat slow.
If database backup is not required or DataGuard is not being used, you can speed up the
compression process by enabling the NOLOGGING option for Partition Compressor.
To enable the NOLOGGING option for Partition Compressor, add the following line to the
configserver.properties file:
partition.compress.exchange.table.logging=false

Partition logs
All log entries including the ones for the database partition utilities are written to the
server.log file on the ArcSight Manager. In addition, the partition entries are duplicated
to one of the following log files on the Manager:
partitionmanager.log—For Partition Manager logs
partitioncompressor.log—For Partition Compressor logs
partitionarchiver.log—For Partition Archiver logs
partitionstatisticsupdater.log—For Partition Statistics Updater logs
Entries in a duplicate log file are specific to a partition utility and are based on the log filters
defined in <ARCSIGHT_HOME>configserver.defaults.properties file for that
utility. These duplicate files enable you to easily browse the relevant information about a
partition utility. Additionally, these files are attached in e-mail notifications sent from the
partition management utilities.
Additional Partition Archiver logs are available on the ArcSight database machine. These
logs are more detailed than the ones available on the Manager and are duplicated to
<ARCSIGHT_HOME>logspartitionarchiver.log file on the database machine.
Unlike the duplicated Manager log files, this file is not sent in e-mail notifications.
For information about incomplete logs, see the Database section of the Troubleshooting
chapter in this guide.

Confidential ArcSight™ ESM User’s Guide 99
Chapter 4
Managing Resources
Some administrator tasks necessary to manage ArcSight ESM are performed in the ArcSight
Console. The details for performing such tasks are documented in the Online Help and also
in the ArcSight ESM User’s Guide. This chapter points you to the location where these tasks
are documented in the ArcSight ESM User’s Guide.
This chapter in ArcSight ESM
User’s Guide...
...discusses these topics
Chapter 24‚ Managing Users and
Permissions
• Managing Users
• Managing Permissions and Resources
• Managing Notifications
Chapter 27‚ Modeling the Network • Modeling the Network
• Working with Assets, Locations, Zones,
Networks, Vulnerabilities, and Categories
• Managing Customers
Chapter 10‚ Filtering Events • Creating Filters
• Moving or Copying Filters
• Deleting Filters
• Debugging Filters to Match Events
• Applying Filters
• Importing and Exporting filters
• Using Filter Groups
• Investigating Views
• Modifying Views

4 Managing Resources
100 ArcSight™ ESM User’s Guide Confidential
Chapter 25‚ Managing Resources • Managing File Resources
• Locking and Unlocking Resources
• Selecting Resources
• Finding Resources
• Visualizing Resources
• Viewing Resources in Grids
• Validating Resources
• Extending Audit Event Logging
• Saving Copies of Read-Only Resources
• Common Resource Attribute Fields
• Managing Packages
Chapter 26‚ Managing
SmartConnectors
• Selecting and Setting SmartConnector
Parameters
• Managing SmartConnector Filter Conditions
• Setting Special Severity Levels
• Sending Model Mappings to
SmartConnectors
• Sending Control Commands to
SmartConnectors
• Managing SmartConnector Groups
• Managing SmartConnector Resources
• Importing and Exporting SmartConnector
Configurations
• Upgrading SmartConnectors
Chapter 28‚ Managing Partitions • Getting Partition Information
• Seeing a Partition Schedule
• Archiving Partitions
• Reactivating Archived Partitions
• Reactivating Zipped or Large Archived
Partitions
• Deactivating Archived Partitions
• Running Scheduled Tasks Right Away
• Partition Properties
This chapter in ArcSight ESM
User’s Guide...
...discusses these topics

Appendix A
ArcSight Commands
This appendix provides information about ArcSight command scripts.
Running an ArcSight Command
To run an ArcSight command script on a component, open a command window and switch
to the <ARCSIGHT_HOME> directory. The arcsight commands run using the
arcsight.bat file in <ARCSIGHT_HOME>bin. The general syntax is as follows:
binarcsight <command_name> [parameters]
In general, commands that accept a path, accept either an path that is absolute or relative
to <ARCSIGHT_HOME>. Running the command from <ARCSIGHT_HOME> and prefixing
it with bin enables you to use the shell’s capabilities in looking for relative paths.
Alphabetical Commands List
ACLReportGen
agent logfu
agent tempca
agentcommand
agents
agentsetup
agentsvc
agenttempca
agentup
arcdbutil
arcdt
archive
archivefilter
archivewizard
bleep
bleepsetup
changepassword
checklist
console
consolesetup
database pc
database pm
database xts
databasesetup
dbcheck
dbview-generator
deploylicense
downloadcertificate
dropSLPartitions
exceptions
execproc
execprocsvc
export_system_tables
flexagentwizard
groupconflictingassets
idefensesetup
import_system_tables
keytool
keytoolgui
kickbleep
listsubjectdns
logfu
manager
managerinventory
manager-no-wrapper
manager-reload-config
managersetup
managerstop
managersvc
managerthreaddump
managerup
monitor
netio
package
portinfo
querytuner
reenableuser
refcheck
regex
replayfilegen
resetpwd
restorearchives
resvalidate
ruledesc
runcertutil
runmodutil
runpk12util
script
searchindex
sendlogs
tee
tempca
testdbconnection
threaddumps
tproc
uninstallservice
webserver
webserver-no-wrapper
webserversetup
webserversvc
websetup
whois

A ArcSight Commands
Command Descriptions
ACLReportGen
agent logfu
Description
A tool for generating a report on ACLs either at the group level or at
the user level. By default, the generated report is placed in the
/opt/arcsight/manager/ACLReports directory.
Applies to Manager
Syntax ACLReportGen [parameters]
Options
Optional:
-config <config>
-locale
-m <mode>
-pc
<privateConfig>
-h
The primary configuration file
(config/server.defaults.properties)
The locale to run under
Mode in which this tool is run to generate the
ACLs report. Supported modes are
• grouplevel
• userlevel
Default value is grouplevel
The override configuration file
(config/server.properties)
Help
Examples
To run this tool:
arcsight ACLReportGen
Description Graphical SmartConnector log file analyzer
Applies to SmartConnectors
Syntax agent logfu –a [options]
Options
-a SmartConnector log. Required.
For other options, see logfu command
(Manager)
Examples
To run logfu:
arcsight agent logfu –a

A ArcSight Commands
agent tempca
agentcommand
agents
Description
Inspect and manage temporary certificates for a SmartConnector
host machine
Syntax agent tempca
Options For options, see tempca command (Manager)
Examples
To run:
arcsight agent tempca
Description Send a command to SmartConnectors
Syntax agentcommand –c (restart | status | terminate)
Options -c Command: restart, status, or terminate
Examples
To retrieve status properties from the SmartConnector:
arcsight agentcommand –c status
To terminate the SmartConnector process:
arcsight agentcommand –c terminate
To re-start the SmartConnector process:
arcsight agentcommand –c restart
Description
Run all installed ArcSight SmartConnectors on this host as a
standalone application.
Syntax agents
Options None
Examples
To run all SmartConnectors:
arcsight agents

A ArcSight Commands
agentsetup
agentsvc
Description Run the SmartConnector Configuration Wizard
Syntax
agentsetup [-i <mode>] [-w] [-f <file>] [-g] [-t <type>]
[-sn <name>]
Options -a Show connectors for all platforms
-f <file> Properties file (required in –i silent mode)
-g Generate sample properties file for use in –i
silent mode
-h Get help on agentsetup command
-i <mode> Mode: silent, console, swing
-R Re-register an connector
-sn <name> Short Name
-t <type> SmartConnector Type (overrides short name)
-w Run in wizard mode
Examples
To run the SmartConnector Configuration Wizard:
arcsight agentsetup
Description Install ArcSight SmartConnector or Partition Archiver as a service.
Applies to SmartConnectors and Database
Syntax agentsvc –i –u <user>
Options -i Install the service
-u <user> Run service as specified user
Examples
To install a SmartConnector or Partition Archiver as a service:
arcsight agentsvc

A ArcSight Commands
agenttempca
agentup
arcdbutil
arcdt
Description See the agent tempca command
Description
Get the current state of a SmartConnector. Returns 0 if the
SmartConnector is running and reachable. Returns 1 if not
Syntax agentup
Options None
Examples
To check that the SmartConnector is up, running, and accessible:
arcsight agentup
Description
A utility that enables you to launch database utilities for operations
such as import, export, sql interface, backup, restore, and other
database commands
Applies to Database
Syntax arcdbutil <database_command> [command_options]
Options
<database_command> Possible commands include: sql, listener,
backup, recover, import, export, and other
database commands
[command_options] All valid options for the database command
you use
Examples
To identify all disabled rules in your current installation:
arcdbutil sql select name from arc_resource where id in
(select id from arc_rules where active=0);
To get an SQL interface:
arcdbutil sql
Enter user-name: / as sysdba
Description
A utility that enables you run diagnostic utilities such as session wait
times, thread dumps, and database alert logs about your ArcSight
system, which helps Customer Support analyze performance issues
on your ArcSight components
Applies to Manager

A ArcSight Commands
archive
Syntax arcdt diagnostic_utility utility_options
Options
diagnostic_utili
ty
Utilities you can run are:
• db-alertlog—Retrieve the database alert
log from the database machine.
• session-waits—Retrieve the currently
running JDBC (Java Database Connection)
sessions and their wait times.
Required Parameters:
-sp Flag specifying whether output should
be saved to disk or not.
Optional Parameters:
-c <count> The number of times we want
to query the various session tables. (5)
-f <frequency> The time interval (in
seconds) between queries to the session
tables. (20)
-fmt <format> The format the output
should be displayed in (where relevant),
choices are: html/text (text)
-o <outputfile> File name to save
output to. ()
• thread-dumps—Obtain thread dumps
from the Manager. Optional parameters
which can be specified
-c <count> The number of thread dumps
to request. (3)
-f <frequency> The interval in SECONDS
between each thread dump request. (10)
-od <outputdir> The output directory
into which the requested thread dumps
have to be placed. ()
help
help commands
help <command>
Use these help options (no dash) to see the
options, a list of commands, or help for a
specific command.
Examples
To retrieve the last 20 lines of database alert log from your database
machine and save it to a file called 20110720_dblog, run this
command:
arcsight arcdt db-alertlog -ln 20 -o 20110720_dblog
Description
Import or export resources (users, rules, and so on) to or from one
or more XML files.
Applies to Manager, Console
Syntax archive –f <archivefile> [options]

A ArcSight Commands
Options
-action <action> Possible actions include: diff, export,
i18nsync, import, list, merge, and sort.
Default: export.
-all Export all resources in the system (not
including events)
-base <basefile> The basefile when creating a migration
archive. The new archive file is specified with
–source (the result file is specified with –f)
-config <file> Configuration file to use. 
Default:
config/server.defaults.properties
-exportaction
<exportaction>
The action attribute to assign to each
resource object exported. Export actions are:
insert: Insert the new resource if it doesn’t
exist.
update: Update a resource if it exists.
remove: Remove a resource if it exists.
Default: insert
-f <archivefile> The input (import) or the output (export) file
specification. 
Note: Filename paths can be absolute or
relative. Relative paths are relative to
<ARCSIGHT_HOME>, not the current directory.
Required
-format <fmt> Format of the archive: preferarchive,
force, interactive, overwrite or skip.
Default: default.
default: Prompts user to resolve import
conflicts.
force: Conflicts are resolved by the new
overwriting the old.
overwrite: Merges resources, but does not
perform any union of relationships.
preferarchive: Merges resources. For
example, if a group is imported, the resulting
group contains all its original members and all
of the new members from the import file.
skip: Do not import resources with conflicts.
-h Get help for this command
-i (Synonym for –action import.)
-m <manager> The ArcSight Manager to communicate with

A ArcSight Commands
-newids All archival objects within an archive are given
new IDs. All refs to these archival objects are
changed to the new ID or removed if not
found. This option is useful when an archive is
created and then all resources in the archive
are modified to create new resources but the
IDs were retained
-o Overwrite any existing files
-optimizedimport Performs pre-processing during import for
optimization. Forces the import of values even
though they are the same as what is stored in
the database. If this flag is not set, each of
the values in the archive is compared with the
value in the database to determine whether
any changes have been made; if no changes
are found, then the import for that object is
skipped
-p <password> Password with which to log in to the Manager
-param
<paramfile>
The source file for parameters. Any
parameters in the paramfile can be overridden
by command line values
-pc <configfile> Private configuration file to override –config.
Default: config/server.properties
-pkcs11 Use this option when authenticating with a
PKCS#11 provider. For example,
arcsight archive -m <hostname> -pkcs11
-f <file path>
-port <port> The port to use for Manager communication.
Default: 8443
-q Quiet: do not output progress information
while archiving
-source
<sourcefile>
The source file used when –f specifies an
output file
-standalone Operate directly on the Database, not the
Manager.
Warning: Do not run archive in –standalone
mode when the Manager is running; database
corruption could result.
-u <username> The user name to log in to the Manager with
-uri
<ncludeURIs>
The URI(s) to export. No effect during import.
All dependent resources are exported, as
well—for example, all children of a group.
Separate multiple URIs (such as “/All
Filters/Geographic/West Cost”) with a
space, or repeat the –uri switch
-urichildren
includes
The parent URI(s) to export. No effect during
import. All child resources of the specified
resources are exported. The parent resources
are only exported if there is a dependency

A ArcSight Commands
-xrefids Exclude reference IDs. This option determines
whether to include reference IDs during
export. This is intended only to keep changes
to a minimum between exports. Do not use
this option without a complete understanding
of its implications
-xtype
<excludeTypes>
The type(s) to exclude during export. No
effect during import. Exclude types must be
valid type names, such as Group, Asset, or
ActiveChannel
-xtyperef
<excludeTypes>
Same as the –xtype option, but also excludes
all references of the specified type
-xuri
<excludeURIs>
The URI(s) to exclude during export. No effect
during import. Resources for which all
possible URIs are explicitly excluded are not
exported. Resources which can still be
reached by a URI that is not excluded are still
exported
-xurichildren
<excludes>
The parent URI(s) to exclude during export.
No effect during import. Resources for which
all possible URIs are explicitly excluded are
not exported. Resources which can still be
reached by a URI that is not excluded are still
exported.
Examples
To import resources from an XML file (on a Unix host):
arcsight archive –action import –f
/user/subdir/resfile.xml
To export certain resources (the program displays available
resources):
arcsight archive –f resfile.xml –u admin –m mgrName –p pwd
To export all resources to an XML file in quiet, batch mode:
arcsight archive –all –q –f resfile.xml –u admin –m
mgrName p password
To export a specific resource:
arcsight archive –uri “/All Filters/Geographic/West Coast”
f resfile.xml
Manual import (program prompts for password):
arcsight archive –i –format preferarchive –f resfile.xml –
u admin m mgrName
Scheduled or batch importing:
arcsight archive –i –q –format preferarchive –f
resfile.xml –u admin –m mgrName p password
Scheduled or batch exporting:
arcsight archive –f resfile.xml –u admin –m mgrName p
password uri “/All Filters/Geographic/East Coast” –uri
“/All Filters/Geographic/South”

A ArcSight Commands
archivefilter
Description
Use the command to change the contents of the archive. The
archivefilter command takes a source archive xml file as input,
applies the filter specified and writes the output to the target file.
Applies to Manager
Syntax
archivefilter –source <sourcefile> –f <archivefile >
[options]
Options
-a <action> Action to perform {insert, remove, none}
(Default: none)
-e
<element_list>
Elements to process (Default: ‘*’ which
denotes all elements)
-extid <regex> Regular expression to represent all of the
external IDs to include. This is the external ID
of the archival object. (Default: none)
-f <file> Target file (required). If a file with an identical
name already exists in the location where you
want to create your target file, the existing
file is overwritten. If you would like to receive
a prompt before this file gets overwritten, use
the –o option
-o Overwrite existing target file without
prompting (Default: false)
-relateduri
<regex>
Regular expression to get all of the URIs
found in references to include. This checks all
attribute lists that have references and if any
of them have a URI that matches any of the
expressions, that object is included
-source <file> Source file (required)
-uri <regex> Regular expression to represent all of the
URIs to include. This is the URI of the archival
object
-xe
<element_list>
Elements to exclude
-xextid <regex> Regular expression to represent all of the
external IDs to exclude
-xgroups
<groups>
Groups to exclude
-xuri <regex> Regular expression to represent all of the
URIs to exclude
-h Help for this command

A ArcSight Commands
archivewizard
bleep
Examples
To include any resources, for example all Active Channels, whose
attributes contain the URI specified by the –relateduri option:
arcsight archivefilter -source allchannels.xml -f t0.xml -
relateduri "/All Active Channels/ArcSight
Administration/"
To include any resources whose parent URI matches the URI
specified by the –uri option:
uri "/All Active Channels/ArcSight Administration/.*"
To exclude resources whose parent URI matches the URI specified
by the –xuri option:
xuri "/All Active Channels/.*"
To include all the resources that contain either URIs specified by the
two –relateduri options:
arcsight archivefilter -source allchannelsFilter.xml -f
t0.xml -relateduri "/All Active Channels/ArcSight
Administration/" -relateduri .*Monitor.*
Description Archive wizard
Applies to Manager
Syntax archivewizard
Options None
Examples
To run:
arcsight archivewizard
Description
Unsupported stress test command to supply a Manager with security
events from replay files (see replayfilegen). Replay files
containing more than 30,000 events require a lot of memory on the
bleep host.
Do not run bleep on the Manager host. Install the Manager on the
bleep host and cancel the configuration wizard when it asks for the
Manager’s host name.
Run arcsight tempca –ac on the bleep host if the Manager under
test is using a demo certificate.
Create the file config/bleep.properties using the descriptions in
bleep.defaults.properties.
Applies to Manager
Syntax bleep [-c <file>] [-D <key>=<value> [<key>=<value>…]]

A ArcSight Commands
bleepsetup
changepassword
Options
-c file Alternate configuration file (default:
config/bleep.properties)
-D <key>=<value> Override definition of configuration properties
-m <n> Maximum number of events to send. (Default:
-1)
-n <host> Manager host name
-p <password> Manager password
-t <port> Manager port (Default: 8443)
-u <username> Manager user name
-h Display command help
Examples
To run:
arcsight bleep
Description Wizard to help create the bleep.properties file
Applies to Manager
Syntax bleepsetup
Options -f Properties file (silent mode)
-i Mode: {swing, console, recorderui, silent}
Default: swing
-g Generate sample properties file
Examples
To run:
arcsight bleepsetup
Description
Command to change obfuscated passwords in properties files. The
utility prompts for the new password at the command line
Applies to Manager
Syntax changepassword –f <file> –p <property_name>
Options
-f <file> Properties file, such as
config/server.properties
-p
<property_name>
Password property to change, such as
server.privatekey.password

A ArcSight Commands
checklist
console
Examples
To run:
arcsight changepassword
Description
ArcSight Environment Check. Used internally by the installer.
Right JRE, supported OS, connected to supported Database,
Can run from Connector, Database, or Manager.
Description Run the ArcSight Console
Applies to Console
Syntax console [-i] [options]
Options -ast <file>
-debug
-i
-imageeditor
-laf <style> Look and feel style: metal, plastic, plastic3d
-p <password> Password
-port Port to connect to Manager (default: 8443)
-redirect
-relogin
-server Manager host name
-slideshow
-theme
-timezone <tz> Timezone: such as “GMT” or “GMT-8:00”
-trace Log all Manager calls
-u <name> User name
Examples
To run the console:
arcsight console

A ArcSight Commands
consolesetup
database pc
Description
Run the ArcSight Console Configuration Wizard to reconfigure an
existing installation
Applies to Console
Syntax consolesetup [-i <mode>] [-f <file>] [-g]
Options -i <mode> Mode: console, silent, recorderui, swing
-f <file> Log file name (properties file in –i silent
mode)
-g Generate sample properties file for –i silent
mode
Examples
To change some console configuration options:
arcsight consolesetup
Description Partition configuration command
Applies to Database
Syntax database pc
Options -d <db_type> Database type: oracle, db2
-i <mode> Mode: silent
-f <file> Properties filename. Required in –i silent
mode
-g Generate the SQL scripts
-s Generate a sample properties file for use in –i
silent mode
-x Execute the existing SQL scripts
-p Run this command in expert mode.
If the statistics updates are timing out and the
event rate is very high, then the sample size
should be reduced to 0.1. Using the -p option
with this command opens the wizard and
allows you to change the sample size.
Examples
To configure your database partition:
arcsight database pc

A ArcSight Commands
database pm
database xts
Description Partition management command
Applies to Database (Partition Manager)
Syntax database pm
Options
-cn <name> This is a required parameter.
Name of command you want to issue on the
Partition Manager. One of:
• manage
• compress
• update
-c <config> The default configuration file to use
(config/server.defaults.properties)
-i <mode> The invocation mode. Use one of:
• remote
• standalone
-m <name> The hostname or IP address of the ArcSight
Manager
-p <password> The admin password for ArcSight Manager
-pc <file> The custom configuration file to use
(config/database.properties)
-pn <name> name of partitions for which statistics are to
be updated
-port <port> port number of ArcSight Manager (8443)
-u <user-name> The admin user name for ArcSight Manager
(usually admin)
-h help. Get help for this command
Examples
arcsight database pm -cn Manage -m linux53_64_45sp3 -u
admin -p arcsight
Description
Extend the ArcSight Database Tablespaces. (This is a convenience
tool; If you have the full Oracle license, you can optionally use
Enterprise Manager or SQL*Plus.)
Applies to Database
Syntax database xts
Options None

A ArcSight Commands
It is better to run this command locally on the machine that hosts the database. If you run
it remotely, the wizard does not allow you to browse the remote directlory and it cannot
validate diskspace availability before it expands the tablespace. If you run it locally it does
both.
databasesetup
dbcheck
dbview-generator
Examples
To extend your database space:
arcsight database xts
Description
Runs the ArcSight database installer. This installer is documented in
the “Installing ArcSight Database” chapter of the ESM Installation
and Configuration guide.
Applies to Database
Syntax databasesetup
Options None
Examples
To run the database installation:
arcsight databasesetup
Description
Gathering information and statistics about the current ArcSight
Database instance, such as the data to index size ratio
Applies to Database
Syntax dbcheck
Options None
Examples arcsight dbcheck
Description
Utility that generates database views based on the fields of a
fieldset. Field sets are named subsets chosen from the available
attributes of an event. To create a new field set or to see the existing
ones, go to the Active Channels resource tree and click the Field
Sets tab
Applies to Manager, Database
Syntax
dbview-generator –f <fieldset> –m <manager> –n <view_name>
–p <password> –u <user_name>
Options
-f <fieldset> URI of the fieldset from which you want to
generate the database view
-m <manager> Name of the Manager

A ArcSight Commands
deploylicense
downloadcertificate
-n <view_name> Name for the view
-u <user_name> User name to connect to the Manager
-p <password> Password for the user_name
Examples
To generate a database view containing fields in the Standard field
set:
arcsight dbview-generator –f “/All Field Sets/ArcSight
System/Active Channels/Standard” –m mymanager –n
dv_view_standard –p mypassword –u myuser
To retrieve the data from the view you generated run the following
command in SQL:
select * from db_view_standard
Description
Install a new ArcSight license file. The Manager may be running; it
detects the new license file automatically
Applies to Manager
Syntax deploylicense file
Options
mode)
mode
-i <mode> Mode: console, silent, recorderui, swing
Examples
To deploy a new license:
arcsight deploylicense
Description Wizard for importing certificates
Applies to Manager
Syntax downloadcertificate
mode)
mode
Examples
To run:
arcsight downloadcertificate

A ArcSight Commands
dropSLPartitions
exceptions
Description Command for dropping old Session List partitions
Applies to Database
Syntax dropSLPartitions
Options -d <days> Number of days to retain data
-m <manager> The ArcSight Manager to communicate with
-p <password> (Optional) The password to log in with
-u <username> The user name used for logging in
-p <port> (Optional) The port used for communication
(8443 by default)
-h (Optional) Get help for this command
Examples
To run:
arcsight dropSLPartitions
Description Search for logged exceptions in ArcSight log files
Applies to Manager, Console, SmartConnectors
Syntax
exceptions logfile_list [options] [path to the log file]
The path to the log file must be specified relative to the current
working directory.
Options
-x Exclude exceptions/errors that contain the
given string. Use @filename to load a list from
a file.
-i Include exceptions/errors that contain the
given string. Use @filename to load a list from
a file.
-r Exclude errors.
-q Quiet mode. Does not display
exceptions/errors on the screen.
-e Send exceptions/errors to the given email
address.
-s Use a non-default SMTP server. Default is
bynari.sv.arcsight.com.
-u Specify a mail subject line addition, that is,
details in the log.
-n Group exceptions for readability.

A ArcSight Commands
execproc
execprocsvc
-l Show only exceptions that have no
explanation.
-p Suppress the explanations for the exceptions.
Example
To run:
arcsight exceptions
/opt/home/arcsight/manager/logs/default/server.log*
Description
Process Executor tool. Used on Unix platforms to execute shell
commands
Applies to Manager
Syntax execproc
Options None
Examples
To run:
arcsight execproc
Description Start or stop the Process Executor as a service
Applies to Manager
Syntax
execprocsvc cmd [-wrapperConfig <file>] [initialHeap
maxHeap]
Options -c Console mode
-i Install service
initialHeap Initial heap memory size, in MB. (Default:
128)
maxHeap Maximum heap memory size, in MB. (Default:
512)
-q Stop service (quit)
-r Remove service
-s Start service
-wrapperConfig
<file>

A ArcSight Commands
export_system_tables
flexagentwizard
Examples
To install a process called ‘proc:’
arcsight execprocsvc proc –i
To run the installed process with a maximum of 1GB of memory:
arcsight execprocsvc proc –s 128 1024
Description
Command to export your database tables. Upon successful
completion the utility generates two files: a temporary parameter
file and the actual database dump file,
arcsight_dump_system_tables.sql, which is placed in the
database’s <ARCSIGHT_HOME>/tmp.
Applies to Manager
Syntax export_system_tables <username> <password> <DBname>
Options <username> Oracle database username
<password> Password for the Oracle database user
<DBname> Name specified in tnsnames.ora for the
database from which you are exporting the
system tables
-s include session list tables
Examples
To run:
arcsight export_system_tables
<username>/<password>@<DBname>
arcsight export_system_tables <ArcSight username>
<ArcSight password> <DBname>
Note: 
When running the export_system_tables command, you may see an
warning message in your command prompt or shell console window
saying “Exporting questionable statistics”. You can safely
ignore this warning. This warning occurs when you export the table
data with its related optimizer statistics and Oracle cannot verify the
validity of these statistics.
If you are using ESM v5.0 SP1 patch 2 on an Oracle 10.2.0.4 database, you
might get the following error message.
"ORA-39071: Value for TABLES is badly formed."
Check to see if your Oracle compatibility is set to 10.2.0.1. If it is, set it to
10.2.0.4 and try again.
Description Wizard-like command to generate simple ArcSight FlexConnectors

A ArcSight Commands
groupconflictingassets
idefensesetup
Syntax flexagentwizard
Options None
Examples
To run:
arcsight flexagentwizard
Description
Tool that groups asset resources with common attribute values.
Group Conflicting Attribute Assets Tool. Assets can have conflicting
IP addresses or host names within a zone
Applies to Manager
Syntax groupconflictingassets
Options
-c Clean (delete the contents of) the group to
receive links to assets before starting.
(Default: false)
-m <host> Manager host name or address
-o <name> Name for group to receive links to assets
which have conflicting attributes. (Default:
“CONFLICTING ASSETS”)
-port <n> Port to connect to Manager (Default: 8443)
-prot <string> Protocol { http | https } (Default: https)
-user <name> User name
Examples
To run:
arcsight groupconflictingassets
Description Wizard to configure iDefense appliance information on the Manager
Applies to Manager
Syntax idefensesetup
Options -f <logfilename> Optional properties file name (silent mode)
-i <mode> Mode: swing, Console, recorderui, or silent
-g Generate sample properties file for silent
mode

A ArcSight Commands
import_system_tables
keytool
-h Help
Examples
To launch the iDefense Setup wizard:
arcsight idefensesetup
Description
Command to import database tables. The file you import from must
be the one that export_system_tables utility created. This utility looks
for the dump file, arcsight_dump_system_tables.sql, in the
database’s <ARCSIGHT_HOME>.
Syntax
import_system_tables <old_user> <new_user> <password>
<TNSname> <dump_file_path> <dump_file_name>
Options
<old_user> The database username that was used to
export system tables using the
export_system_tables command.
<new_user> The database username of the database to
which you are importing system tables
<password> Password for <new_user>
<TNSname> Name specified in tnsnames.ora for the
database to which you are importing the
system tables
<dump_file_path> Absolute path or relative path from
<ARCSIGHT_HOME>
<dump_file_name> Name of the dump file you plan to import
Examples
To run:
arcsight import_system_tables <old_user> <new_user>
<password> <TNSname> <dump_file_path> <dump_file_name>
Description Runs Java Runtime Environment keytool utility to manage key stores
Applies to Manager, Console, SmartConnectors
Syntax keytool –store <name>
Options
-store <name> (Required) Specific store {managerkeys |
managercerts | clientkeys | clientcerts |
ldapkeys | ldapcerts | webkeys | webcerts }
(original options) All options supported by
the JRE keytool utility are passed along. Use
arcsight keytool

A ArcSight Commands
keytoolgui
kickbleep
listsubjectdns
–help For a list of options and arguments. Also, use
the command keytool without arguments or
the arcsight prefix for more-detailed help.
Examples
To view Console key store:
arcsight keytool –store clientkeys
Description
Graphical user interface command for manipulating key stores and
certificates
Applies to Manager, Console
Syntax keytoolgui
Options None
Examples
To run:
arcsight keytoolgui
Description Runs a simple, standardized test using the bleep utility
Applies to Manager
Syntax kickbleep
Options -f Properties file (silent mode)
-g Generate sample properties file
-i Mode: {swing, console, recorderui, silent}
Default: swing
Examples
To run:
arcsight kickbleep
Description Display subject distinguished names (DN) from a key store
Applies to Manager, SmartConnectors
Syntax listsubjectdns
Options
-store name Specific store { managerkeys | managercerts
| clientkeys | clientcerts | ldapkeys |
ldapcerts} (Default: clientkeys.)

A ArcSight Commands
logfu
manager
Examples
To list Distinguished Names in the Console key store:
arcsight listsubjectdns
Description Graphical tool for analyzing log files.
Applies to Manager (See also agent logfu.)
Syntax logfu {-a | -c | -m} [options]
Options -a Analyze SmartConnector logs
-c Analyze Console logs
-f <timestamp> From time
-i Display information about the log files to be
analyzed
-l <timespec> Analyze only the specified time (Format:
<time>{smhd}) Examples: 1d = one day, 4h
= four hours
-m Analyze Manager logs
-mempercent <n> Percent of memory messages to consider for
plotting. (Default: 100)
-noex Skip exception processing
-noplot Skip the plotting
-t <timestamp> To time
Examples
To analyze Manager logs for the last 12 hours:
arcsight logfu –m –l 12h
Description Runs the ArcSight Manager in command line mode (not as a service)
Applies to Manager
Syntax manager
Options None
Examples
To run the ArcSight Manager:
arcsight manager

A ArcSight Commands
managerinventory
manager-no-wrapper
manager-reload-config
Description Display configuration information about the installed Manager
Applies to Manager
Syntax managerinventory
Options -a <filter> Attribute filter. Default: "*"
-f <filter> Object filter. Default: "Arcsight:*"
-o <op> Operation {list, show}. Default is list
-out <file> Output filename. Default is stdout
-port <n> Port to connect to Manager (Default: 8443)
-prot <string> Protocol { http | https } (Default: https)
-u <name> User name
-append Append to the output file rather than create a
new one and overwrite any existing one
-sanitize Sanitize the IP addresses and host names
-h Get help for this command
Examples
To run:
arcsight managerinventory
Description
Run the Manager without automatic restart in case of fatal errors.
(See manager for options.)
Applies to Manager
Syntax manager-no-wrapper
Options None
Examples
To run the manager without automatic restart:
arcsight manager-no-wrapper
Description
Load the server.defaults.properties and server.properties
files on the Manager

A ArcSight Commands
managersetup
managerstop
Applies to Manager
Syntax arcsight manager-reload-config
Options
-diff Displays the difference between the
properties the Manager is currently using and
the properties that this command loads
-as Forces the command to load properties that
can be changed without restarting the
Manager. The properties that require a
Manager restart are updated in the
server.properties but are not effective until
the Manager is restarted
-t <seconds> Number of seconds after which the manager-
reload-config command stops trying to load
the updated properties file on the Manager
Examples
To reload config:
arcsight manager-reload-config
To view the differences between the properties the Manager is
currently using and the properties that this command loads:
arcsight manager-reload-config -diff
Description Run the ArcSight Manager Configuration Wizard
Applies to Manager
Syntax managersetup –i console
mode)
mode
Examples
To run:
arcsight managersetup
Description
Stop the ArcSight Manager whether it is in service or command line
mode
Applies to Manager
Syntax managerstop
Options None

A ArcSight Commands
managersvc
managerthreaddump
managerup
Examples
To stop the Manager service:
arcsight managerstop
Description
Start, stop, install, or uninstall the ArcSight Manager as a service.
Note: The start option does not work on Windows. To start Manager
as a service on Windows, follow instructions in Chapter 1‚ Basic
Administration Tasks‚ on page 9.
Applies to Manager
Syntax managersvc {start | stop | restart | status | dump}
Options None
Examples
To start the Manager service (only on non-Windows platforms):
arcsight managersvc start
Description Script to dump the Manager's current threads
Applies to Manager
Syntax managerthreaddump
Options None
Examples
To run:
arcsight managerthreaddump
Description
Get the current state of the Manager. Returns 0 if the Manager is
running and reachable. Returns 1 if not
Applies to Manager
Syntax managerup
Options None
Examples
To check that the Manager is up, running, and accessible:
arcsight managerup

A ArcSight Commands
monitor
netio
Description Tool used in conjunction with Network Management Systems
Applies to Manager
Syntax monitor
Options -a <filter> Attribute filter. Default: "*"
-append Append to output file instead of overwriting
(Default: false)
-f <filter> Object filter. Default: "Arcsight:*"
-o <op> Operation {list, show}. Default is list
-out <file> Output filename for management service
information. Default is stdout
-p <pwd> Password
-sanitize Sanitize IP address and host names (Default:
false)
-u <name> User name
Examples
To run:
arcsight monitor
Description Primitive network throughput measurement utility
Applies to Manager
Syntax netio
Options -c Client mode (Default: false)
-n <host> Host to connect to (Client mode only)
-p <port> Port (Default: 9999)
-s Server mode
Examples
To run:
arcsight netio

A ArcSight Commands
package
Description
Import or export resources (users, rules, and so on) to or from one
or more XML files.
Use this command instead of the archive command.
Note: Some functionality for this command are available from the
GUI only.
Applies to Manager, Database, Console
Syntax
package –action <action-to-be-taken> -package <package
URI> -f <package-file>
Options
- action
<action>
Creates a new package based upon one or
more packages that you specify. The possible
actions include bundle, convertarchives,
export, import, install, uninstall. The
default is export
-config <file> The primary configuration file to use. Default
is config/server.defaults.properties
-convertbaseuri
<baseuri>
The base URI for packages that are converted
from archives. This option is only used in
conjunction with the –action
convertarchives option
-f <path> The location of the package bundle file. File
name paths can be absolute or relative.
Relative paths are relative to
<ARCSIGHT_HOME>
-m <manager> The Arcsight Manager to communicate with
-p <password> (Optional) The password with which to log in
to the Manager
-package
<packagerefs>
The URI(s) of the package(s). This option is
used in conjunction with –action install
and –action uninstall in order to list which
packages to operate upon
-pc
<privateConfig>
This configuration file overrides the
server.defaults.properties file. The
default location is
config/server.properties
-pkcs11 Use this option when authenticating with a
PKCS#11 provider. For example,
arcsight package -m <hostname> -pkcs11
-f <file path>
-port <port> The port to use for communication. The
default port used is 8443
-source
<sourcefile>
The source file. This is used in conjunction
with the –f command which specifies an
output file
-u <username> The user name used for logging in to the
Manager

A ArcSight Commands
portinfo
-standalone Operate directly on the Database not the
Manager
Examples
To convert a previously archived package:
arcsight package –action convertarchives –convertbaseuri
“/All Packages/Personal/Mypackage” –source sourcefile.xml
–f packagebundle.arb
To install a package:
arcsight package –action install –package “/All
Packages/Personal/Mypackage” –u username –p password –m
managername
To uninstall a package:
arcsight package –action uninstall –package “/All
Packages/Personal/Mypackage” –standalone –config
/config/server.defaults.properties –pc
/config/server.properties
To import a package through the Manager:
arcsight package –action import –f packagebundle.arb –u
username –p password –m managername
To export a package:
arcsight package –action export –package “/All
Packages/Personal/Mypackage” –f packagebundle.arb –u
To export multiple packages:
Packages/Personal/PackageOne” –package “/All
Packages/Personal/PackageTwo” –f packagebundle.arb –u
To export packages in a standalone mode (directly from the
database) Make sure that the ArcSight Manager is not running:
Packages/Personal/Mypackage” –f packagebundle.arb –u
username –p password –standalone –config
server.default.properties –pc server.properties
To combine xml files from multiple packages into one package:
arcsight package -action bundle -f myPkgNew.arb -source
chnpkg.xml -source filterpkg.xml -source rulepkg.xml
In the above example, chnpkg.xml, filterpkg.xml, and
rulepkg.xml files are extracted from their respective packages and
are bundled in one package bundle called myPkgNew.arb.
Description
Script used by the portinfo tool of the Console. Displays common
port usage information for a given port
Applies to Console
Syntax portinfo port

A ArcSight Commands
querytuner
Options
port Port number
Examples
To run:
arcsight portinfo
Description
A troubleshooting tool that generates explain plans for all queries
within ArcSight ESM, and helps evaluate whether hints may improve
the performance of some queries. This tool pulls explain plans for all
the queries used by reports and trends and looks for ones that can
execute inefficiently without database hints.
All findings are logged in the file Manager's
<ARCSIGHT_HOME>/logs/query-tuner.log.
Run this tool from the Manager’s bin directory either in a standalone
mode (without the Manager running) or you can run it while the
Manager is running.
Applies to Database, Manager, Console
Syntax arcsight querytuner -m analyze -uri <uri_for_the_query>
Options -m analyze To analyze a query
-d
<query_duration>
Optional parameter. query_duration is the
time duration, for example, 1h, 2h, 1d, to be
used while running the queries
-t <timeout> Optional parameter. timeout is the number
of seconds after which a slow running query
will timeout. If you provide this value,
performance is measured if and when a good
hint is found
-uri <uri> Optional parameter. uri is the URI of the
query
-h Help for this command, for example,
./arcsight querytuner -h

A ArcSight Commands
Examples
To analyze all the queries
arcsight querytuner –m analyze
To analyze all queries and measure performance if a hint helps, -t is
the timeout to be used while executing the query:
arcsight querytuner -m analyze -t 300000
To analyze a single query:
arcsight querytuner -m analyze -uri <uri_for_the_query>
For example,
arcsight querytuner -m analyze -uri "/All Queries/ArcSight
Foundation/Intrusion Monitoring/Executive Summaries/Business
Role/Business Role - Successful Attacks"
This tells you if any hint may potentially help. You should see the
message "Hint that Helped=<the_actual_hint>" in the query-tuner.log
file to look for a hint that might potentially help.
Open the query-tuner.log file. For every Query at the end of the
query report look for the keyword “hasBadPattern=true” followed by
"Hint that Helped=<the_actual_hint>" or sometimes you see “No hints
could be found for this pattern.”
Please contact Customer support when you see “hasBadPattern=true”
followed by “No hints could be found for this pattern.” Be prepared to
provide the querytuner log and the package export of the query.
Once you run the Query Tuner tool and see that a hint has helped for a
particular query, you can install the hint on the Manager from the
ArcSight Console. Refer to the Console’s online help for information on
how to do so.
Applying a
Hint to a
Query
Note: Please contact Customer Support before applying any hints
received by running the Query Tuner.
Once you run the Query Tuner tool and see that a hint has helped for a
particular query, you can add the hint to the query as follows:
1 In the Console's
<ARCSIGHT_HOME>/current/config/console.properties file, set
the following property:
database.hint.editable=true
2 Restart the Console if it is running.
3 Open the query-tuner.log file located in the Manager's
<ARCSIGHT_HOME>/logs directory.
4 Scan through the file and locate the query URI. Copy the actual hint
in the line "Hint that Helped=<the_actual_hint>" located below
the query URI. Make sure not to copy the words “Hint that
Helped=”
5 In the ArcSight Console Navigator, open the Reports resource.
6 Click on the Queries tab to bring it forward.
7 Follow the URI for the query for which you want to apply the hint,
right-click it and select Edit Query.
8 In the Inspect/Edit panel, paste the hint you copied in Step 4 in the
Database Hint box (the actual hint).

A ArcSight Commands
reenableuser
refcheck
regex
replayfilegen
Description Re-enable a disabled user account
Applies to Manager
Syntax reenableuser <username>
Options <username> The name of the user resource to re-enable
Examples
To re-enable a disabled user:
arcsight reenableuser <username>
Description Resource reference checker
Applies to Manager
Syntax refcheck
Options None
Examples
To run:
arcsight refcheck
Description Graphical tool for regex-based FlexConnectors
Syntax regex
Options None
Examples
To run:
arcsight regex
Description
Wizard for creating security event data files (“replay files”) that can
be run against a Manager for testing, analysis, or demonstration
purposes.
Note: This is a client side command only and should executed from
the Console’s ARCSIGHT_HOME/bin directory.
Applies to Console
Syntax replayfilegen –m mgr [options]

A ArcSight Commands
resetpwd
restorearchives
Options
mode)
mode
Examples
Run from the Console’s <ARCSIGHT_HOME>/bin directory:
arcsight replayfilegen
To run in console mode:
arcsight replayfilegen –i console
Description
Wizard to reset a user’s password and optionally notify the user of
the new password by e-mail
Applies to Manager
Syntax resetpwd
Options
mode)
mode
Examples
To reset a user’s password:
arcsight resetpwd
Description
This tool allows you to load archives from an older ArcSight Express
installation to a new one. The loaded archives from the older
installation are loaded as archives in DEACTIVATED state. By
activating them, you can load the events and search through them as
you would for an archive that was done from the newer installation.
The system does not differentiate between the archives loaded from
a different installation and the ones created daily locally.
Notes:
• If you override the archive root path, then the files are not copied
over to the default archive location. Hence deleting those files
makes the archive unusable. The space used by these archive is
not shown in the "Archive Jobs" administration page.
• Loading events from two installations to the local installation is
not recommended.
Applies to Database

A ArcSight Commands
resvalidate
Syntax
/opt/arcsight/logger/current/arcsight/bin/arcsight
restorearchives
Options
-r <root> Optional Parameter.
The root of the directory that contains all
archives to be imported. All archives should
be sub-directories of this directory. If
unspecified the tool loads archives from the
default archive location,
/opt/arcsight/logger/data/archives
-i interactive Interactive mode. Confirmation is required
before loading each archive. Use this mode to
selectively load a subset of the archives.
-t test This option helps you validate the archives
without actually loading them into the
database.
-C clear Clears all events and archives from the
database, and then load the archives. This is
required when the events loaded from a
different ArcSight Express appliance clashes
with the events present in the local appliance.
This is useful when the tool skips some
archives because of event ID clash, or archive
clash. This tool removes all events and
archives from the local installation. Therefore,
this option is most useful for a fresh ArcSight
Express installation.
-h help Help for this command
Examples
To run:
arcsight restorearchives -C
Description
Utility for checking whether there are any invalid resources in the
database. The utility generates two reports called validationReport
(with .xml and .html extensions) that are written to the directory
from which you run the resvalidate command
Syntax resvalidate
Options
-excludeTypes
<exclude_resource
_names>
Resource type to exclude from being checked;
for example, Rule, DataMonitor
If specifying multiple resource types to
exclude, use comma to separate them.
Resource type – Rule,DataMonitor(comma
separated)
-out <output_dir> Output directory for validation report. If none
is specified, the report is placed in the
directory from which you run the
resvalidate command

A ArcSight Commands
ruledesc
runcertutil
-persist [false |
true]
If a resource is found to be invalid, whether to
mark it invalid or only report it as invalid. For
example, a rule depends on a filter that is
missing. When you run the resvalidate
command and –persist=false, the rule is
reported as invalid but not marked invalid.
However if –persist=true, the rule is marked
as invalid.
Default: persist=false.
Examples
To run:
arcsight resvalidate
Description
Rule description tool to fetch rules information. (Used by HPOVO.)
Tool to monitor managed objects in the ArcSight Manager
Applies to Manager
Syntax ruledesc –t {ovo|uri} –i info [options]
Options -t <type> (Required) Type: { ovo | uri }
-i <info> (Required) Info (depends on type).
-p <pwd> Password
-port <port> Port for Manager. Default: 8443
-prot <prot> Protocol {http | https}. Default: https
-u <name> User name
Examples
To run:
arcsight ruledesc
Description
A wrapper launcher for the nss certutil tool used for managing
certificates and key pairs. For more details on the certutil tool, you
can vist the ‘NSS Security Tools’ page on the Mozilla website.
Note: If you do not see any error or warning messages after
runcertutil has run, it is an indication that the command
completed successfully.
Applies to N/A
Syntax arcsight runcertutil
Options -A Add a certificate to the database

A ArcSight Commands
-a Use ASCII format or allow the use of ASCII
format for input or output.
-v <certificate_
validity_in_
months>
Set the number of months for which a new
certificate is valid. You can use this option
with the 
-w option which sets the beginning time for
the certificate validity. If you do not use the 
-w option, the validity period begins at the
current system time.
If you do not specify the -v argument, the
default validity period of the certificate is
three months.
-w <beginning_
offset_months>
Set an offset from the current system time, in
months, for the beginning of a certificate's
validity period. Can be used when creating the
certificate. Use a minus sign (-) to indicate a
negative offset. If this argument is not used,
the validity period begins at the current
system time.
-n <certificate_
name>
Alias for the certificate
Notes:
• When generating a key pair on the
Manager or ArcSight Web, it is mandatory
to set the alias name to “mykey” (without
the quotes)
• When importing a certificate, you can set
the alias name to any name of your choice
-t <attributes> Set the certificate trust attributes
-d <certdb_dir> Specify the directory of the certificate
database relative to <ARCSIGHT_HOME>.
-i Certificate import request
-L List all the certificates
-r Encoding type
-o <filename> Output file name for new certificates or binary
certificate requests. Be sure to use quotation
marks around the file name if the file name
contains spaces. If you do not specify a
filename, by default, the output is directed to
standard output.
-S Create a certificate to be added to the
database
-s <subject> Subject name
-k <key_type> Type of key pair to generate
-x Self signed
-m
<serial_number>
Certificate serial number

A ArcSight Commands
runmodutil
runpk12util
-v <days> Validity period in days, for example, use 
-v 1825
to change the validity period to 5 years where
1825 is the number of days in 5 years.
-V Check the validity of the certificate
-n <cert_name> Certificate name
-H Help on this tool
Examples
To run:
arcsight runcertutil
Description
A wrapper launcher for the modutil nss cryptographic module utility.
For more details on the certutil tool, you can vist the ‘NSS Security
Tools’ page on the Mozilla website.
Applies to N/A
Syntax arcsight runmodutil
Options
-fips
[true|false]
Alias for the certificate
-dbdir
<dir_path>
The security database directory
-H Help on this tool
Examples
To run:
arcsight runmodutil
Description
The pk12util allows you to export certificates and keys from your
database and import them into nssdb. This is a wrapper launcher for
the pk12util nss tool.
For more details on the certutil tool, you can vist the ‘NSS Security
Tools’ page on the Mozilla website.
Applies to N/A
Syntax arcsight runpk12util
Options
-d
<Cert_directory>
Path to your certificate directory (nssdb)
-i <file> The name of the file to be imported
-h Help on this tool

A ArcSight Commands
script
searchindex
Examples
To run:
arcsight runpk12util
Description Run a Python script
Applies to Manager
Syntax script –f <script_file>
Options -f <file_list> The script(s) to run
-a <args> Command line arguments to pass to script
Examples
To run a Python script:
arcsight script myScript.py
Description
Utility that creates or updates the search index for resources.
If you provide the credentials for the Manager, it automatically
associates with the newly created or updated index. However, if you
do not specify any credentials, you will have to manually configure
the Manager to use the updated index.
Note: Supporting 50,000 actors requires a minimum of 2 GB heap
size for this service. The value of the heap size needs to be modified
in <ARCSIGHT_HOME>/bin/scripts/searchindex.bat and
<ARCSIGHT_HOME>/bin/scripts/searchindex.sh files. The default
value in these files is set to 1028m.
Applies to Manager
Syntax searchindex –a action
Options
-a <action> Possible actions: create, update, or
regularupdate
create—Creates a new search index.
update—Updates all resources in the index
that were touched since the last daily update
was run. Although “update” is a scheduled
task that runs daily, you can run it manually.
regularupdate—Updates all resources in the
index that were touched since the last regular
update was run. Although “regular update” is
a scheduled task that runs every 5 minutes,
you can run it manually.
-m <manager> Name of the Manager
-p <password> Password for the user

A ArcSight Commands
sendlogs
tee
tempca
-t <time> Time stamp that indicates starting when the
resources should be updated
-u <user> User name with which to log in to the
Manager
Examples
To run:
arcsight searchindex –a <action>
Description
Wizard to sanitize and save ArcSight log files so that you can send
them to customer support for analysis, if they instruct you to do so.
(Note: it does not actually send the log files anywhere.)
Applies to Manager, Database, Console, SmartConnectors
Syntax sendlogs
Options
mode)
mode
-n <num> Incident number (Quick mode)
Examples
To run on all components except SmartConnectors:
arcsight sendlogs
Description
Displays the output of a program and simultaneously writes that
output to a file
Applies to Manager
Syntax -f <filename>
Options -a Append to the existing file
Examples
To run:
arcsight tempca -i | arcsight tee sslinfo.txt
Description Inspect and manage demo certificates
Applies to Console
Syntax tempca

A ArcSight Commands
testdbconnection
Options -a <alias> Key store alias of the private key to dump
-ac Add the demo CA’s certificate to the client
truststore
-ap Create demo SSL key pair and add it to
ArcSight Manager key store
-dc Dump/export the demo CA’s certificate to a
file (demo.crt) for browser import
-dpriv Dump private key from ArcSight Manager key
store
-f <file> Filename to write the demo CA’s certificate to
-i Display summary of current SSL settings
-k <n> Key store: Manager (1) or Web Server (2)
-n <host> Host name of the Manager (opt for the
creation of a demo key pair)
-nc No chain: Do not include certificate chain
(option for creation of a demo key pair)
-rc Reconfigure not to trust demo certificates.
Removes the demo CA’s certificate from the
client truststore
-rp Remove pair’s current key pair from ArcSight
Manager key store
-v <days> Validity of the new demo certificate in days
(Default: 365)
Examples
To run:
arcsight tempca
Description Test whether the database is up and running
Syntax testdbconnection –u username –p password
Options
-u <username> (Required) User name of the Arcsight user in
the database. Typically, arcsight
-p <password> (Required) Password of the ArcSight user in
the database
-i <instance> Instance of the database. Default: arcsight
-p <port> Port to connect. Default: 1521
-s <host> Hostname of the machine on which database
is located.
Default: localhost

A ArcSight Commands
threaddumps
tproc
uninstallservice
-t <dbtype> Database type: oracle. Default: oracle
Examples arcsight testdbconnection –u arcsight –p password
Description Utility to extract and reformat thread dumps from Manager log files
Applies to Manager
Syntax threaddumps <file>
Options None
Examples
To run:
arcsight threaddumps
Description Standalone Velocity template processor
Applies to Manager
Syntax tproc
Options -d <file> Definitions file
-Dname=value Defines
-l Keep log file
-o <file> Output file
-p <file> Properties file
-t <file> Template file
-v Verbose mode
Examples
To run:
arcsight tproc
Description Wizard to uninstall service
Applies to Manager, ArcSight Web
Syntax uninstallservice

A ArcSight Commands
webserver
webserver-no-wrapper
webserversetup
webserversvc
Options
-c <component> Component whose service will be
uninstalled—Manager or Web
Examples
To run:
arcsight uninstallservice
Description Start the ArcSight Web server
Applies to ArcSight Web
Syntax webserver
Options -c <file> Base configuration file
-host <host> Manager name or address
-p <port> Manager port
-pc <file> User configuration file
Examples
To start the ArcSight Web server:
arcsight webserver
Description Start the ArcSight Web server without automatic restart
Syntax webserver-no-wrapper
Options -ms <mem> Minimum memory
-mx <mem> Maximum memory
Examples
To start the ArcSight Web server without automatic restart:
arcsight webserver-no-wrapper
Description See runwebsetup and websetup
Description Start, stop, restart, or install the ArcSight Web server as a service

A ArcSight Commands
websetup
Syntax
webserversvc [options]
You can use the single letter options shown in brackets instead of
entering the whole word on Windows only
Options Description Windows Solaris Linux AIX
start or (-s)
Start the service No
(Command
available
but does
not work)
Yes Yes Yes
stop or (-q) Stop the service Yes Yes Yes Yes
restart
Restart the
service
No Yes Yes Yes
status
Check status of
service
No No Yes Yes
install or (-i)
<initialHeap>
<maxHeap>
Install the
service
Optional
parameters:
initialHeap—
Initial heap
memory size, in
MB. (Default:
128)
maxHeap—
Maximum heap
memory size, in
MB. (Default:
512)
Yes No No No
remove or (-r)
Remove the
service
Yes No No No
console 
or (-c)
Console Mode Yes No No No
Examples
To start the ArcSight Web server as a service:
arcsight webserversvc start
Description Run the ArcSight Web Configuration Wizard
Syntax websetup
Options None

A ArcSight Commands
whois
Examples
To run the ArcSight Web Configuration Wizard:
arcsight websetup
Description Script used by the whois command of the console
Applies to Console
Syntax whois [-p <port>] [-s <host>] <target>
Options -p <port> Server port
-s <host> Name or address of ‘whois’ server
<target> Name or address to lookup
Examples
To run:
arcsight whois

A ArcSight Commands

Appendix B
Troubleshooting
The following information may help solve problems that occur while operating the ArcSight
system. In some cases, the solution can be found here or in specific ArcSight
documentation, but Customer Support is available if you need it.
If you intend to have Customer Support guide you through a diagnostic process, please
prepare to provide specific symptoms and configuration information. If you intend to do
the initial diagnostic steps yourself, proceed through the following checklist systematically,
trying each applicable item and noting the results for reference.
This appendix is divided into the following sections:
General
Report is empty or missing information.
Check that the user running the report has inspect (read) permission for the data being
reported.
Running a large report crashes the Manager.
A very large report (for example, a 500 MB PDF report) might require so much virtual
machine (VM) memory that it can cause the ArcSight Manager to crash and restart. To
prevent this scenario, you can set up the Manager to expose a special report parameter for
generating the report in a separate process. The separate process has its own VM and
heap, so the report is more likely to generate successfully. Even if the memory allocated is
still not enough, the report failure does not crash the Manager.
This option must be set up on the Manager to expose it in the Console report parameters
list. The steps are as follows:
“General” on page 147
“Query and Trend Performance Tuning” on page 150
“SmartConnectors” on page 153
“Console” on page 153
“Manager” on page 155
“ArcSight Web” on page 157
“Database” on page 158
“SSL” on page 158

B Troubleshooting
1 On the ArcSight Manager in the server.properties file, set
report.canarchivereportinseparateprocess=true. (This makes a new
report parameter available on the Console.)
2 Save the server.properties file and restart the Manager.
3 On the ArcSight Console, open the report that you want to run in a separate process in
the Report Editor, and click the Parameters tab. Set the parameter Generate
Report In Separate Process to true.
4 Run the report. The report should run like a normal report, but it does not consume
the resources of the Manager VM.
Reports that query over a large time range with complex
joins take a long time to run.
You can expedite a report that queries over a large time range with complex joins if you set
it to query with a full scan database hint. To set the query with full scan database hint, do
this:
1 On the ArcSight Manager in the server.properties file, set
report.canquerywithfullscanhint=true. (This makes a new report
parameter available on the Console.)
2 Save the server.properties file and restart the Manager.
3 On the ArcSight Console, open the report that you want to contain the full scan hint in
the Report Editor, and click the Parameters tab. Set the parameter Query with Full
Scan Hint to true.
4 Run the report.
Some Asian language fonts appear mangled when
generating reports in PDF
This problem occurs because some Asian language fonts that are truetype fonts are not
supported directly by versions of Adobe Reader earlier than version 8.0. In order to work
around this, each truetype font must be mapped to an opentype font supported in Adobe
Use this parameter only if you experience a Manager crash when running
large reports such as the ones that contain tables with more than
500,000 rows and 4 or 5 columns per row.
1 Use this parameter only in special circumstances if your organization has
determined with the help of Customer Support or professional services
that it is appropriate.
2 If a report is saved with the parameter set to "true", the full database
optimization hint is applied even if the property
report.canquerywithfullscanhint in server.properties is set back
to false later on.
3 When the property report.canquerywithfullscanhint is set to "true",
the report uses the FULL_SCAN hint in the SQL queries it generates to
query the database. The content of the report does not change, but the
queries logged in server.report.log contain the hint. The main benefit
of querying the database with the FULL_SCAN hint is that it can
significantly reduce the runtime for SQL queries that query over events
within a large time range and contain complex joins.

B Troubleshooting
Reader 8.0. ArcSight provides this mapping in the
<ARCSIGHT_HOME>/i18n/server/reportpdf_config_<locale>.properties
file. You have the option to change the default mapping of any truetype font to the
opentype font by modifying the respective font mapping in this file.
To work around the issue of mangled fonts, ArcSight recommends that you:
1 Install a localized Adobe Reader 8.0 depending on the language of your platform on
your Manager machine. This version of the Adobe Reader installs the opentype fonts
by default.
2 Edit the server.properties file as follows:
a Set report.font.truetype.path property to point to the directory that
contains the truetype and opentype font. On Windows it is typically
C:WINNTfonts;C:Program FilesAdobeReader
8.0ResourceCIDFont where “;” is used as a path separator to separate
the multiple paths. Use “:” as a path separator in Unix. On Unix platforms, the
truetype font path may differ depending on the specific Unix platform, but it is
typically /usr/lib/font. The CIDFont directory is always the same relative to
the Adobe Reader installed directory. So, the default directory would be
/usr/lib/font:<adobe_reader_dir>/Resource/CIDFont.
b Set report.font.cmap.path property to point to Adobe Reader’s CMap
directory. On windows, it is typically C:Program FilesAdobeReader
8.0ResourceCMap. On Unix, the CMap path is relative to the Adobe
Reader installation -- <adobe_reader_dir>/Resource/CMap.
E-mail notification doesn’t happen.
If you receive the following error:
[2009-12-03 14:31:33,890][WARN
][default.com.arcsight.notification.NotifierBase][send] Unable to
send out e-mail notification, notifications have not been
configured.
 Verify the following properties are set in the server.properties file:
notifications.enable=true
and
notifications.incoming.enable=true
 Check server.properties file to find which SMTP server is associated with the
Manager. Make sure that the SMTP server is up and running.
Review the Notification resource and confirm the e-mail address and other
configuration settings.
Notification always escalates.
Check server.properties file to find which POP3 or IMAP server is associated with the
Manager. Make sure that the POP3 or IMAP server is up and running, in order to process
acknowledgements from notification recipients.
Pager notification doesn’t happen.
Check server.properties file to find which SNPP server is associated with the
Manager. Make sure that the SNPP server is up and running.

B Troubleshooting
Query or report performance degrades suddenly.
 Check that the ArcSight Database host has sufficient disk space.
 Check that the ArcSight Database statistics are up to date.
 Has the network infrastructure changed?
 Has the ArcSight Database or DBMS configuration changed?
See also, “Query and Trend Performance Tuning” on page 150 for more information on
performance enhancements and suggestions on how to improve performance with regard
to queries and trends.
Query and Trend Performance Tuning
Previous to ESM v.4.0 SP1, some trends exceeded 10 hours to execute queries. This
eventually caused these queries to fail or lead to ESM scheduler problems. This effect was
most pronounced on systems with high event rates (typically thousands of events per
second).
To resolve this issue, various queries used by the trends in the default ArcSight system
content were studied to ensure that the database was choosing optimal query execution
plans. In a number of cases, the execution plan was not optimal and database "hints" were
added to the queries to optimize the query execution. Most of these queries were sped up,
some of them by a significant amount (much more than a factor of 10).
We have enhanced the scheduler to allocate two threads for processing system tasks. This
change alleviates performance issues caused by conflicts between system tasks and user
level tasks within the scheduler.
Starting in ESM v.4.0 SP1, Patch 3, several performance enhancements related to queries
and trends were included. All follow-on service packs, patches, and releases include these
performance enhancements, configurable properties, and reports. The following sections
detail these, and also provide other troubleshooting tips.
Persistent Database Hints
Database hints are provided in system content packages. These hints are not visible in the
Console. Please do not attempt to modify the system queries through the Console because
this causes the hint to disappear and the query to run slowly again.
server.defaults.properties Entries for Trends
 trends.query.timeout.seconds=7200
This is the amount of time that a trend query is allowed to run, in seconds, before the
SQL statement times out and the trend query fails. If absent or 0, no time-based
timeout is applied.
 trends.query.timeout.percent=50
This is the amount of time that a trend query is allowed to run, as a percentage of the
query interval for interval trends, before the SQL statement times out and the trend
query fails. If absent or 0, no percentage-based timeout is applied.
As an example, with a 50 percent setting, a query covering a start/end time range of 1
hour times out after 30 minutes. A start/end time range covering 1 day would time out
after 12 hours.
If both timeouts are specified, the system uses the smaller of the two.

B Troubleshooting
 trends.query.failures.deactivation.threshold=3
If this many consecutive "accumulate" (not refresh) runs fail for any reason, the
system automatically disables the trend. The check is always performed after any
accumulate query run fails. Once the threshold is reached, any remaining queries to be
executed by this task are skipped. If this setting is absent or 0, the checking
mechanism is turned off.
If a trend or query is stopped because of any of the above reasons, an audit event
reflects this.
Troubleshooting Checklist after Restarting the Manager
 Use the Console Trend Editor to manually disable any trends that you do not need or
that you notice have excessive query times. Disabling these trends helps reduce
scheduler and database contention.
 Your own custom trends may have long-running queries and may be timing out. If this
is the case, use the Query Tuner tool provided with this patch. See the description on
querytuner in the ArcSight Commands appendix for instructions on how to use this
tool. Once you have identified a hint that might help, please contact Customer Support
and provide a package with your query or queries for ArcSight to examine. We
investigate and determine if database hints can improve your trend queries.
 As trend data gathering tasks wake up, the trend attempts to fill in the gaps for
missing intervals. Depending on the size of the gaps, this may take some time before
the trends catch up.
 A trend does not usually re-run any previously failed runs. If you want to re-run a
particular time, you need to manually request it from the Trend Editor.
Reports for Monitoring Trend Performance
The following new reports are available as a part of this Patch. We recommend running
these reports after installing the Patch to monitor the trend performance:
/All Reports/ArcSight Administration/Resource
Monitoring/Trends/Trend Query Runs Duration
/All Reports/ArcSight Administration/Resource
Monitoring/Trends/Skipped Scheduled Tasks
Disable these Trends on High Throughput Systems
If your system environment typically processes a very large number of events per second
(EPS) (e.g., over 1000 EPS or 100 million events per day), we recommend that you
manually disable the following 9 trends, which are enabled by default:
/All Trends/ArcSight Administration/User/ArcSight User Login Trends
– Hourly
/All Trends/ArcSight Foundation/Configuration Monitoring/Asset
Configuration Change Tracking/Host Configuration Modifications
/All Trends/ArcSight Foundation/Configuration Monitoring/Asset
Restarts/Asset Startup and Shutdown Events - Daily Trend
/All Trends/ArcSight Foundation/Configuration Monitoring/User
Account Modifications/User Account Creation
/All Trends/ArcSight Foundation/Configuration Monitoring/User
Account Modifications/User Account Modifications

B Troubleshooting
/All Trends/ArcSight Foundation/Intrusion Monitoring/Operational
Summaries/Reconnaissance/Port Scanning
Summaries/Reconnaissance/Zone Scanning Events by Priority
Summaries/Vulnerability View/Prioritized Vulnerability Events by
Zone
/All Trends/ArcSight Foundation/Network Monitoring/Overall Traffic
How do you know when a trend is caught up?
You can use either of the following techniques, both using the ArcSight Console UI:
 Using the Trend Data Viewer from within the Trends resource tree, you can see at
most 2000 rows of data. (Select a trend in the resource tree, right-click, and choose
Data Viewer.) Sort the trend timestamp column so that the timestamps show newest
to oldest and observe when the newest value indicates it has caught up.
 Using the Refresh... button in the Trend Editor, set the start time as far back as
needed (days or weeks) to see any entries and click Refresh to see which runs show
up as available to be refreshed. Only the most recent ones should show first. Note that
you should not actually refresh any runs, but only use this technique to see what has
been run.
How long does it take a trend to catch up?
This depends on how long the underlying query interval is, but a trend typically does up to
48 runs, as needed, when it wakes up.
For a trend that queries an entire day and runs once a day, this would allow for more than
a month’s worth of data to be queried. The data must be present on the system, however,
or the query returns no results (but it does not fail).
Enhancing the Performance Globally for all Database
Queries
You can enhance the performance for all queries made against the database. When Oracle
Optimizer decides on a query execution plan, it can dynamically do a sampling of actual
data to estimate the cost of the query. Based on the findings of this sampling, the
Optimizer comes up with the best query execution plan which helps improve query
performance. To enable dynamic sampling, run:
% arcdbutil sql
Enter user-name: / as sysdba
SQL> @<ARCSIGHT_HOME>utilitiesdatabaseoraclecommonsql
SetDynamicSampling.sql
In addition to Dynamic Sampling, you can update the IO transfer speed in the database
which helps in query performance. If you do not update the IO transfer speed, Oracle
defaults to a very low IO transfer speed esimate that adversely affects the query execution
plan. Run the following command (while logged in as sysdba):
SQL> @ARCSIGHT_HOMEutilitiesdatabaseoraclecommonsql

B Troubleshooting
GatherSystemStats.sql
This script should also be run every time you make any storage hardware changes that
affects IO transfer speeds.
SmartConnectors
My device is not one of the listed SmartConnectors.
ArcSight offers an optional feature called the FlexConnector Development Kit which may
enable you to create a custom SmartConnector for your device.
ArcSight can create a custom SmartConnector. Contact Customer Support.
My device is on the list of supported products, but it does
not appear in the SmartConnector Configuration Wizard.
Your device is likely served by a Syslog sub-connector of either file, pipe, or daemon type.
Device events are not handled as expected.
Check the SmartConnector configuration to make sure that the event filtering and
aggregation setup is appropriate for your needs.
SmartConnector not reporting all events.
Check that event filtering and aggregation setup is appropriate for your needs.
Some Event fields are not showing up in the Console.
Check that the SmartConnector’s Turbo Mode and the Turbo Mode of the Manager for the
specific SmartConnector resource are compatible. If the Manager is set for a faster Turbo
Mode than the SmartConnector, some event details are lost.
SmartConnector not reporting events.
Check the SmartConnector log for errors. If the SmartConnector cannot communicate with
the Manager, it caches events until its cache is full.
Partition Archiver problems.
See Partition Archiver under “Database” on page 158.
Console
Can’t log in with any Console.
Check that the ArcSight Manager is up and running. If the Manager is not obviously
running, open a command window on <ARCSIGHT_HOME>/bin, and run:
./arcsight manager
If the Manager is running, but you still can’t log in, suspect any recent network changes,
such as the installation of a firewall that affects communication with the Manager host.

B Troubleshooting
Can’t log in with a specific Console.
If you can log in from some Console machines but not others, focus on any recent network
changes and any configuration changes on the Console host in question.
Console reports out of memory.
This can happen when you open many independent viewing channels. If you need to do
this often, change the memory settings in the console.bat or console.sh file. Find the
line that starts set ARCSIGHT_JVM_OPTIONS= and change the parameter –Xmx128m to –
Xmx256m. You must restart the Console for the new setting to take effect.
Acknowledgement button is not enabled.
The Acknowledgement button is enabled when there are notifications to be acknowledged
and they are associated with a destination that refers to the current user. To enable the
button, add the current user to the notification destination.
The grid view of Live security events is not visible.
To restore the standard grid view of current security events, select Active Channels from
the Navigator drop-down menu. Double-click Live, found at /Active
channels/Shared/All Active channels/ArcSight System/Core/Live
The Navigator panel is not visible.
Press Ctrl+1 to force the Navigator panel to appear.
The Viewer panel is not visible.
Press Ctrl+2 to force the Viewer panel to appear.
The Inspect/Edit panel is not visible.
Press Ctrl+3 to force the Inspect/Edit panel to appear.
Internal ArcSight events appear.
Internal ArcSight events appear to warn users of situations such as low disk space for the
ArcSight Database. If you are not sure how to respond to a warning message, contact
Customer Support.
The Manager Status Monitor reports an error.
The Console monitors the health of the ArcSight Manager and the ArcSight Database. If a
warning or an error occurs, the Console may present sufficient detail for you to solve the
problem. If not, report the specific message to Customer Support.
Console logs out by itself.
Check the Console log file for any errors. Log in to the Console. If the Console logs out
again, report the error to Customer Support.

B Troubleshooting
Console stops responding when sending a test SNPP
notification.
If the Console stops responding when sending a test SNPP notification, it may indicate that
the SNPP port is blocked by a firewall or packet filtering device.
Cannot log in to ArcSight Web from within the Console.
In ArcSight Console, if you click File->Launch ArcSight Web, it starts the browser within
the Console window and display the ArcSight Web login screen. Once you enter your
username and password for the Manager, you should be able to log into the Web from
within the Console. However, if inspite of entering the correct login information, you cannot
login to ArcSight Web and your browser appears to hang, then you have to change the
security settings on your browser. To do so on Internet Explorer:
1 Go to Tools->Internet Options.
2 Click the Security tab.
3 Click the Internet icon.
4 Click the Custom level... button.
5 Select Medium from the Reset to drop down menu.
6 Click Reset button. You receive a warning asking you whether you want to change the
security setting of the zone. Click Yes.
7 Click OK in the Security Options box.
8 Click OK in the Internet Options box.
9 Go back to the Console and try to restart ArcSight Web from within the Console by
clicking File->Launch ArcSight Web.
Console does not start in Windows 2008
If you installed and then started the Console in Windows 2008, you may get an error due
to access refusal. In Windows 2008, make sure to configure the User Access Control (UAC)
of the ArcSight Console user. Consult the Microsoft website for more details on UAC specific
to Windows 2008.
Manager
Can’t start Manager.
The ArcSight Manager provides information on the command console which may suggest a
solution to the problem. Additional information is written to
<ARCSIGHT_HOME>/logs/default/server.std.log.
To check database connectivity manually, open a command window on
<ARCSIGHT_HOME>/bin (on the Manager host) and run:
arcsight testdbconnection

B Troubleshooting
Manager shuts down.
The Manager stops when it encounters a fatal error. The file
<ARCSIGHT_HOME>/logs/default/server.std.log has more details about the
error condition.
For example, the following error indicates that a connection cannot be established with the
underlying Oracle DBMS:
[ERROR][default.com.arcsight.common.persist.oracle.OracleDatabaseI
nfoBroker][getDatabaseInfo]
com.arcsight.common.persist.PersistenceException: Unable to get
connection: Io exception: Connection reset by peer: socket write
error
This indicates that the Oracle TNS Listener is running but the actual ArcSight Database
service is not reachable.
Manager restarts automatically.
If the Java Virtual Machine (JVM) fails to respond within two minutes, an ArcSight
watchdog program automatically restarts it, which reduces system performance but does
not cause data loss. This situation has been observed on low-end Windows-based host
machines with pagefile size optimization enabled. Optimization complicates the garbage
collection process, rendering the JVM non-responsive for longer than two minutes.
Disable pagefile size optimization. Perform the following steps to disable pagefile size
optimization on Windows 2000 Manager hosts:
1 Right-click My Computer and select Properties from the menu. Select the
Advanced tab.
2 Click Performance Options for Windows 2000.
3 Set Initial size to the same value as Maximum size.
4 Click Set.
5 Click OK.
The log contains a warning “Side table for [name] is 100%
full. System performance will be affected.”
This log error message is the result of the default sizes for side object caches being too
small for some larger production deployments. Although system performance is generally
not affected, to stop generating the warning message, add the following lines to the
server.properties file and restart the ArcSight Manager:
persist.securityevent.stcache.GeoDescriptor=50000
persist.securityevent.stcache.AgentDescriptor=500
persist.securityevent.stcache.DeviceDescriptor=50000
persist.securityevent.stcache.CategoryDescriptor=3000
persist.securityevent.stcache.LabelsDescriptor=2000

B Troubleshooting
persist.securityevent.stcache.ResourceRef=20000
If you continue to see the error message after this change, one or more SmartConnectors
may be misconfigured. Contact Customer Support.
Scheduled Task Run is Off When Switching from Daylight
Savings Time to Standard Time or Vice Versa.
 If the trigger time for a particular scheduled task run happens to fall during the
transition time from DST to ST or vice versa, the interval for that particular run gets
thrown off. The interval calculation for subsequent scheduled runs do not get affected.
 Currently, there are four time zones that are not supported in ESM:
 Kwajalein
 Pacific/Kwajalein
 Pacific/Enderbury
 Pacific/Kiritimati
These time zones fall in two countries, Marshall Islands and Kiribati.
ArcSight Web
Some content, particularly dashboards, is not visible.
Install the latest Adobe Flash plug-in to your browser. Visit the Adobe website to download
this free plug-in.
Can’t log in to ArcSight Web.
Check that the ArcSight Web Server is up and running. If ArcSight Web is up, check that
the ArcSight Manager is also up and running.
If the Manager is running, but you still can’t log in, suspect any recent network changes,
such as the installation of a firewall that affects communication between the ArcSight Web
server and the Manager host.
If you can log in to the ArcSight Console but not ArcSight Web, focus on any recent
network changes and any configuration changes to your browser.
Make sure that the version number of ArcSight Web matches that of the Manager. If the
version numbers do not match, log in is disabled.
Can’t start ArcSight Web.
If the ArcSight Web Server cannot start, check that the ArcSight Manager is up and
running. If the Manager is not obviously running, open a command window on
<ARCSIGHT_HOME>/bin, and run:
./arcsight manager
Examine the ArcSight Web log file for specific error messages. If the message is not clear,
contact Customer Support.

B Troubleshooting
Database
Partition Archiver can’t connect to Manager.
Check the Partition Archiver log for errors. The log file is found in the logs directory:
<ARCSIGHT_HOME>/logs/default/agent.out.wrapper.log
An SSL Handshake exception in the log indicates a problem with the Manager’s certificate.
From the SmartConnector’s install directory, run the following command to establish a valid
certificate:
./arcsight agent tempca -ac
Oracle hangs without warning.
If automatic archive log mode is turned on, Oracle hangs if the archive log destination
becomes full. Oracle resumes when you make archive log space available.
An e-mail notification reports a problem with the ArcSight
Database.
Don’t ignore a warning or error notification from the ArcSight system. If the message is not
clear to you, contact Customer Support. Ignoring a database error can lead to the Manager
suddenly stopping, which eventually leads to security event data loss.
See Appendix C, Monitoring Database Attributes, for more information.
Partition logs may not be complete.
Only one duplicate log file can be written to at one time. Therefore, if a partition utility is in
progress and another partition utility starts in parallel, the logs for the first utility are no
longer written to the duplicate log file. However, the log data for the first utility is not lost;
it is available in the <ARCSIGHT_HOME>/logs/server.log file.
See the “Database Administration” chapter, for more information.
SSL
Cannot connect to the SSL server: IO Exception in the
server logs when connecting to the server
Causes:
The SSL server may not be running.
 A firewall may be preventing connections to the server.
Resolutions:
 Ensure that the SSL server is running.
 Also, ensure that a firewall is not blocking connections to the server.

B Troubleshooting
Cannot connect to the SSL server
The hostname to which the client initiates an SSL connection should exactly match the
hostname specified in the server SSL certificate that the server sends to the client during
the SSL handshake.
Causes:
 You may be specifying Fully Qualified Domain Name (FQDN) when only hostname is
expected or the other way around.
 You may be specifying IP address when hostname is expected.
Resolutions:
 Type exactly what the server reports on startup in server.std.log (“Accepting
connections at http://...”)
 For Network Address Translation (NAT) or multi-homed deployments, use hosts file to
point client to correct IP.
PKIX exchange failed/could not establish trust chain
Cause:
Issuer cannot be found in trust store, the cacerts file.
Resolution:
Import issuer’s certificate (chain) into the trust store.
Issuer certificate expired
Cause:
The certificate that the SSL server is presenting to the client has expired.
Resolution:
Import the latest issuer’s certificate (chain) into the trust store.
Cannot connect to the Manager: Exception in the server
log
Cause:
If you replaced the Manager’s key store, it is likely that the old key store password does not
match the new password.
Resolution:
Make sure the password of the new key store matches the old key store. If you do not
remember the current key store’s password, run the Manager Configuration Wizard on the
Manager (ArcSight Web Configuration Wizard on the Web) to set the password of the
current key store to match the new key store’s password.
Certificate is invalid
Cause:
The timestamp on the client machine might be out of the bounds of the validity range
specified on the certificate.
Resolution:
Make sure that the current time on the client machine is within the validity range on the
certificate.

B Troubleshooting
Issue with Internet Explorer and ArcSight Web in FIPS
Mode
When using Internet Explorer (IE) with ArcSight Web running in FIPS mode, IE may return
an error message when you attempt to log in using username and password
authentication:
 ArcSight Web is FIPS-enabled
 You have opted to use Password Based or SSL Client Based Authentication
 You use ActivClient middleware and have registered the certificate from Smart Card
into Internet Explorer
 You have enabled TLS v1 on Internet Explorer
 ArcSight Web’s truststore contains the Smart Card issuer’s certificate
 The card is not present in the card reader
This is an issue with Internet Explorer. To use the password based authentication in FIPS
140-2 mode, you need to remove all registered PKCS#11 related certificates from the
Internet Explorer certificate repository. To do so:
1 Go to Tools->Internet Options and click the Content tab.
2 Click Certificates and then select the Personal tab.
3 Select all the PKCS#11 related certificates and click Remove.
4 Click Intermediate Certification Authorities.
5 Select all the PKCS#11 related certificates and click Remove.

Appendix C
Monitoring Database Attributes
This chapter provides information about in-built checks that monitor database attributes
and generate warning or error messages, as appropriate. This appendix is divided into the
following sections:
Understanding Database Checks
ArcSight ESM provides in-built checks to monitor database configurations and runtime
attributes. These checks inform you if attributes such as Oracle account password or
available reserve partitions drop below an acceptable value. Depending on the severity of
deviation, a warning or an error message is generated.
If an error or a warning message is generated, these actions take place:
 A message is logged to the server.std.log file on the Manager.
 If you have configured the Manager to generate e-mail, a message is sent.
 A notification message is displayed on the ArcSight Console.
If an error message is generated, the event flow to the Manager is stopped. In that case,
SmartConnectors start caching the events so there is no loss of events. After you have
resolved the issue that caused the error, you can click a reactivation URL that is included in
the error message to restart the event flow.
Each check task is scheduled to run at a predefined interval and compare the current
system state with a predefined threshold, both of which can be changed to suit your needs.
The server.defaults.properties defines the interval and threshold for each task.
You can override these values in the server.properties file on the Manager. That is,
do not edit the server.defaults.properties file. Copy the entry to the
server.properties file and then change the setting.
“Understanding Database Checks” on page 161
“Disabling Database Checks” on page 162
“List of Database Check Tasks” on page 163

C Monitoring Database Attributes
Message text
The following is an example of the error or warning e-mail message that is sent:
Date: Fri, 16 Dec 2011 01:24:36 +0000 (GMT+00:00)
To: administrator@mycompany.com
[-- Attachment #1 --]
[-- Type: text/plain, Encoding: 7bit, Size: 1.0K --]
== SUBSYSTEM STATUS CHANGED ======================================
Error - Event Receiver
== ORIGIN OF CHANGE =============================================
Error - PartitionManagerCheckTaskTracker
-- DESCRIPTION ---------------------------------------------------
[PartitionManagerCheckTaskTracker: Fatal Error: There are only 0
of 7 reserve partitions available. This is likely due to failures
in Partition Manager runs for the past few days. If this situation
is not fixed, the MAX partition will become the CURRENT partition
in the next few days, causing system failure.
Check the Partition Manager logs for errors and fix the problem
before proceeding.
Fix the root cause of the error reported. If the event flow is
stopped, use the
following URL to resume:
https://yourmanager.mycompany.com:8443/arcsight/web/reactivate.jsp
?id=87160D7E0425A22FBE5354FE90387A96]
The following is an example of the notification message that is displayed on the Console:
Disabling Database Checks
If you do not want to run a specific database check, you can disable it.

To disable a database check task, specify the name of the check task as the value for the
whine.check.exclude property in the server.properties file on the Manager.
For example, to exclude PartitionManagerCheckTask, enter this in the
whine.check.exclude=PartitionManagerCheckTask
To exclude multiple check tasks, specify a comma-separated list for the
whine.check.exclude property; for example,
whine.check.exclude=PartitionManagerCheckTask,
PartitionCompressorCheckTask
List of Database Check Tasks
The following is a list of check tasks available in this ArcSight ESM release. Each check task
includes an interval at which that task is performed, any attributes that are checked, and
the default thresholds at which a Warning or Error message is generated.
1 General check tasks
# The default interval to run configured check tasks, in seconds.
whine.check.interval=30
# Specific check intervals for checking free space, in seconds.
whine.check.interval.DBFreeSpaceChecker=30
# The actual update interval of free database space information by
DatabaseInfoBroker, seconds.
databaseinfo.update.interval=30
2 AccountCheckTask - Checks User Account Expiry
# AccountCheckTask is run every 12 hours
whine.check.interval.AccountCheckTask=43200
# AccountCheck Password Expiry warning threshold (days)
dbcheck.oracle.account.warn.threshold=5
# AccountCheck Password Expiry error threshold (days)
dbcheck.oracle.account.error.threshold=2
3 ArchiveDestinationCheckTask - If the redo log archive destination is cross
mounted in the manager box, this task checks for space availability in such a
destination
# ArchiveDestinationCheckTask is run every 1 hour
whine.check.interval.ArchiveDestinationCheckTask=3600
# Whether database archive destination file systems are cross-mounted in the
Manager box
dbcheck.oracle.archivedest.xmount=false
# Minimum number of hours of archive space that should be available
dbcheck.oracle.archivedest.threshold.hours=18
To obtain the name of a task, see List of Database Check Tasks.

4 ArchiveSessionCheckTask - Checks whether any Oracle sessions are stuck on
"archive required" wait event.
# ArchiveSessionCheckTask is run every 30 seconds
whine.check.interval.ArchiveSessionCheckTask=30
5 ParameterCheckTask - Checks default and non-default Oracle parameters against
values specified below.
# ParameterCheckTask is run every 24 hours
whine.check.interval.ParameterCheckTask=86400
# Suggested % of shared_pool in terms of total sga
dbcheck.oracle.parameter.sharedpool=20
# Suggested % of db_cache in terms of total sga
dbcheck.oracle.parameter.dbcache=40
# Suggested minimum db_files value
dbcheck.oracle.parameter.dbfiles=200
# Suggested maximum java_pool size
dbcheck.oracle.parameter.javapool=0
# Suggested minimum log_buffer size
dbcheck.oracle.parameter.logbuffer=1048576
# Suggested maximum parallel_max_servers value
dbcheck.oracle.parameter.parallelmaxservers=0
# Suggested pga_aggregate_target value
dbcheck.oracle.parameter.pgaaggregatetarget=40
# Suggested minimum processes value
dbcheck.oracle.parameter.processes=100
# Suggested minimum undo_retention value
dbcheck.oracle.parameter.undoretention=43200
# Suggested timed_statistics value
dbcheck.oracle.parameter.timedstatistics=TRUE
# Suggested workarea_size_policy value
dbcheck.oracle.parameter.workareasizepolicy=AUTO
# Specific check intervals for certian tasks, in seconds
whine.check.interval.DBFreeSpaceChecker=10
# Suggested filesystemio_options parameter value
dbcheck.oracle.parameter.filesystemiooptions=SETALL
6 PartitionArchiverCheckTask - Checks whether partition archiver is working
successfully.
# PartitionArchiverCheckTask is run every 12 hours
whine.check.interval.PartitionArchiverCheckTask=43200
# Archiver Lag Warning Threshold
dbcheck.oracle.archiver.warnthreshold=2

7 PartitionCompressorCheckTask - Checks whether partition compressor is working
successfully.
# PartitionCompressorCheckTask is run every 12 hours
whine.check.interval.PartitionCompressorCheckTask=43200
8 PartitionManagerCheckTask - Checks whether enough reserve partitions are
available.
# PartitionManagerCheckTask is run every 12 hours
whine.check.interval.PartitionManagerCheckTask=43200
# Partition Manager Warning Threshold (# of available reserve partitions)
dbcheck.oracle.manager.warnthreshold=5
# Partition Manager Error Threshold (# of available reserve partitions)
dbcheck.oracle.manager.errorthreshold=2

Appendix D
The Logfu Utility
Logfu is an ArcSight utility that analyzes log files. It is indispensable for troubleshooting
problems that would otherwise require poring over text logs. Logfu generates an HTML
report (logfu.html) and, especially in SmartConnector mode, includes a powerful
graphic view of time-based log data. Logfu pinpoints the time of the problem and often the
cause as well.
Logfu has two windows: the interactive Chart and the Plot/Event window.
“Running Logfu” on page 168
“Example” on page 170
“Troubleshooting” on page 170
“Menu” on page 172
“Typical Data Attributes” on page 172
“Intervals” on page 173

D The Logfu Utility
Running Logfu
Logfu finds log files in the current directory. The –a or –m or –c switches tell it which file
names to look for. The –m switch tells it to look for all three Manager logs—
server.std.log, server.log, and server.status.log—for example.
To run Logfu, follow these steps:
1 Open a command or shell window in <ARCSIGHT_HOME>/logs/default. This
refers to the logs directory under the ArcSight installation directory. (Path separators
are / for Unix and for Windows.) Logfu requires an X Windows server on Unix
platforms.
2 Run logfu for the type of log to analyze:
For Manager logs, run: ../bin/arcsight logfu –m
For SmartConnector logs, run: ../bin/arcsight agent logfu –a
3 Right-click in the grid and select Show Plot/Event Window from the context menu.
4 Check at least one attribute (such as Events Processed) to be displayed.
The initial display is always an empty grid. Loading very large log files can take a few
minutes (a 100MB log might take 5 or 10 minutes). Once log files are scanned, the
information gleaned from them is cached (in files named data.*), which speeds up loading
the second time. If something about the log changes, however, you must manually delete
the cache files to force logfu to reprocess the log.
Right-click the grid and choose Show Plot/Event Window from the context menu.
Select what to show on the grid from the Plot/Event Window that appears.
The tree of possible things to display is divided into Plot—attributes that can be plotted
over time, like events per second—and Event—one-time things, like exceptions, which are
shown as vertical lines. Check as many things as you want to show.
Because SmartConnectors can talk to multiple Managers and each can be configured to use
multiple threads for events, the Plot hierarchy includes nodes for each SmartConnector and
each Manager. Within the SmartConnector, threads are named E0, E1, and so on. Each
SmartConnector has one heartbeat thread (H0) as well. Different types of SmartConnector

D The Logfu Utility
(firewall log SmartConnector, IDS SNMP SmartConnector, and so on) have different
attributes to be plotted.
The interactive Chart uses sliders to change the view. Hovering over a data point displays
detailed information.
There are two horizontal sliders—one at the top of the grid, one underneath. The slider at
the top indicates the time scale. Drag it to the right to zoom in, or widen the distance
between time intervals (vertical lines). The slider at the bottom changes the interval
between lines—anywhere from 1 second at the far left to 1 day at the far right. The time
shown in the grid is listed below the bottom slider:
Showing YY/MM/DD HH:MM:SS – YY/MM/DD HH:MM:SS (Interval= X)
Click anywhere in the grid area and drag a green rectangle to zoom in, changing both the
vertical and horizontal scales at once. Hold the Ctrl key as you drag to pan the window in
the vertical or horizontal direction, and hold both the Shift and Ctrl keys as you drag to
constrain the pan to either vertical or horizontal movement. When you are panning, only
sampled data is shown, but when you stop moving, the complete data fills in. (You can
change this by unchecking Enable reduced data point rendering in Preferences.)
Hover the mouse over a data point to see detailed information in a “tooltip” window, as
shown in the figure, above..
For each attribute being plotted, a colored, vertical slider appears on the right of the grid.
This slider adjusts the vertical (value) scale of the thing being plotted.
By default, data points are connected by lines. When data is missing, these lines can be
misleading. To turn off lines, uncheck Connect dots in Preferences.
Once you have specified attributes of interest, scaled the values, centered and zoomed the
display to show exactly the information of concern, select Save as JPG on the menu to
create a snapshot of the grid display that you can print or e-mail. The size of the output
image is the same as the grid window, so maximize the window to create a highly detailed
snapshot, or reduce the window size to create a thumbnail.

D The Logfu Utility
Example
Perhaps a particular SmartConnector starts by sending 10 events per second (EPS) to the
Manager, but soon is sending 100, then 500, then 1000 EPS before dropping back down to
10. Logfu lets you plot the SmartConnector’s EPS over time—the result is something like a
mountain peak.
When you plot the Manager’s receipt of these events, you might see that it keeps up with
the SmartConnector until 450 EPS or so. You notice that the Manager continues consuming
450 EPS even as the SmartConnector’s EPS falls off. This is because the Manager is
consuming events that were automatically cached.
By plotting the estimated cache size, you can see the whole story—the SmartConnector
experienced a peak event volume and the cache stepped in to make sure that the Manager
didn’t lose events, even when it couldn’t physically keep up with the SmartConnector.
Use the vertical sliders on the right to give each attribute a different scale to keep the peak
EPS from the SmartConnector from obscuring the plot of the Manager’s EPS.
Troubleshooting
Another real-world example involved a Check Point SmartConnector that was mysteriously
down for almost seven days. Logfu plotted the event stream from the SmartConnector and
it was clearly flat during the seven days, pinpointing the outage as well as the time that the
event flow resumed. By overlaying Check Point Log Rotation events on the grid, it became
clear that the event outage started with a Log Rotation and that event flow resumed
coincident with a Log Rotation.
Further investigation revealed what had happened—the first Check Point Log Rotation
failed due to lack of disk space, which shut down event flow from the device. When the
disk space problem had been resolved, the customer completed the Log Rotation and
event flow resumed.
If the Manager suddenly stops seeing events from a SmartConnector Logfu helps
determine whether the SmartConnector is getting events from the device. Another
common complaint is that not all events are getting through. Logfu has a plot attribute
called ‘ZFilter’—zone filter—that indicates how many raw device events are being filtered by
the SmartConnector. Events processed (the number of events sent by the device) minus

D The Logfu Utility
ZFilter should equal Sent (the number of events sent to the Manager). A sample HTML
report is shown below.

D The Logfu Utility
Menu
Typical Data Attributes
SmartConnector Specific
Menu Item Description
Show Plot/Event Window Presents the possible attributes to be
displayed
Bring To Front
Send to Back
Undo Zoom Return to previous view
Zoom out
Auto Scale Fit all data on the grid
Save as JPG Save a snapshot of the current view on the
grid
Go to Display the line of the log file which
corresponds to a particular data point
Reset Clear all checked attributes and restore the
normal startup view of an empty grid
Preferences Check:
Connect dots – draw lines between data
points
Enable fast rendering
Enable reduced data point rendering
CommandResponses Processed Number of Get Status calls from the Manager
Current Max Rate
Events Processed
Events/Sec Averaged events per second
Events/Sec (Since Last Check) Events per second in last minute (unless check
time is configured to a different interval)
Max Rate
contcachesize Contiguous Cache Size
maxrate Maximum Rate
maxsleeptime Maximum Sleep Time
randomizeratetime Randomize Rate Time
timefactor

D The Logfu Utility
For Each SmartConnector Thread
Memory Usage
Events
Intervals
1 second
5 seconds
10 seconds
30 seconds
1 minute
5 minutes
10 minutes
30 minutes
1 hour
6 hours
12 hours
1 day
Average Batch Size Number of events per batch (typically ~100)
Average Cycle Time Duration of transport and Manager acknowledgement
Average Time Per Batch Should be under 1 minute
Total Total available memory
Used Memory used
SmartConnectors Initializing SmartConnector startup
com.arcsight.agent.transport.
TransportException
com.arcsight.common.agent.
ServerConnectionException
java.net.SocketException
Forcing disconnection Transport event—Manager disconnecting.

D The Logfu Utility

Appendix E
Creating Custom E-mails Using Velocity
Templates
This appendix describes how to modify Velocity templates to customize e-mail messages
you receive from the ArcSight notification system.
A sample use case is presented to illustrate the concept.
Overview
ArcSight supports the use of Velocity templates that are a means of specifying dynamic
input to the underlying Java code.
You can apply Velocity templates in a number of places in ArcSight. For a complete list of
Velocity template applications in ArcSight, see the Console online Help.
This section describes one such application—E-mail Notification Messages—in detail. You
can use Velocity templates on your Manager to create custom e-mail messages to suit your
needs.
Notification Velocity templates
The <ARCSIGHT_HOME>/Manager/config/notifications directory contains the
following two Velocity templates for customizing e-mail notifications:
 Email.vm—The primary template file that calls secondary template files.
 Informative.vm—The default secondary template file.
Commonly used elements in Email.vm and
Informative.vm files
It is important to understand the commonly used Velocity programming elements in the
Email.vm and Informative.vm files before editing these files.
The #if statement
The general format of the #if statement for string comparison is:
“Overview” on page 175
“Notification Velocity templates” on page 175

E Creating Custom E-mails Using Velocity Templates
#if ($introspector.getDisplayValue($event, ArcSight_Meta_Tag)
Comparative_Operator Compared_Value)
The #if statement for integer comparison is:
#if ($introspector.getValue($event,
ArcSight_Meta_Tag).intValue()Comparative_Operator Compared_Value)
You can specify ArcSight_Meta_Tag, Comparative_Operator, and
Compared_Value to suit your needs.
ArcSight_Meta_Tag is a string when using the #if statement for string comparison (for
example, displayProduct) and is an integer for the #if statement for integer comparison
(for example, severity).
For a complete listing of ArcSight meta tags, see the Token Mappings topic in ArcSight
FlexConnector Guide.
Comparative_Operator is == for string comparison; =, >, and < for integer
comparison.
Compared_Value is a string or an integer. For string comparison, enclose the value in
double quotes (“ ”).
Contents of Email.vm and Informative.vm
The default Email.vm template file contents are:
## This is a velocity macro file...
## The following fields are defined in the velocity macro.
## event == the event which needs to be sent.
## EVENT_URL == root of the event alert.
## NOTIFICATION_URL == URL of the notifications page in ArcSight
Web
#parse ("Informative.vm")
This message can be acknowledged in any of the following ways:
1) Reply to this email. Make sure that the notification ID listed
in this message is present in your reply)
2) Login to the ArcSight Console and click on the notification
button on the status bar
3) Login to ArcSight Web at ${NOTIFICATION_URL}
To view the full alert please go to at ${EVENT_URL}
The default Informative.vm template file contents are:
=== Event Details ===
#foreach( $field in $introspector.fields )
#if( $introspector.getDisplayValue($event, $field).length() > 0 )

${field.fieldDisplayName}: $introspector.getDisplayValue($event,
$field)
#end
#end
How the Email.vm and Informative.vm Template Files
Work
Email.vm calls the secondary template file Informative.vm (#parse
(“Informative.vm”)). The Informative.vm file lists all the non-empty fields of an
event in the format fieldName : fieldValue.
Understanding the Customization Process
If you want to customize the template files to suit your needs, ArcSight recommends that
you create new secondary templates containing fields that provide information you want to
see in an e-mail for a specific condition.
For example, if you want to see complete details for an event—Threat Details, Source
Details, Target Details, and any other information—generated by all Snort devices in your
network, create a secondary template file called Snort.vm in
<ARCSIGHT_HOME>/config/notification, on your Manager, with the following lines:
=== Complete Event Details ===
Threat Details
Event: $introspector.getDisplayValue($event,"name")
Description:
$introspector.getDisplayValue($event,"message")
Severity:
$introspector.getDisplayValue($event,"severity")
------------------------------------------------------------------
--
Source Details
Source Address:
$introspector.getDisplayValue($event,"attackerAddress")
Source Host Name:
$introspector.getDisplayValue($event,"attackerHostName")
Source Port:
$introspector.getDisplayValue($event,"sourcePort")
Source User Name:
$introspector.getDisplayValue($event,"sourceUserName")
------------------------------------------------------------------
--
Target Details

Target Address:
$introspector.getDisplayValue($event,"targetAddress")
Target Host Name:
$introspector.getDisplayValue($event,"targetHostName")
Target Port: $introspector.getDisplayValue($event,"targetPort")
Target User Name:
$introspector.getDisplayValue($event,"targetUserName")
------------------------------------------------------------------
--
Extra Information (where applicable)
Transport Protocol:
$introspector.getDisplayValue($event,"transportProtocol")
Base Event Count:
$introspector.getDisplayValue($event,"baseEventCount")
Template:
/home/arcsight/arcsight/Manager/config/notifications/Snort.vm
------------------------------------------------------------------
--
Once you have created the secondary templates, you can edit the Email.vm template to
insert conditions that call those templates.
As shown in the example below, insert a condition to call Snort.vm if the
deviceProduct in the generated event matches “Snort”.
#if( $introspector.getDisplayValue($event, "deviceProduct") ==
"Snort" )
#parse("Snort.vm")
#else
#parse("Informative.vm")
#end
Customizing the template files
Follow these steps to customize the Email.vm and create any other secondary template
files to receive customized e-mail notifications:
1 In <ARCSIGHT_HOME>/config/notifications, create a new secondary template
file, as shown in the Snort.vm example in the previous section.
2 Save the file.
3 Edit Email.vm to insert the conditions, as shown in the example in the previous
section.
4 Save Email.vm.

Sample Output
If you use the Snort.vm template and modify Email.vm as explained in the previous
section, here is the output these templates generate:
Notification ID: fInjoQwBABCGMJkA-a8Z-Q== Escalation Level: 1
=== Complete Event Details ===
Threat Details
Event: Internal to External Port Scanning
Description: Internal to External Port Scanning Activity
Detected; Investigate Business Need for Activity
Severity: 2
------------------------------------------------------------------
--
Source Details
Source Address: 10.129.26.37
Source Host Name:
Source Port: 0
Source User Name: jdoe
------------------------------------------------------------------
--
Target Details
Target Address: 161.58.201.13
Target Host Name:
Target Port: 20090
Target User Name:
------------------------------------------------------------------
--
Extra Information (where applicable)
Transport Protocol: TCP
Base Event Count: 1
Template:
/home/arcsight/arcsight/Manager/config/notifications/Snort.vm
------------------------------------------------------------------
--
How to Respond
This message can be acknowledged in any of the following ways:

1) Reply to this email. Make sure that the notification ID listed
in this message is present in your reply)
2) Login to the ArcSight Console and click on the notification
button on the status bar
3) Login to myArcSight and go to the My Notifications
Acknowledgment page at
https://mymanager.mycompany.com:9443/arcsight/app?service=page/Not
ifyHome
To view the full alert please go to
https://mymanager.mycompany.com:9443/arcsight/app?service=external/EventInspector&
sp=SfInjoQwBABCGMJkA-a8Z-Q%3D%3D&sp=F&sp=F

Appendix F
The Archive Command Tool
You can use the archive command line tool to import and export resource information
stored in the ArcSight Database. You can use this tool in managing configuration
information, for example, importing asset information collected from throughout your
enterprise. You can also use this tool to archive resource information stored in the ArcSight
Database so that, for example, prior to installing new versions of ESM, you can simply
restore all the resource information after completing the installation.
When archiving information from the ArcSight Database, the archive command
automatically creates the archive files you specify, saving resource objects in XML format.
This documentation does not provide details on the structure of archive files and the XML
schema used to store resource objects for re-import into ESM. If you have any special
requirements for importing and exporting archive files, please contact your ArcSight
representative.
Archive Command Modes
The ArcSight archive command tool can be run in two basic modes, remote or
standalone. This command displays a resource in the archive menu list of resources only if
the user running the utility has top-level access to the resource. Access is different for each
mode.
“Archive Command Modes” on page 181
“Exporting Resources to an Archive” on page 183
“Importing Resources from an Archive” on page 184
“Syntax for Performing Common Archive Tasks” on page 187
You can use the packages feature to archive resources from and import
resource to your ArcSight Database. For more information about packages
and how to use them, see the Managing Packages topic in ArcSight Console
Online Help. For information about the packages command, see Appendix A
of this guide.

F The Archive Command Tool
Remote Mode
In remote mode, you can perform resource import or export operations from either an
ArcSight Manager or ArcSight Console installation and can perform archive operations while
ArcSight Manager is running.
arcsight archive -u Username -m Manager [-p Password] -f Filename
[-i | -sort] [-q] ...
When you run the archive utility in the remote mode, it runs as the user specified in the
command line. However, even users with the highest privilege level (administrator) do not
have top level access, for example, to the user resource ('All users'). Thus, the User
resource does not show up in the list of resources. You can export users with the -uri
option, but if you want to use the -u option, use the Standalone mode.
To export user resources, you can use the -uri option and specify a user resource to which
you have direct access. For example:
arcsight archive -u <username> -m <manager_hostname> -format
exportuser -f exportusers.xml -uri "/All Users/Administrators/John
Standalone Mode
In standalone mode, from the computer where ArcSight Manager is installed, you can
connect directly to the ArcSight database to import or export resource information,
however, ArcSight Manager must be shut down before you perform archive operations.
When you run the archive utility in standalone mode, it runs as RootUser. This is a special
system user which has top level access to all resources including the User resource (which
is 'All Users'), so, for example, User Resource shows up in the list of resources.
The basic syntax for the archive command in standalone mode is the following:
arcsight archive -standalone -f Filename [-i | -sort] [-q] ...
See the description for the archive command in Appendix A‚ ‚ on page 101 for more
information on this tool.
The cacerts file on the Manager host must trust the Manager's certificate. You
may have to update cacerts if you are using demo certificates by running:
arcsight tempca –ac
You do not need to run the above command if you run the archive command
from the Console.
Do not run the archive tool in standalone mode against a database currently in
use by an ArcSight Manager as it is possible to corrupt the database.
Both remote and standalone archive commands support the same optional
arguments.

You can use the standalone mode to export user resources. Because this mode runs with
system privileges, it provides access to the full User tree. Note that the standalone mode
only works from the archive command found in the Manager installation, and does not
work remotely. For example:
arcsight archive -standalone -format exportuser -f exportusers.xml
Exporting Resources to an Archive
1 Open a shell window or a Windows command prompt window, on a computer where
either ArcSight Console or ArcSight Manager is installed.
This command adds a certificate to the Manager’s key store for secure SSL communication
with the ArcSight Manager.
2 From the <ARCSIGHT_HOME>/bin directory, enter the arcsight archive
command along with any parameters you want to specify. For example (on Windows):
arcsight archive -u admin -p password -m hostname
-f c:archivearchive.xml
This command first logs into ArcSight Manager. It then displays a list of Resources available
for archiving.
3 Enter the number of the resource type to archive.
The archive command now displays a list of options that let you choose which
resource or group of resources within the resource type that you want to archive.
4 Choose the resource or group to archive.
After making your selection, you are prompted whether you want to add more
resources to the archive.
5 You can continue adding additional resources to the archive list. When you’ve finished,
answer no to the prompt
Would you like to add more values to the archive? (Y/N)
After it is finished writing the archive file, the archive command returns the command
prompt, from which you can enter additional commands or exit.
If you are on the computer where ArcSight Manager is installed, and are
running the archive command in remote mode for the first time, go to the
<ARCSIGHT_HOME>/bin directory and type the following:
arcsight tempca –ac
From the <ARCSIGHT_HOME>/bin directory, you can enter the command,
arcsight archive -h to get help. In that case, the command displays a list
of parameters you can specify with the archive command.
If the ArcSight Manager is running, you must specify archive commands in
remote mode, entering your user name, password, and Manager name to
connect to ArcSight Manager. To run the archive command in standalone
mode, accessing resources directly from the ArcSight Database, enter 
-standalone rather than -u <username> -p <password> -m <manager>.

Importing Resources from an Archive
1 Open a shell window or a Windows command prompt window, on a computer where
either ArcSight Console or ArcSight Manager is installed.
This command adds a certificate to the Manager’s key store for secure SSL
communication with the ArcSight Manager.
2 From the <ARCSIGHT_HOME>/bin directory, type arcsight archive with its
parameters and attach -i for import.
3 Select one of the listed options if there is a conflict.
Importing is complete when the screen displays Import Complete.
About Importing v3.x Content to a v4.x ESM System
If you import content to an ArcSight ESM v4.x system that was exported from a v3.x
system, make sure you are aware of the following:
Do not import system content from an ArcSight ESM v3.x or earlier system to an ArcSight
ESM v4.x system. If you do so, it can cause unpredictable consequences on the ArcSight
Manager and associated Console clients. The Packages feature in v4.x does not prevent
you from importing v3.x system content; therefore, you must be careful when importing
content into your v4.x system.
The above restriction does not apply to the custom content you may have created and
archived from an ArcSight ESM v3.x system. You can import any custom content to a v4.x
system if it does not reference any v3.x system content.
To identify whether your archived files contain ArcSight ESM v3.x system content, do one
of the following:
 Read through the archive XML file to locate the system content URIs.
If you are on the computer where ArcSight Manager is installed, and are
running the archive command in remote mode for the first time, go to the
<ARCSIGHT_HOME>/bin directory and type the following:
arcsight tempca -ac
If the ArcSight Manager is running, you must specify archive commands
in remote mode, entering your user name, password, and Manager name
to connect to ArcSight Manager. To run the archive command in
standalone mode, accessing resources directly from the ArcSight
Database, enter -standalone rather than -u <username> -p
<password> -m <manager>.
The predefined content with which ArcSight ships is referred to as system
content. In ArcSight v3.x, system content was available in System
Resource_Name sub-tree of each resource tree. Additional system content for
a few resources was available in the ArcSight System Administration sub-
tree. For example, system content for the Rules resource was available in
/All Rules/System Rules and system content for the Assets resource was
available in /All Assets/ArcSight System Administration and /All
Assets/System Assets. Refer to the complete list of system content URIs
listed below at the end of this section.

 Use the arcsight archive command with the list option to see the system content
URIs:
arcsight archive –action list –f <archive file name>
To remove/exclude system content from the archived file, run this command from
<ARCSIGHT_HOME>bin directory:
arcsight archivefilter -source <source_file_name> -xuri
<system_content_URIs_to_exclude> -f <target_file_name>
Here is a complete list of system content URIs that must be excluded before importing
custom content from an ArcSight ESM v3.x or earlier system to an ArcSight ESM v4.x
system:
/All Active Channels
/ArcSight Solutions
/Site Active Channels
/System Active Channels
/All Field Sets
/ArcSight Solutions
/Site Field Sets
/System Field Sets
/All Active Lists
/ArcSight Solutions
/Site Active Lists
/System Active Lists
/All Agents
/ArcSight Administration
/All Assets
/ArcSight Solutions
/ArcSight System Administration
/Site Assets/Disallowed Servers
/All Zones
/System Zones
/All Networks
/System Networks/Global
/Site Networks/Local
/All Locations
/System Locations/ArcSight

/All Cases
/ArcSight Solutions
/System Cases
/All Dashboards
/ArcSight Solutions
/Site Dashboards
/System Dashboards
/All Data Monitors
/ArcSight Solutions
/Site Data Monitors
/System Data Monitors
/All Filters
/ArcSight Solutions
/Site Filters/Device Type Filters
/System Filters
/All Partitions/
/All Profiles
/ArcSight Solutions
/Site Profiles
/System Profiles
/All Reports
/ArcSight Solutions
/System Reports
/All Rules
/ArcSight Solutions
/Real-time Rules
/System Rules
/All Stages/
/All Users

/Administrators
/Default User Groups
Syntax for Performing Common Archive Tasks
For manual importing, run this command in <ARCSIGHT_HOME>/bin:
arcsight archive -i -format preferarchive -f <file name>
-u <user> -m <manager hostname>
Before performing the import operation, you are prompted for a password to log in to the
ArcSight Manager.
For exporting:
arcsight archive -f <file name>
-u <user> -m <manager hostname>
Before performing the import operation, you are prompted for a password to log in to the
ArcSight Manager and use a series of text menus to pick which Resources are archived.
For scheduled/batch importing:
arcsight archive -i -q -format preferarchive
-f <file name> -u <user>
-p <password> -m <manager hostname>
For scheduled/batch exporting:
arcsight archive -u admin -p password -m arcsightserver
-f somefile.xml -uri “/All Filters/Geographic Zones/West
Coast”
-uri “/All Filters/Geographic Zones/East Coast”
Make sure you have read the topic “About Importing v3.x Content to a v4.x
ESM System” on page 184 before you perform any of the tasks listed in this
section.
You can specify multiple URI resources with the URI parameter keyword by
separating each resource with a space character, or you can repeat the URI
keyword with each resource entry.

Appendix G
TLS Configuration to Support FIPS
Mode
This appendix covers the following sections:
FIPS 140-2 is a standard published by the National Institute of Standards and Technology
(NIST) and is used to accredit cryptographic modules in software components. A
cryptographic module is either a piece of hardware or a software or a combination of the
two which is used to implement cryptographic logic. The US Federal government requires
that all IT products dealing with Sensitive, but Unclassified (SBU) information should meet
the FIPS 140-2 standard.
Configuring a component to run in FIPS 140-2 mode, requires that you set up TLS
configuration on the component. Since TLS is based on SSL 3.0, we recommend that you
“NSS Tools Used to Configure Components in FIPS Mode” on page 190
“Types of Certificates Used in FIPS Mode” on page 190
“Using a Self-Signed Certificate” on page 190
“Using a Certificate Authority (CA) Signed Certificate” on page 191
“Some Often-Used SSL-related Procedures” on page 203
“Setting up Server-Side Authentication” on page 209
“Setting up Client-Side Authentication” on page 209
“Changing the Password for NSS DB” on page 211
“Listing the Contents of the NSS DB” on page 212
“Veiwing the Contents of a Certificate” on page 212
“Setting the Expiration Date of a Certificate” on page 212
“Deleting an Existing Certificate from NSS DB” on page 213
“Replacing an Expired Certificate” on page 213
“Using the Certificate Revocation List (CRL)” on page 214
• Not all ESM versions or ArcSight Express models support the FIPS mode.
• PKCS #11 token support may not be available for all ESM versions and
ArcSight Express models.
Refer to the ESM Product Lifecycle Document available on the Customer
Support website for information on the platforms on which FIPS mode and
PKCS #11 Token are supported.

G TLS Configuration to Support FIPS Mode
have a good understanding of how SSL works. Please read the section “Understanding SSL
Authentication” on page 33 for details on how SSL works.
You have to perform some manual steps to set up the TLS configuration. This appendix
serves as a reference for the manual procedures to perform on ArcSight Manager, ArcSight
Console, and ArcSight Web.
NSS Tools Used to Configure Components in FIPS
Mode
Network Security Services (NSS) is a cross-platform cryptographic C library and a collection
of security tools. ArcSight ESM comes bundled with the following three basic NSS command
line tools:
 runcertutil - is a certificate and key management tool used to generate key pairs
and import and export certificates.
 runmodutil - is the NSS module configuration tool. It is used to enable or disable the
FIPS module and change Key Store passwords.
 runpk12util - is an import and export tool for PKCS #12 format key pairs (.pfx
files).
See Appendix A‚ ArcSight Commands‚ on page 101 for details on the above command line
tools. You can also refer to the ‘NSS Security Tools’ page on the Mozilla website for more
details on any of the above NSS tools (make sure to search for them as certutil, modutil, or
pk12util).
For online help on any command, enter the following command from a
component’s bin directory:
arcsight <command_name> -H
Types of Certificates Used in FIPS Mode
You can use either a self-signed certificate or a CA-signed certificate when setting up SSL
authentication on your ESM components.
Using a Self-Signed Certificate
The “Installing ArcSight ESM in FIPS Mode” appendix in the ArcSight ESM Installation and
Configuration Guide walks you through the steps to generate and use a self-signed
certificate when doing a fresh installation of ESM in FIPS mode.
To configure ArcSight SmartConnectors and ArcSight Logger, refer to their
respective documentation.
The runcertutil tool currently has a limitation that it cannot import the
certificate when the NSS DB is set to FIPS mode. In order to work around
this issue, you have to disable FIPS mode in the NSS DB, import the
certificate, and then re-enable FIPS mode.

Using a Certificate Authority (CA) Signed Certificate
In ESM, the Manager and ArcSight Web are both servers. You can use CA-signed
certificates for both of them. To use a CA-signed certificate, you have to first obtain the
signed certificate from the CA. The CA embeds the public key of the server and the CA’s
signature in the certificate. So, the Manager’s CA-signed certificate contains the public key
of the Manager along with the CA’s signature, and the Web’s CA-signed certificate contains
the public key of the Web along with the CA’s signature.
To obtain the CA-signed certificate, you have to generate a Certificate Signing Request
(CSR) on the server (Manager or the Web as the case may be). Next, you send the CSR to
the CA. Using the CSR, the CA then creates a certificate for the server and sends it back to
you. Once you receive the certificate from the CA, you have to import the certificate into
the server’s NSS DB.
You are also required to import the server’s certificate into any client that wishes to connect
to the server. Doing this allows the client to trust the server.
Here are the steps to perform on each component if you use CA-signed certificates:
Steps Performed on the Manager
1 Install the Manager by running its executable file.
2 When you get to the first configuration screen shown below, leave the wizard running
and open a command prompt window.
Make sure that your Manager’s nssdb does not contain any previously
imported/generated Manager certificate or key pair. To confirm this, list all the
contents of the nssdb by running the following from the Manager’s /bin
directory:
./arcsight runcertutil -K -d <ARCSIGHT_HOME>/config/jetty/nssdb
If you find a certificate or a key pair in the output of the command, delete it by
./arcsight runcertutil -D -n <certificate-alias> -d
<ARCSIGHT_HOME>/config/jetty/nssdb

3 Generate a key pair on the Manager by running the following from the Manager’s
/bin directory:
./arcsight runcertutil -G -d <ARCSIGHT_HOME>/config/jetty/nssdb
When prompted for password, enter “changeit” (without the quotes).
Enter random keyboard strokes when prompted, to generate the random seed used to
generate your key.
4 Verify key pair creation by entering the following command:
./arcsight runcertutil -K -d <absolute_path_to_Manager’s_nssdb>
Enter “changeit” when prompted for the NSS DB password. You should see something
similar to <0> rsa <key> in the output of the command.
5 Generate a certificate signing request (CSR) by running the following from the
Manager’s /bin directory:
To create a PEM ASCII format CSR file:
./arcsight runcertutil -R -s "CN=<hostname_or_IP>,
O=<Name_of_organization>,
L=<City_where_the_organization_is_located>,
ST=<State_where_organization_is_located>, C=<Country>" -a -o
<absolute_path_to_filename.csr> 
-d <ARCSIGHT_HOME>/config/jetty/nssdb
To create a DER binary file:
If you do not specify the absolute path to where you want the .csr file to be
placed (as shown in the example screen shot below), the .csr file gets placed
in the Manager’s <ARCSIGHT_HOME>.

ST=<State_where_organization_is_located>, C=<Country>" -o
-d <ARCSIGHT_HOME>/config/jetty/nssdb
Enter the password for the NSS DB when prompted. The default password is
“changeit” (without the quotes).
Enter random keyboard strokes when prompted to generate the random seed to
generate your key.
The CSR gets generated in the location specified by the -o option.
6 Go back to the installation wizard screen and choose No, do not upgrade. This is a
new manager setup to create a new, clean installation and click Next.
7 Next, you see the following screen:
Select the Run manager in FIPS 140-2 mode radio button and click Next.

8 The configuration wizard asks you to confirm that you have set up the NSS DB. Click
Yes.
9 Acknowledge that once you select the FIPS 140-2 mode, you cannot revert to the
default mode. Click Yes.
10 Follow the prompts in the next few wizard screens to complete the Manager
installation. Refer to “Installing ArcSight Manager” chapter in the ArcSight ESM
Installation and Configuration Guide for details on any screen.
11 Send the .csr file to your Certificate Authority.
The Certificate Authority sends you the signed Manager’s certificate which contains the
CA’s signature and the Manager’s public key.
12 After you receive the signed certificate from the CA, import it into the Manager’s NSS
DB by running these commands from the Manager’s /bin directory:
a Disable FIPS mode by running:
./arcsight runmodutil -fips false -dbdir
b Import the Manager’s CA-signed certificate that you received from your CA by
running:
./arcsight runcertutil -A -n <provide_an_alias_for_the_cert> 
-t "CT,C,C" -d <ARCSIGHT_HOME>/config/jetty/nssdb -i
<absolute_path_to_the_signed_certificate>
c Enable FIPS mode by running:
./arcsight runmodutil -fips true -dbdir
13 Start the Manager.
For the -t option, be sure to use CT,C,C protocols only and in the same
order that it is shown above.

Steps Performed on the Web
ArcSight Web plays a dual role. On one hand, it acts as a client to the Manager to which it
connects. On the other, it acts as a server to web browsers that connect to it. Therefore,
the Web authenticates the Manager but has to authenticate itself to web browsers.
To authenticate the Manager, the Web’s NSS DB should contain the Manager’s certificate.
At the same time, since the Web acts as a server to the web browsers that connect to it,
you should have a key pair and a certificate containing the Web’s public key in the Web’s
NSS DB. This allows the Web to authenticate iteself to the web browsers.
You import the Manager’s certificate into the Web’s webnssdb. To obtain a CA-signed
certificate for the Web, generate a key pair on the Web, generate a CSR on the Web, and
send the CSR to the CA. Lastly, after you receive the signed certificate from the CA, import
it into the webnssdb.
To accomplish all of the above:
1 Install ArcSight Web by running its executable file.
2 When you get to the first configuration screen shown below, leave the wizard running
3 Import the Manager’s certificate:
• Make sure that you have copied the Manager’s certificate to the machine
on which you install ArcSight Web.
• Make sure that your Web’s webnssdb does not contain any previously
imported/generated certificates or key pairs. To confirm this, list all the
contents of the webnssdb by running the following from the Web’s /bin
directory:
./arcsight runcertutil -K -d
<ARCSIGHT_HOME>/config/jetty/webnssdb
If you find a certificate or a key pair in the output of the command, delete
it by running the following command:
./arcsight runcertutil -D -n <certificate-alias> -d

a Disable FIPS mode in the Web’s webnssdb. This is required in order to import
certificates into the webnssdb.
b Import the Manager’s certificate into the webnssdb by running the following from
the Web’s bin directory.
-t "CT,C,C" -d <ARCSIGHT_HOME>/config/jetty/webnssdb -i
<absolute_path_to_the_Manager’s_certificate>
This is required in order for the Web to be able to authenticate the Manager.
c Enable FIPS mode by running:
4 Generate a key pair on the Web by running:
For the -t option, be sure to use CT,C,C protocols only and in the
same order that it is shown above.

./arcsight runcertutil -G -d
Enter the password for webnssdb when prompted. The default password is ‘changeit’
without the quotes.
Enter random keyboard strokes when prompted, to generate the random seed used to
generate your key.
5 Verify that the key pair got created by entering the following command:
./arcsight runcertutil -K -d <absolute_path_to_Web’s_webnssdb>
Enter “changeit” when prompted for the webnssdb password. You should see
something similar to <0> rsa <key> in the output of the command.
6 Generate a CSR in the webnssdb which you have to send to the CA to obtain a CA-
signed certificate for the Web:
O=<company_name>, L=<Location_of_the_company>,
ST=<State_where_company_is_located>, C=<country>" -a -o
<absolute_path_to_the_filename.csr> -d
This generates a CSR file that is placed in the location you had specified in the -o
option in the command.
Notes:
• Make sure the CN is either the IP address of the machine on which
ArcSight Web resides or its fully qualified domain name used in the
URL when you access ArcSight Web using a browser.
• If you do not specify the absolute path to where you want the .csr file
to be placed, the .csr file gets placed in the Web’s <ARCSIGHT_HOME>.

7 Go back to the wizard screen. Select No, I do not want to transfer the settings
and click Next.
8 Select Run web in FIPS 140-2 mode in the following screen and click Next:
9 The following prompt asks you whether you configured your webnssdb. Click Yes.
10 You see this warning message:
Click Yes.
11 When you get to the following screen, make sure that the Webserver Host name
exactly matches the host name that you had entered for the webserver when installing

the Manager. For example, if you had entered an IP address for the webserver in the
Manager setup, make sure to enter the IP address in this screen too.
12 Follow the prompts in the next few wizard screens and complete the wizard.
13 Send the .csr file to your Certificate Authority.
The Certificate Authority will send you the signed Web’s certificate containing the CA’s
signature and the Web’s public key.
14 After you receive the Web’s signed certificate from the CA, import it into the Web’s
webnssdb.
a Disable FIPS mode on the webserver by running the following command from the
Web’s /bin directory:
b Import the Web’s CA-signed certificate by running:
-t "CT,C,C" -d <ARCSIGHT_HOME>/config/jetty/webnssdb -i
<absolute_path_to_the_web_certificate>
The web browsers that connect to the webserver use the Web’s certificate to
authenticate the webserver.
c Enable FIPS mode by running the following from the Web’s bin directory:
15 Start ArcSight Web by running the following from its /bin directory:
./arcsight webserver
same order that it is shown above.

Steps Performed on the Console
You are required to import the Manager’s certificate into the Console’s nssdb.client.
This allows the Console to trust the Manager.
1 Install the Console by running its executable file.
2 When you get to the first configuration screen shown below, leave the Console running
3 Import the Manager CA certificate CA’s root certificate which you can obtain from the
CA that signed the Manager’s certificate:
a Set the Console’s nssdb.client temporarily to non-FIPS 140-2 mode by
running the following command from the Console’s
<ARCSIGHT_HOME>currentbin directory:
arcsight runmodutil -fips false -dbdir
<ARCSIGHT_HOME>currentconfignssdb.client
b Run the following command to import the CA’s root certificate:
Make sure that you have copied the Manager’s certificate to the machine on
which install the ArcSight Console.

arcsight runcertutil -A -n <provide_an_alias_for_the_cert> 
-t “CT,C,C” -d <ARCSIGHT_HOME>currentconfignssdb.client -
i <path_to_the_CA’s_root_certificate>
c Run the following command to enable FIPS mode in nssdb.client:
arcsight runmodutil -fips true -dbdir
<ARCSIGHT_HOME>confignssdb.client
order shown above.

4 Go back to the wizard and select No, I do not want to transfer the settings in the
following screen and click Next:
5 Select Run console in FIPS 140-2 mode and click Next.
6 The configuration wizard reminds you to set up the NSS DB. Click Yes.

7 Acknowledge that once you select the FIPS 140-2 mode, you cannot revert to the
default mode. Click Yes.
8 Follow the prompts in the next few wizard screens to complete the Console
installation. Refer to” Installing ArcSight Console” chapter in the ArcSight ESM
Installation and Configuration Guide for details on any screen.
When you start the Console. You should see a message saying that the Console is starting
in FIPS mode, as shown in the screenshot below.
Some Often-Used SSL-related Procedures
Here are some of the commonly used SSL-related procedures that are intended to serve as
a reference when installing or setting up ESM components in FIPS mode.
Generating a Key Pair in a Component’s NSS DB
This section explains how to generate a key pair in a component’s NSS DB. A component
that has to authenticate itself is required to have a key pair on it. For example, during
server-side authentication, since the server needs to authenticate itself to a client, the
server should have a key pair in its NSS DB and send its certificate which contains the
server’s public key to the client requesting it. The same is true for client-side authentication
where a key pair has to exist on the client. For self-signed certificate, the certificate gets
generated when generating a key pair.
On the Manager
1 Run the following command from the Manager’s <ARCSIGHT_HOME>/bin directory to
generate a key pair:
When you import or generate a key pair in a component’s NSS DB, if there is
a existing key pair/certificate that has the same CN as the one you create,
the runcertutil utility uses the existing alias for the newly created key pair
and ignore the alias you supplied in the runcertutil command line.

./arcsight runcertutil -S -s “CN=<hostname>” -v
<number_of_months_the_certificate_should_be_valid> -n mykey -k
rsa -x -t “C,C,C” -m 1234 -d <ARCSIGHT_HOME>/config/jetty/nssdb
where the hostname is the name of the machine on which your Manager is installed
and -v is the validity period of the certificate.
For example, if your hostname is myhost.arcsight.com, you would run:
./arcsight runcertutil -S -s “CN=myhost.arcsight.com” -v 6 -n
mykey -k rsa -x -t “C,C,C” -m 1234 -d
This generates a key pair and certificate with the alias mykey which is valid for 6
months from the current date and time in the Manager’s nssdb.
2 Enter the password for NDSS DB when prompted. The default password is “changeit”
(without the quotes).
3 Enter random keyboard strokes when prompted, to generate the random seed used to
generate your key.
On the Console
To create a key pair on the Console:
1 Run the following command from the Console’s bin directory:
arcsight runcertutil -S -s “CN=<External_ID_of_the_user>” -v
rsa -x -t “C,C,C” -m 4975 -d
For the -t option, be sure to use C,C,C protocols only and in the same
• Make sure to use “mykey” (without quotes) as the alias name for the
key pair as shown in the example.
• The -m serial number should be unique within nssdb
• The hostname is the short name or fully qualified domain name
depending upon how your ESM manager name was set up when you
installed the Manager.
• Using -v to set the validity period of your certificate is optional. If
you do not use this option, the certificate will be valid for 3 months
by default. Using -v is optional. If you choose to use it, see “Setting
the Expiration Date of a Certificate” on page 212 for details.

2 Enter the password for nssdb.client. The default password is ‘changeit’ without
quotes.
generate your key.
On ArcSight Web
To create a key pair on the Web server:
1 Run the following command from ArcSight Web’s /bin directory:
rsa -x -t “C,C,C” -m 2345 -d
2345 represents the serial number which has to be unique within the webnssdb and
hostname is the name of the machine on which ArcSight Web is installed.
2 Enter the password for webnssdb. The default password is ‘changeit’ without the
quotes.
generate your key.
Verifying Whether the Key pair Has Been Successfully Created
To verify whether the key pair has been successfully created in the nssdb, run the
following from the component’s <ARCSIGHT_HOME>/bin directory:
./arcsight runcertutil -L -d <path_to_the_component’s_NSS DB>
• CN is the External ID of the user you created when running the
Manager’s setup.
• The -m serial number should be unique within nssdb.client.
• Using -v is optional. If you choose to use it, see “Setting the
Expiration Date of a Certificate” on page 212 for details.
Notes:
• Make sure that this serial number is different from the serial number
used when you generated the Manager’s key pair. Since the
Manager’s certificate gets imported into the webnssdb, you need to
make sure that the serial number for the Web’s key pair is different
from the serial number used when generating the Manager’s key pair.
• Using -v is optional. If you choose to use it, see “Setting the
Expiration Date of a Certificate” on page 212 for details.
When you import or generate a key pair into NSS DB, if there is a
existing key pair/certificate with the same CN as the one you create, the
runcertutil utility uses the existing alias for the newly created key pair
and ignores the alias you supplied in the runcertutil command line.

Viewing the Contents of the Certificate
If you would like to check the contents of the certificate, you run this from the
component’s /bin directory:
./arcsight runcertutil -L -d <path_to_the_component’s_NSS DB> -
n <key_alias>
Exporting a Certificate
This section explains how to export a certificate from a component’s NSS DB. During an
SSL handshake, for server side authentication, you need to have the server’s certificate in
the NSS DB of both the server and the client. Export the server’s certificate from the
server’s NSS DB in order to import it into the client that wishes to connect to the server.
Likewise, for client side authentication, you need to have the client’s certificate in the NSS
DB of both the client and the server. Export the client’s certificate from the client’s NSS DB
in order to import it into the server to which the client connects.
From the Manager
Run the following command from the Manager’s <ARCSIGHT_HOME>/bin directory:
./arcsight runcertutil -L -n <alias_for_exported_certificate> -r -d
<ARCSIGHT_HOME>/config/jetty/nssdb -o
<absolute_path_to_where_you_want_certificate_exported>
For example:
./arcsight runcertutil -L -n managercert -r -d
<ARCSIGHT_HOME>/config/jetty/nssdb -o
/home/arcsight/arcsight/Manager-6391/ManagerCert.cer
This exportsthe Manager’s certificate into a file called ManagerCert.cer and places it in your
/home/arcsight/arcsight/Manager-6391 directory. The alias for this file is
managercert.
From the Console
To export the Console’s certificate run the following from the Console’s bin directory:
arcsight runcertutil -L -n <alias_for_exported_certificate> -r -d
<ARCSIGHT_HOME>currentconfignssdb.client -o
<absolute_path_to_where_you_want_certificate_exported>
From the Web
To export the Web’s certificate, run the following from the Web’s /bin directory:
If you do not specify the absolute path for the .cer file, it is placed in the
Manager’s <ARCSIGHT_HOME> directory.
If you do not specify the absolute path for the .cer file, it gets placed in the
Console’s <ARCSIGHT_HOME>.

./arcsight runcertutil -L -n <alias_for_exported_certificate> -r -d
<ARCSIGHT_HOME>/config/jetty/webnssdb -o
<full_path_to_where_you_want_certificate_exported>
Importing a Certificate into NSS DB
This section explains how to import a certificate into a component’s NSS DB. For server side
authentication, the server’s certificate needs to be imported into the client’s NSS DB. For
client side authentication, the client’s certificate needs to be imported into the server’s NSS
DB.
The NSS tool, certutil, is used to import a certificate into the NSS DB. The certutil
tool currently has a limitation that it cannot import the certificate when the component is
running in FIPS mode. In order to work around this issue, you have to disable FIPS mode
on the component first, then import the certificate, and lastly re-enable FIPS mode.
On the Manager
If you use a CA-signed certificate, import the Manager’s CA-signed certificate into the
Manager’s nssdb. In addition, if you set up client side authentication, import the client’s
certificate into the Manager’s nssdb. To import a certificate into the Manager’s nssdb:
1 Disable FIPS mode by runing the following from the Manager’s
<ARCSIGHT_HOME>/bin directory:
2 Run the following to import the certificate into the Manager’s nssdb:
./arcsight runcertutil -A -n
<provide_an_alias_for_the_certificate> -t “CT,C,C“ -d
<ARCSIGHT_HOME>/config/jetty/nssdb -i
<absolute_path_to_the_certificate_file>
3 Run the following command to re-enable the FIPS 140-2 mode:
If you do not specify the absolute path for the .cer file, it gets placed in the
Web’s <ARCSIGHT_HOME>.
If you are importing the Console’s certificate to set up client-side
authentication, make sure that you do NOT use the alias mykey for the
Console’s certificate when importing it into the Manager’s nssdb because
the nssdb already has the Manager’s certificate with the alias mykey in it.
All aliases in the nssdb should be unique.

On the Console
Import the Manager’s certificate into the Console that connects to the Manager. To import a
certificate into the Console’s nssdb.client:
1 Set the nssdb temporarily to non-FIPS 140-2 mode by running the following from the
Console’s <ARCSIGHT_HOME>bin directory:
arcsight runmodutil -fips false -dbdir
2 Run the following to import the certificate:
arcsight runcertutil -A -n <provide_an_alias_for_the_cert> -t
“CT,C,C” -d <ARCSIGHT_HOME>confignssdb.client -i
<absolute_path_to_certificate_file>
3 Run the following command to set the nssdb back to FIPS 140-2 mode:
arcsight runmodutil -fips true -dbdir
On ArcSight Web
To import a certificate on ArcSight Web:
1 Run the following from ArcSight Web’s <ARCSIGHT_HOME>/bin directory to
temporarily disable the FIPS 140-2 mode in order to import the certificate:
2 Run the following to import the Manager’s certificate into ArcSight Web’s webnssdb:
./arcsight runcertutil -A -n <provide_an_alias_for_the_cert> -t
“CT,C,C” -d <ARCSIGHT_HOME>/config/jetty/webnssdb -i
<absolute_path_to_the_certificate_file>
3 Run the following to re-enable the FIPS 140-2 mode:
Importing an Existing Key Pair into the NSS DB
If you already have an existing key pair, you can use it instead of generating a new key pair
on a component. This procedure instructs you how to import an existing key pair into a
component’s NSS DB.

1 Export the key pair using a tool, such as keytoolgui, and be sure to export the key
pair with the name you gave it. An alias is required in order to import the key pair into
NSS DB.
2 Import the .pfx file into NSS DB using the pk12util tool. Make sure that the alias of
the key pair being imported does not match the alias of a pre-existing key pair in the
component’s NSS DB. If the key pair being imported has an alias that matches a pre-
existing key pair, the key pair fails to import citing an error:
PKCS12 decode validate bags failed: The user pressed cancel.
Run the following command from the component’s /bin directory:
On the Manager:
./arcsight runpk12util -i <absolute_path_to_mykey.pfx> -d
On the Web:
./arcsight runpk12util -i <absolute_path_to_mykey.pfx> -d
On the Console:
arcsight runpk12util -i <absolute_path_to_mykey.pfx> -d
3 Run the following from the component’s <ARCSIGHT_HOME>/bin directory to verify
that the key pair has been imported correctly. Note that the alias of the key pair that
you just imported in the NSS DB is the same as the alias of that key pair in the .pfx
file, in our example, mykey.
On Manager:
./arcsight runcertutil -L -d <ARCSIGHT_HOME>/config/jetty/nssdb
On Web:
./arcsight runcertutil -L -d
You should see the alias of the imported key pair in the output.
Setting up Server-Side Authentication
When you install a component in FIPS mode, you set it up for server-side authentication.
Setting up client-side authentication is optional.
The ArcSight ESM Installation and Configuration Guide walks you through the steps for
installing ESM with server-side authentication.
Setting up Client-Side Authentication
SSL 3.0 supports client-side authentication. TLS is based on SSL 3.0. ArcSight ESM uses
TLS and supports client-side authentication.
The client side authentication takes place after the initial handshake (after the Manager
has authenticated itself to the Console). The Manager then requests the Console for its
(Console’s) certificate. The Console in turn sends its certificate to the Manager. The
Manager has to be configured to accept the Console’s certificate. In other words, the

Console’s certificate must exist in the Manager's nssdb prior to the Manager authenticating
the Console. With this high level overview in mind, here are the steps you need to perform
to set up client-side authentication.
If you plan to use self-signed certificate for the Console:
1 Stop the Console if it is running.
2 Generate a key pair in the Console’s nssdb.client. Follow the steps in “Generating
a Key Pair in a Component’s NSS DB” on page 203 (“On the Console” subsection). This
automatically generates a self-signed certificate on the Console’s NSS DB.
Alternatively, you can use an existing key pair which you have to import into the
Console’s NSS DB. See “Importing an Existing Key Pair into the NSS DB” on page 208
for details.
3 Export the Console’s certificate. See the section “Exporting a Certificate” on page 206
(“From the Console” subsection) for detailed instructions.
4 Stop the Manager if it is running.
5 Import the Console’s certificate into the Manager’s nssdb. See the section “Importing
a Certificate into NSS DB” on page 207 (“On the Manager” subsection) for details.
6 Restart the Manager, then Console.
If you plan to use CA-signed certificate for the Console:
1 Stop the Console if it is running.
2 Generate a key pair on the Console. See the “Generating a Key Pair in a Component’s
NSS DB” on page 203 for details.
3 Generate a CSR on the Console by running the following from the Console’s bin
directory:
arcsight runcertutil -R -s "CN=<hostname_or_IP>,
ST=<State_where_organization_is_located>, C=<Country>" -a -o
-d <ARCSIGHT_HOME>currentconfignssdb.client
4 Send the CSR file to your CA and obtain a signed certificate from your CA.
5 Import the CA-signed certificate into the Console’s nssdb.client. See “Importing a
Certificate into NSS DB” on page 207 (subsection “On the Console”) for details.
6 Stop the Manager if it is running.
Make sure that you do NOT use the alias mykey for the certificate when
importing it into the Manager’s nssdb because the nssdb already has the
Manager’s certificate with the alias mykey in it. All aliases in the nssdb must be
unique.
If you do not specify the absolute path to where you want the .csr file to
be placed, the .csr file gets placed in the Console’s <ARCSIGHT_HOME>.

7 Import the Console’s CA-signed certificate into the Manager’s nssdb. See “Importing a
Certificate into NSS DB” on page 207 (subsection “On the Manager”) for details.
Changing the Password for NSS DB
ESM ships with a default password for the NSS DB, “changeit” (without quotes). ArcSight
recommends that you change the password on each component before moving to a
production environment. To do so:
1 Disable the FIPS mode in NSS DB by running the following from the component’s /bin
directory:
<absolute_path_to_the_component’s_NSS DB>
2 Run the following to list the NSS DB’s token name:
./arcsight runmodutil -list -dbdir
3 Change the token’s password by running the following from the component’s /bin
directory:
./arcsight runmodutil -changepw “<name_of_token>” -dbdir
4 Enter the old password and a new password and confirm it when prompted.
5 Re-enable FIPS mode on the NSS DB:
6 Open the properties file:
On the Manager:
Located in: <ARCSIGHT_HOME>/config/server.properties.
Change
server.privatekey.password.encrypted=<encrypted_password>
to
server.privatekey.password=<new_unencrypted_password>
On the Console:
Located in <ARCSIGHT_HOME>currentconfigconsole.properties
Change
console.privatekey.password.encrypted=<encrypted_password>
to
console.privatekey.password=<new_unencrypted_password>
On the Web:
Located in <ARCSIGHT_HOME>/config/webserver.properties.
Change

webserver.privatekey.password.encrypted=<encrypted_password>
to
webserver.privatekey.password=<new_unencrypted_password>
7 Run the setup program from the component’s /bin directory:
Manager:
Console:
arcsight consolesetup
Web:
./arcsight webserversetup
and accept all the defaults in the wizard. This is required in order to obfuscate the
password that you had entered in plain text.
Listing the Contents of the NSS DB
After you import a certificate or generate a key pair in a component’s NSS DB, you can
verify that the certificate import was successful or the key pair has been successfully
generated. You can do this by listing the contents of the NSS DB. To view the contents of a
component’s NSS DB, run the following command from the component’s /bin directory:
./arcsight runcertutil -L -d <absolute-path-to-the_component’s_NSS
DB>
You should see the alias of the certificate you just imported or the alias for the key pair you
generated.
Veiwing the Contents of a Certificate
To view the contents of a certificate, run the following command from the component’s
/bin directory:
./arcsight runcertutil -L -d <absolute-path-to-the_component’s_NSS
DB> -n <certificate_alias>
Setting the Expiration Date of a Certificate
To set the expiry date of the certificate, you have to do so when generating the key pair.
Once you have generated the key pair, you cannot change the expiration date on the
certificate and the certificate expires in three months by default.
<number_of_months_the_certificate_should_be_valid> -n mykey -k rsa
-x -t “C,C,C” -m 1234 -d <component’s_NSS DB_path>
For the -t option, be sure to use C,C,C protocols only and in the same order
that it is shown above.

You specify the validity of the certificate with the -v <number_of_months> option. The
value that you provide with -v calculates the number of months that the certificate is valid
starting from the current time. You can use the -w <offset_months> along with -v to
set the beginning time for the validity. The -w <offset_months> if used, calculates the
start time of the certificate validity and the offset is calcualted from the current system
time. If you do not use the -w option, the current time is used as the start time for the
certificate validity. See the subsection, “runcertutil” in Appendix A‚ ArcSight Commands‚ on
page 101 for details on the -v and -w options.
Deleting an Existing Certificate from NSS DB
To delete a certificate from a component’s NSS DB:
1 Stop the component if it is running.
2 Run the following command from the component’s /bin directory:
./arcsight runcertutil -D -n <certificate-alias> -d <absolute-
path-to-the_component’s_NSS DB>
Replacing an Expired Certificate
When an existing certificate/nssdb expires on a server (Manager or Web), you need to
replace it with a new one. To replace the certificate:
1 Stop the server if it is running.
2 Delete the expired certificate from the server’s NSS DB. See “Deleting an Existing
Certificate from NSS DB” on page 213 for details.
Since the common name (CN) for the new certificate is identical to the CN in the old
certificate, you are not permitted to have both the expired as well as the new
certificate co-exist in the NSS DB.
3 In case of CA-signed certificate, replace the certificate by importing the new certificate
into the server’s NSS DB.
In case of self-signed certificate, you have to generate a key pair on the server. See
“Generating a Key Pair in a Component’s NSS DB” on page 203 for details on how to
do this. Generating the key pair automatically generates the certificate.
4 On every client that connects to the server, make sure to delete the old expired server
certificate from the client’s NSS DB and import the server’s newly generated certificate.
For example, if your Manager’s certificate has expired, you have to
a Delete the expired certificate from the Manager’s nssdb.
b Generate a new key pair, which automatically generates a new self-signed
certificate.
c Export the newly generated certificate from the Manager.
d Delete the expired Manager’s certificate from the Console’s and Web’s NSS DB.
e Import the Manager’s new certificate into the Console’s and Web’s NSS DB.

Using the Certificate Revocation List (CRL)
Starting in v4.0 SP2, ArcSight ESM supports the use of CRL to revoke a CA-signed
certificate which has been invalidated. The CA that issued the certificates also issues a CRL
file which contains a signed list of certificates which it had previously issued that it now
considers invalid. ArcSight Manager checks the client certificates against the list of
certificates listed in the CRL and denies access to clients whose certificates appear in the
CRL.
Before you use the CRL feature, make sure:
 Your certificates are issued/signed by a valid Certificate Authority or an authority with
an ability to revoke certificates.
 The CA’s certificate is present in the Manager’s
<ARCSIGHT_HOME>/config/jetty/nssdb directory
In the case of client-side authentication, the Manager validates the authenticity of the
client certificate using the certificate of the signing CA.
 You have a current CRL file provided by your CA.
The CA updates the CRL file periodically as and when additional certificates get
invalidated.
To use the CRL feature:
1 Make sure you are logged out of the Console.
2 Copy the CA-provided CRL file into your Manager’s
<ARCSIGHT_HOME>/config/jetty/crls directory.
After adding the CRL file, it takes approximately a minute for the Manager to get
updated.
Migrating an Existing Default Mode ESM Installation
to FIPS Mode
You can migrate your existing default mode ESM installation to FIPS mode. Refer to the
ArcSight ESM Installation and Configuration Guide for details.

Appendix H
Monitoring System Health
This appendix provides some guidance about some of the configuration you can perform
and some of the stock content you can use for monitoring system health. (This appendix
does not attempt to list all stock content for monitoring system health.)
Overview
ArcSight ESM performs self-auditing and self-monitoring, using ESM and component event
sources. When the ESM, appliances, and SmartConnectors perform certain self-generated
system operations (particularly system statistics and health monitoring), they each
generate a corresponding event. ArcSight internal events can be leveraged to build content
that provides a centralized/unified view of the health of an ArcSight deployment.
This appendix details how to configure various components to send this information to a
Manager, allowing comprehensive monitoring of the system health of your ArcSight
deployment.
What to Monitor
Two types of internal events are generated by all ArcSight components:
 Status Monitor Events – periodic statistics about system health such as EPS and
database free space.
 Audit Events – Report actions in real time such as user authentication, activity, and
resource modification.
For monitoring system health, it is the status monitor event that is of primary concern. You
can configure appliances and connectors to forward these events to the Manager. ESM
monitors its own local critical system events and the status monitor events sent from
components. If any events match its alert criteria (indicating a critical situation), ESM
provides a summary of events for further investigation and a drill-down view.
“Overview” on page 215
“ESM Component Configuration” on page 218
“ESM Content Configuration” on page 219

H Monitoring System Health
The diagram below is an example of a common scenario that shows the flow of monitor
events through an ArcSight appliance ecosystem.
A typical implementation targets the following network elements:
 Availability—Monitor critical devices, ArcSight connectors, appliances, and ESM
 Performance—CPU Usage, memory usage
 Network speed—Current EPS, EPS over time, inbound/outbound traffic
 Disk and Storage—Monitor disk usage and disk free space on appliances and ESM
In monitoring dependent components, ArcSight recommends a focus on the three most
typical components: ArcSight SmartConnectors, appliances, and ESM.
ArcSight Appliances
The internal monitoring events of an ArcSight appliance might monitor CPU usage, memory
usage, current EPS, historical EPS, network interface statistics, and available disk usage.
The following table shows a subset of appliance internal events that are most relevant for
monitoring system health.
Appliance Internal Events
CPU Statistics • Current value
Disk Statistics • Disk space
• Read/Write
Event Statistics • EPS (receiver, forwarder)
• Event count (receiver, forwarder)
Memory Statistics • JVM memory
• Platform memory

You can find a description of system health events for ArcSight Logger in “Monitoring
System Health” in the ArcSight Logger Administrator’s Guide.
You can find a description of system health events for ArcSight Connector Appliance in
“Audit Logs” in the ArcSight Connector Appliance Administrator’s Guide.
ArcSight ESM
ArcSight ESM has a number of statistical monitors and alarms for every component of the
ArcSight ecosystem. It can monitor SmartConnectors, database performance, resource
exhaustion and has a number of reactive mechanisms such as notifications, SNMP
forwarding, open cases and executing scripts to deal with system or hardware failures in
real time. The following table shows a subset of internal events that are most relevant for
monitoring system health. For a list of audit events, see “Audit Events” in the ArcSight ESM
User Guide.
Network Statistics • Inbound usage
• Outbound usage
ESM Internal Events
Resource Statistics • Open resource count
• Queries/evaluations per second
Resource Framework Statistics • Inserts
• Updates
• Deletes
Rules Engine Statistics
(CPU, memory)
• Events in rule engine
• Events matching rules
• Rate of correlated events
Event Border Statistics • Event count
• Insert time
• Retrieval time
Main Flow Statistics • EPS (count since last monitor event)
• Events (count since startup)
Side Table Statistics • Size
• Insert
• Cache (misses/hit rate)
Database Statistics • Free Space
• Read/Write
Appliance Internal Events

ESM Component Configuration
Configuring SmartConnectors
In addition to normalizing and sending compressed events to Logger or ESM, connectors
can alsoConnectors monitor the management connection and availability of the originating
event sources.
If for some reason ESM or Logger becomes unavailable, a SmartConnector caches all the
data locally, and when connectivity to Logger resumes, send on the events. The following
table shows a subset of internal events that are most relevant for monitoring system
health.
The Connectors for your critical devices should be configured to send the "Connector
Device Status" events to the ArcSight Manager periodically. To do this, configure the
Connector to enable device status monitoring using the Connectors resource editor.
1 In the Navigator panel, go to Connectors and navigate to the Connector you want to
configure.
2 Right-click the Connector and select Configure.
3 In the Connector editor in the Inspect/Edit panel, scroll down to the Processing
section. In the Enable Device Status Monitoring (in milliseconds) field, enter how often
you want the Connector to send Device Status Events.
 For example, if the value is set to 300000, the Connector sends status events for
all its devices every 5 minutes (300000 milliseconds).
 If the value is set to -1, the Connector sends no Device Status events.
For more about enabling device status monitoring and configuring SmartConnectors, see
the ArcSight SmartConnector User’s Guide.
Configuring the Connector Appliance
To configure the Connector Appliance to forward system health events, you need to add
the Syslog Daemon connector to a container, set runtime parameters, and configure audit
forwarding on the container. You can skip the steps below that are already done.
1 Upload an ESM Certificate to Connector Appliance so that the appliance and Manager
can communicate. Refer to the section "CA Certs Repository" in the ArcSight
Connector Appliance Administrator's Guide.
Connector and Device Events
Device Statistics • Last event received
• Total number of events
• Event count Since last call
Connector Flow Statistics • Event rates
• Cache size
Connector Audit Events • Start/stop
• Heartbeat
• Cache statistics

For information about SSL Authentication and certificates, refer to the section
“Understanding SSL Authentication” in the “Configuration” chapter of the ArcSight ESM
Administrator's Guide.
2 Add the ESM certificate to a Container. Refer to the section "Managing Certificates on a
Container" in the ArcSight Connector Appliance Administrator's Guide.
3 Add the Syslog Daemon connector to the container to which you added the certificate.
Refer to the section "Adding a Connector" in the ArcSight Connector Appliance
When choosing a destination, select ArcSight Manager (encrypted).
4 Edit these runtime parameters for the Syslog Daemon connector:
 Set the Preserve System Health Events parameter to Yes.
 Set the Enable Device Status Monitoring (in milliseconds) field, to a positive
number. The minimum interval is one minute, so use at least 60,000 ms. Smaller
values result in one-minute intervals. Entries that are not a positive integer turn
the feature off.
See "Editing Destination Runtime Parameters" in the ArcSight Connector Appliance
5 Configure audit forwarding for the container that has the Syslog Daemon connector.
Refer to the section "Audit Forwarding" in the ArcSight Connector Appliance
Configuring Logger
Logger is one of the many appliances from which system health events can be generated,
then sent directly to a Manager. To initiate this communication, refer to the “Configuration”
chapter in the ArcSight Logger Administrator’s Guide. The section on “Event Input/Output”
describes how to set up Logger to forward events to ESM.
Configuring ESM
You can also use a Forwarding Connector to communicate health-related events from a
source Manager to a destination Manager, if you have such a hierarchical arrangement. For
information, refer to the “Configuration” chapter of the ArcSight SmartConnector
Configuration Guide for Forwarding Connectors.
ESM Content Configuration
Configure Critical Device Not Reporting Resources
The ArcSight Administration content includes resources that monitor the devices in your
network and send a notification when one of your critical devices is down. This content
Audit events for alerts are only written to the Internal Storage group and not
forwarded to ESM by default. If you need to forward these audit events to
ESM, please contact Customer Support for assistance. Please note that this
change applies only to audit events generated for alerts; other audit events
are unaffected.

functions off the Device Status events sent by SmartConnectors that you configured in
“Configuring SmartConnectors” on page 218.
The Device Reporting rules reference the White List filters for which devices to track and
insert in the Reporting Devices active list.
Configure White List Filters
The White List - Devices filter tells the Devices Reported rule which devices to track that
send Device Status events to the Manager. By default, the condition in the filter is True,
which means that all the devices that send Device Status events are inserted in the
Reporting Devices active list.
Modify this filter to choose only the devices you want to insert in the Reporting Devices
active list. Entries in this active list never expire.
Resource Type Universal Resource Identifier (URI) Resource Name
Filter /All Filters/ArcSight
Administration/Connectors/System
Health/Custom/
White List -
Devices
Filter /All Filters/ArcSight
Health/Custom/
White List - Critical
Devices
Rule /All Rules/ArcSight
Health/
Device Reported
Health/Custom/
Critical Device
Reported
Health/Custom/
Critical Device Not
Reporting
Active List /All Active Lists/ArcSight
Health/Custom/
Reporting Devices

The White List - Critical Devices filter tells the Critical Device Reported rule which devices to
track that send Device Status events and are also categorized as criticality High (All
Asset Categories/System Asset Categories/Criticality/High).
Modify this filter to choose the critical devices you want to monitor closely and about which
you want to be notified when they are not reporting.
The devices in Reporting Devices active list are likely to be a subset of the devices in the
Reporting Device active list. By default, the filter picks all the assets that are categorized as
/All Asset Categories/System Asset Categories/Criticality/High.
Create conditions that match your critical devices, and categorize your critical assets (or
zones) as /All Asset Categories/System Asset
Categories/Criticality/High.
To modify the filters to select only the devices you specify:
1 In the Navigator panel, navigate to the White List filters (/All
Filters/ArcSight Administration/Connectors/System
Health/Custom/) and double-click the one you want to modify to open it in the
Inspect/Edit panel.
2 In the Filter editor in the Inspect/Edit panel, select the Filter tab.
 White List - Devices filter: Delete the default condition True (select the
condition and press Delete).
 White List - Critical Devices filter: Leave the Attacker Asset ID and Attacker
Zone conditions in place. These identify the asset as being categorized as
criticality high.
3 Construct an expression that captures the devices you want the rule to evaluate.
 White List - Devices filter: Select event1 and add an AND operator (click the
AND icon ). Use the event fields grid to build the condition, or right-click
event1 and select New Condition.
 White List - Critical Devices filter: Select event1 and use the event fields
grid to build the condition, or right-click event1 and select New Condition.
Depending on the devices you want to capture, you can use device vendor/product,
asset categories, and other conditions.
• Use Device Custom strings. You can use Device Custom strings to
express device vendor and device product fields. Device Custom
String1 is the device vendor (such as Microsoft), Device Custom
String2 is the device product (such as Microsoft Windows). For
example:
Device Custom String1 = Device Vendor ABC
Device Custom String2 = Device Product XYZ (This selects all the
devices with that device vendor/product.)
• Use Attacker fields. The attacker fields correspond to the device.
Use these fields to specify an IP address, a zone or an asset category
using the “Attacker” fields, and the appropriate operator. For
example:
Attacker Zone = /All Zones/... (This checks if the device is in a
zone.)
• Use Assets conditions. Use the Assets condition button to check if
a device is in one or more asset categories. For example:
Attacker Asset ID inGroup /All Asset Categories/...

4 Click OK to apply changes and close the Filter editor.
For more about working with the Common Conditions Editor, see the online Help topic
Common Conditions Editor.
Configure Critical Device Not Reporting Rule
The Critical Device Not Reporting rule is disabled by default. Enable the rule if you want to
be notified when one of your critical devices is down. Enable the rule only after you
modified the White List - Critical Devices filter.
To enable the rule:
1 In the Navigator panel, go to Rules > All Rules > ArcSight Administration >
Connectors > System Health > Custom.
2 Right-click the rule Critical Device Not Reporting and select Enable Rule.
To enable the Create New Case action if a critical device goes down:
To create a case when the rule conditions are met, edit the Create New Case action to give
it an owner and enable the action.
1 Select the Create New Case action and click Edit in the toolbar at the top of the
Actions tab.
2 In the Edit Action dialog box in the Owner drop-down menu, navigate to and select an
appropriate user. Click OK.
3 Select, then right-click the Create New Case action and select Enable. Click OK.
Configure Connector Monitoring Resources
The ArcSight ESM content provides the following resources that monitor the operational
status of SmartConnectors configured on the ArcSight Manager, as well as those configured
to send events to ArcSight Loggers that are forwarding events to the ArcSight Manager.
Resource
Type
Universal Resource Identifier (URI) Resource Name
Health/
Connector Up
Health/
Connector Down
Health/
Connector Still Down
Health/
Connector Caching
Health/
Connector Still Caching
Health/
Connector Cache
Empty

The Connector Discovered or Updated rule monitors all connection and cache status
events, whether generated by SmartConnectors or by the ESM Manager. The correlation
event from this rule is used by other rules to update connector status.
The following rules are used to identify connection status:
 Connector Down
 Connector Up
 Connector Still Down
The following rules are used to identify caching status:
 Connector Caching
 Connector Still Caching
 Connector Dropping Events
 Connector Cache Empty
The next two sections provide information about configuration options for these rules.
Health/
Connector Dropping
Events
Health/
Connector Discovered
or Updated
Health/
Connector Information
Health/
Connectors - Down
Health/
Connectors - Caching
Health/Custom/
Black List - Connectors
Active Channel /All Active Channels/ArcSight
Health/
Connector Connection
Status Events
Active Channel /All Active Channels/ArcSight
Health/
Connector Caching
Events
Dashboard /All Dashboards/ArcSight
Health/
Connector Connection
and Cache Status
Resource
Type
Universal Resource Identifier (URI) Resource Name

Configuring Active Lists for Connector Information and Up or
Down Status
Connector Information
The Connector Information active list collects information about connectors that have
reported into the system, as well as information from the Manager when the
SmartConnector is first registered. A SupportInformation column in the list is pre-populated
as follows:
'poc= | email= | phone= | dept= | action='.
If you have SmartConnectors that are maintained by other individuals or organizations, you
can enter their contact information for each connector.
Connectors - Down
By default, the attributes for the Connectors - Down active list Time to Live (TTL) are set to
20 minutes. A connector down for fewer than 20 minutes is considered to be down for a
short term.
After 20 minutes, the entry for this active list expires and the connector information is
moved to the Connectors - Still Down active list, unless the connector comes back up
before 20 minutes.
Connectors - Caching
By default, the attributes for the Connector - Caching active list TTL are set to 2 hours. A
connector that has been caching for fewer than 2 hours is considered to be caching for a
short term. Connectors caching for up to 2 hours are not considered to be a problem.
After 2 hours, the entry for this active list expires and the connector information is moved
to the Connectors - Still Caching active list, unless the connector cache is emptied in fewer
than two hours, and it is removed by the Connector Cache Empty rule.
Rules Relating for Connector Up or Down Status
Connector Up, Connector Down
The Connector Up and Connector Down rules detect SmartConnectors that are started and
reporting events, and those that are shut down. These rules can send a notification (if
notifications are enabled) when Connectors have been down for a certain period of time
(by default, a TTL of 20 minutes in the Connectors - Down active list).
Excluding Some Connectors from Being Evaluated
In some situations, you might want to exclude certain Connectors from being evaluated by
the Connector Up and Connector Down rules:
 You have Connectors that you start and stop manually. For example, if you start a
TestAlert connector to replay some events, then stop it when you are done, and you
don’t want to get a notification saying that the Connector is down every 20 minutes
until you restart it.
 After installing and configuring ArcSight, you get unwanted notifications about
Connectors going down. You can opt to not receive Connector down notifications from
those Connectors.
 You have a Connector scheduled to run once every week (such as a vulnerability
scanner), and the Connector is otherwise down in the time in between.
 You are testing a new Connector and you are starting and stopping it frequently during
the set-up process.

For these situations, the Connector Up and Connector Down rules points to the Black List -
Connectors active list, as shown in the following figure.
To exclude certain SmartConnectors from being evaluated by these rules, enter the
SmartConnector’s URI and IP address in the Black List - Connectors active list, using the
following steps:
1 In the Navigator panel, go to Lists > Active Lists > All Active Lists > ArcSight
Administration > Connectors > System Health > Custom.
2 Right-click the active list Black List - Connectors and select Edit Active List.
3 In the Active List Editor in the Inspect/Edit panel, click Add Entry.
4 In the ActiveList Entry Editor, enter the URI of the SmartConnector (starting with /All
Connectors) and the Connector’s IP address and click Add, as in the following
example:
5 Repeat steps 3 and 4 for every SmartConnector you want to exclude from the
Connector Up and Connector Down rules.
For more about working with active lists, see the topic Managing Active Lists in the
ArcSight ESM User’s Guide.
You can copy and paste the URI and the IP addresses from the Connector
Information active list.

Populating Active Lists from an Imported CSV File
1 In the Navigator panel, navigate to the active list you want to configure (Lists >
Active Lists).
2 Generate a CSV file with the values with which you wish to populate the active list, and
save it to a directory on the Console system.
3 Right-click the active list you wish to import the values into and select Import CSV
File...
4 In the Open dialog box, navigate to and select the CSV file and click Open.
The Connector Still Down, Connector Still Caching, and Connector Dropping Events rules
have two actions that are disabled by default:
 Send Notification: Identifies whether an acknowledgement is required, as well as the
actual notification text and its destination.
 Create New Case: Specifies the case name, its priority, whether to include the base
events, and the group in which the case is included.
These actions are disabled by default because of several possible reasons; for example,
users might not have set up notification destinations, users might not have use cases, or
the rate of creation might be higher than users prefer.

A
About
Migrating from one certificate type to another 71
ACLReportGen command 102
actors
configuring 88
Adjusting
Console Memory 23
agent logfu command 102
agent tempca command 103
agentcommand command 103
agentsetup command 104
agentsvc command 104
agenttempca command 105
agentup command 105
arcdbutil command 105
arcdt command 105
archive command 106
archivefilter command 110
archivewizard command 111
ArcSight Console
FIPS setup 200
ArcSight Manager
Decoupled Process Execution 10
FIPS setup 191
Service Setup on Windows 12
ArcSight Manager or ArcSight Web Service Setup on 
Unix Platforms 13
authentication
server-side 209
authenticationclient-side 209
B
Backing up ArcSight Databases 95
bleep command 111
bleepsetup command 112
C
certificate
certificate authority 191
expiration 212
export 206
import 207
import CA-signed 194
in FIPS 190
revocation list (CRL) 214
signing request 191
view contents 206, 212
changepassword command 112
Changing
ArcSight Manager Ports 74
Console and ArcSight Web Session Timeouts 75
Manager Properties Dynamically 21
Oracle Initialization Parameters 93
Checking Passwords with Regular Expressions 76
checklist command 113
cipher suites 37
command help 190
commands
ACLReportGen 102
agent logfu 102
agentsetup 104
agentsvc 104
agenttempca 105
agentup 105
arcdbutil 105
arcdt 105
archive 106
archivefilter 110
archivewizard 111
bleep 111
bleepsetup 112
changepassword 112
checklist 113
console 113
consolesetup 114
database pc 114
database pm 115
database xts 115
databasesetup 116
dbcheck 116
dbview-generator 116
deploylicense 117
downloadcertificate 117
dropslpartitions 118
exceptions 118
execproc 119
execprocsvc 119
export_system_tables 120
flexagentwizard 120
groupconflictingassets 121
idefensesetup 121
import_system_tables 122
keytool 122
keytoolgui 123
kickbleep 123
listsubjectdns 123
logfu 124
manager 124
managerinventory 125
Index

Index
manager-no-wrapper 125
manager-reload-config 125
managersetup 126
managerstop 126
managersvc 127
managerthreaddump 127
managerup 127
monitor 128
netio 128
package 129
portinfo 130
querytuner 131
reenableuser 133
refcheck 133
regex 133
replayfilegen 133
resetpwd 134
restorearchives 134
resvalidate 135
ruledesc 136
runcertutil 136
runmodeutil 138
runpk12util 138
script 139
searchindex 139
sendlogs 140
tee 140
tempca 140
testbedconnection 141
threaddumps 142
tproc 142
uninstallservice 142
webserver 143
webserver-no-wrapper 143
webserversetup 143
webserversvc 143
websetup 144
whois 145
commands agent tempca 103
commands agentcommand 103
Commonly used elements in Email.vm 
and Informative.vm files 175
Comparing Self-signed and CA-signed certificates 45
Compression and Turbo Modes 82
Configuring
ArcSight Database Monitor 84
ArcSight Manager Logging 24
ArcSight Manager or ArcSight Web as a Service 12
Database Monitor e-mail message recipients 84
SNMP trap sender 85
the check for free space in Oracle tablespaces 84
console command 113
consolesetup command 114
Contents of Email.vm and Informative.vm 176
Customizing the template files 178
D
Database Check Tasks
List 163
database pc command 114
database pm command 115
database xts command 115
databasesetup command 116
dbcheck command 116
dbview-generator command 116
deploylicense command 117
Disabling
Database Checks 162
downloadcertificate command 117
dropSLPartitions command 118
Dynamic Properties 19
E
Editing
Properties 18
Enabling
Compression for ArcSight SmartConnector 
Events 82
Enforcing Good Password Selection 75
Establishing
SSL Client Authentication with 
Login information 57
exceptions command 118
execproc command 119
execprocsvc command 119
expiration, certificate 212
export_system_tables command 120
Exporting
Data 96
Resources to an Archive 183
F
FIPS 140-2 189
flexagentwizard command 120
G
Gathering
logs and diagnostic information 26
groupconflictingassets command 121
H
help for commands 190
How SSL Works 43
How the Email.vm and Informative.vm 
Template Files Work 177
I
idefensesetup command 121
import_system_tables command 122
Importing
CA-signed certificate into Manager’s key store 52
Resources from an Archive 184
v3.x Content to a v4.x ESM System 184
Installing
New License Files Obtained from ArcSight 23
K
key pair
import 208
keytool 42
keytool command 122
Keytoolgui 38
keytoolgui command 123
kickbleep command 123

Index
L
listsubjectdns command 123
Logfu
Example 170
Intervals 173
Menu 172
Typical Data Attributes 172
logfu command 124
M
Manager
Password Configuration 75
manager command 124
managerinventory command 125
manager-no-wrapper command 125
manager-reload-config command 125
managersetup command 126
managerstop command 126
managersvc command 127
managerthreaddump command 127
managerup command 127
Managing
and Changing Properties File Settings 17
Migrating
from Demo to CA-Signed 71
from Demo to Self-Signed 71
from Self-Signed to CA-Signed 72
monitor command 128
Monitoring Available Free Space in Tablespaces 94
N
netio command 128
Network Security Services (NSS) 190
Notification Velocity templates 175
O
Obtaining
CA-signed certificate 51
Oracle
Cold Backup 95
Hot Backup 95
P
package command 129
Partition logs 97
Password
Length 75
Uniqueness 77
portinfo command 130
Properties File Settings
Defaults and User Properties 18
Property File Format 17
Q
querytuner command 131
R
Reconfiguring
ArcSight Manager 74
the ArcSight Console after Installation 74
Reconnecting to the ArcSight Manager 12
Recovering ArcSight Databases 96
Reducing Impact of Anti-Virus Scanning 14
reenableuser command 133
Re-Enabling User Accounts 78
refcheck command 133
regex command 133
Removing the ArcSight Manager Service on Windows 13
replayfilegen command 133
Requiring Mix of Characters in Passwords 76
resetpwd command 134
Resetting
Oracle Password 94
restorearchives command 134
Restricting Passwords Containing User Name 75
Restricting the Number of Failed Log Ins 78
resvalidate command 135
revocation list, certificate 214
ruledesc command 136
runcertutil 190
runcertutil command 136
runmodutil command 138
Running
ArcSight Command Script 101
ArcSight ESM 9
Logfu 168
runpk12util command 138
S
script command 139
searchindex command 139
Securing
ArcSight Manager Properties File 22
Send Logs utility 25
Sending
Events as SNMP Traps 85
logs and diagnostic information to ArcSight 25
sendlogs command 140
Setting
Custom Login Message 11
Database Threshold Notification 94
Password Expiration 77
Speeding up partition compression 96
SSL certificates 44
Starting
and Stopping the ArcSight Manager Service 
on Windows 12
ArcSight Console 10
ArcSight Manager 9
ArcSight SmartConnectors 11
Stopping
ArcSight Manager 12
Syntax for Performing Common Archive Tasks 187
T
tee command 140
tempca 43
tempca command 140
Terminology
SSL Authentication 34
testdbconnection command 141
The #if statement 175

Index
threaddumps command 142
Tools for SSL configuration 38
tproc command 142
Troubleshooting
ArcSight Web 157
Console 153
Database 158
General 147
Logfu 170
Manager 155
Partition Archiver problems. 153
SmartConnectors 153
SSL 158
Types
SSL Certificates 44
U
Understanding
ArcSight Turbo Modes 83
Customization Process 177
Database Checks 161
SSL Authentication 33
uninstallservice command 142
Using
CA-Signed Certificate 51
Certificates to Authenticate Users to ArcSight 73
Demo Certificate 45
Self-Signed Certificate 46
V
Verifying
SSL Certificate Use 72
W
webserver command 143
webserver-no-wrapper command 143
webserversetup command 143
webserversvc command 143
websetup command 144
whois command 145

Esm admin guide_5.2

More Related Content

What's hot (19)

Similar to Esm admin guide_5.2 (20)

More from Protect724v3 (20)

Recently uploaded (20)

Esm admin guide_5.2