ArcSight ESM Installation and Configuration Guide

HPE Security ArcSight ESM
Software Version: 6.9.1c
ESM Installation Guide
March 21, 2016
ESM Installation Guide
Legal Notices
Warranty
The only warranties for Hewlett Packard Enterprise 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.
Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
The network information used in the examples in this document (including IP addresses and hostnames) is for illustration
purposes only.
HPE Security ArcSight products are highly flexible and function as you configure them. The accessibility, integrity, and
confidentiality of your data is your responsibility. Implement a comprehensive security strategy and follow good security
practices.
This document is confidential.
Restricted Rights Legend
Confidential computer software. Valid license from Hewlett Packard Enterprise 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.
Copyright Notice
© Copyright 2016 Hewlett Packard Enterprise Development, LP
Follow this link to see a complete statement of copyrights and acknowledgements:
https://www.protect724.hpe.com/docs/DOC-13026
Support
Contact Information
Phone
A list of phone numbers is available on the HPE Security ArcSight Technical
Support Page: https://softwaresupport.hp.com/documents/10180/14684/espsupport-contact-list
Support Web Site
https://softwaresupport.hp.com
Protect 724 Community
https://www.protect724.hpe.com
HPE ESM 6.9.1c
Page 2 of 94
Contents
Chapter 1: What Is ESM With CORR-Engine Storage?
7
ESM Components
ArcSight Manager
CORR-Engine
ArcSight Command Center
ArcSight Console
SmartConnectors
7
7
8
8
8
8
Deployment Overview
8
ESM Communication Overview
Effect on Communication When Components Fail
Choosing between FIPS Mode or Default Mode
Mode Comparison
Using PKCS #11
Import Control Issues
9
9
10
10
11
11
Directory Structure for ESM Installation
12
References to ARCSIGHT_HOME
12
Chapter 2: Installing on an Appliance
13
Starting the Appliance for the First Time
13
Using the Configuration Wizard
14
Keep these TCP Ports Open
17
Enable Peering
17
Configuring the Appliance for Out-of-Band Remote Access
18
Chapter 3: Installing Software ESM
19
Securing Your ESM System
Protecting ArcSight Manager
Built-In Security
Physical Security for the Hardware
Operating System Security
General Guidelines and Policies about Security
19
19
21
21
22
22
Preparing to Install
System Requirements
23
23
HPE ESM 6.9.1c
Page 3 of 94
ESM Installation Guide
Supported Platforms
Download the Installation Package
Prepare the System
Keep these TCP Ports Open
Install the Time Zone Package
Set Directory Sizes
Sizing Guidelines for CORR-Engine
Export Language UTF File
24
25
25
26
26
27
27
29
Starting the Installer
Running the Installation File
Starting the Configuration Wizard In Console Mode
Using the Configuration Wizard
Handling a Time Zone Update Error
30
30
31
31
34
Uninstalling ESM
35
Chapter 4: Post-Installation Considerations
36
Rerunning The Installer
36
Rerunning the ESM Configuration Wizard
36
Setting Up ESM Reports to Display in a Non-English Environment
On the Manager
On the Console
37
37
37
Improving the Performance of Your Server
38
The Next Steps
39
Chapter 5: Installing ArcSight Console
40
Console Supported Platforms
40
Required Libraries for RHEL and CentOS (64 Bit)
40
Installing the Console
Configuring the ArcSight Console
Importing the Console’s Certificate into the Browser
Character Set Encoding
41
42
46
47
Starting the ArcSight Console
Logging into the Console
47
49
Reconnecting to the ArcSight Manager
49
Reconfiguring the ArcSight Console
49
Uninstalling the ArcSight Console
50
HPE ESM
6.9.1c
Page 4 of 94
ESM Installation Guide
Appendix A: Troubleshooting
51
Location of Log Files for Components
51
If You Encounter an Unsuccessful Installation
53
Customizing the Manager
54
Fatal Error when Running the First Boot Wizard
54
Changing the Hostname of Your Machine
55
Changing the Host Name of the Machine after Running the First Boot Wizard
56
Appendix B: Default Settings For Components
58
General Settings
58
CORR-Engine Settings
58
Manager Settings
58
Appendix C: Using PKCS
60
PKCS#11
60
PKCS#11 Token Support in ESM
60
PKCS#12
61
Setting Up to Use a PKCS#11 Provider
Install the PKCS#11 Provider’s Software
Map a User’s External ID to the Subject CN
Obtain the CAC/90Meter’s Issuers’ Certificate
Extract the Root CA Certificate From the CAC/90Meter Certificate
Import the CAC/90Meter Root CA Certificate into the ArcSight Manager
FIPS Mode - Import into the ArcSight Manager’s nssdb
Default Mode - Import into ArcSight Manager’s Truststore
Select Authentication Option in ArcSight Console Setup
Logging in to the ArcSight Console Using PKCS#11 Token
61
61
62
64
65
67
67
68
69
70
Logging in to an ESM Web UI Using PKCS#11 Token
70
Appendix D: Installing ESM in FIPS Mode
72
What is FIPS?
72
Network Security Services Database (NSS DB)
72
What is Suite B?
73
NSS Tools Used to Configure Components in FIPS Mode
74
TLS Configuration in a Nutshell
74
HPE ESM
6.9.1c
Page 5 of 94
ESM Installation Guide
Server Side Authentication
75
Client Side Authentication
75
Exporting the Manager’s Certificate to Clients
75
Using PKCS #11 Token With a FIPS Mode Setup
76
Installing ArcSight Console in FIPS Mode
76
Types of Key Pairs Used in FIPS Mode
78
Connecting a Default Mode ArcSight Console to a FIPS 140-2 ArcSight Manager
79
Connecting a FIPS ArcSight Console to FIPS Enabled ArcSight Managers
79
Configure Your Browser for FIPS
79
Installing SmartConnectors in FIPS Mode
80
How Do I Know if My Installation is FIPS Enabled?
81
Appendix E: Locales and Encodings
82
Terminology
Character Set
Code Point
Code Set
Encoding
Internationalization
Locale
Localization
Unicode
UTF-8
82
82
82
82
82
82
83
83
83
83
Before You Install a Localized Version of ESM
83
ArcSight Console and Manager
83
ArcSight SmartConnectors
Setting the Encoding for Selected SmartConnectors
Localizing Date Formats
List of Possible Values
agent.parser.locale.name Values
Key-Value Parsers for Localized Devices
84
84
84
84
84
91
Appendix F: Restore Appliance Factory Settings
92
Send Documentation Feedback
94
HPE ESM
6.9.1c
Page 6 of 94
Chapter 1: What Is ESM With CORR-Engine
Storage?
ESM is a Security Information and Event Management (SIEM) solution that collects and analyzes
security data from heterogeneous devices on your network and provides you a central, real-time view of
the security status of all devices of interest to you.
ESM components gather and store events generated by the devices you identify. These events are
filtered and correlated with events from other devices or collection points to discover risks and assess
vulnerabilities.
ESM uses the Correlation Optimized Retention and Retrieval Engine (CORR-Engine) storage, a
proprietary data storage and retrieval framework that receives and processes events at high rates, and
performs high-speed searches. This provides a number of benefits, including increased performance,
ease of management, and use of less disk space.
ESM is available under various licensing models both as software that can be installed on your own
hardware, or as an appliance. This document refers to both types as ESM.
ESM Appliance and ESM Express are different licensing models installed on an appliance.
Software ESM is ESM installed on your own hardware.
ESM Components
The ESM system comprises the following components:
l
l
"ArcSight Manager" below
"CORR-Engine" on the next page
l
"ArcSight Command Center" on the next page
l
"ArcSight Console" on the next page
l
"SmartConnectors" on the next page
ArcSight Manager
The ArcSight Manager is at the center of the ESM system. The Manager is a software component that
functions as a server that receives event data from Connectors and correlates and stores them in the
database. The Manager also provides advanced correlation and reporting capabilities. The Manager and
CORR-Engine are integrated components and get installed on the same machine.
HPE ESM 6.9.1c
Page 7 of 94
ESM Installation Guide
Chapter 1: What Is ESM With CORR-Engine Storage?
CORR-Engine
The CORR-Engine (Correlation Optimized Retention and Retrieval Engine) is a long-term data storage
and retrieval engine that enables the product to receive events at high rates. The Manager and CORREngine are integrated components and get installed on the same machine.
ArcSight Command Center
The ArcSight Command Center is a web-based user interface for ESM. This user interface has the
following characteristics:
l
l
Enables you to perform many of the functions found in the ArcSight Console.
Provides dashboards, a variety of search types, reports, case management, notifications, channels,
and administrative functions for managing content, users, connectors, storage, archives, search
filters, saved searches, and peer configuration.
ArcSight Console
The ArcSight Console provides a user interface for you to perform administrative tasks, such as fine
tuning the ESM content, creating rules, and managing users. The ArcSight Console is installed
separately on client machines.
SmartConnectors
SmartConnectors are software components that forward security events from a wide variety of devices
and security event sources to ESM. SmartConnectors are not bundled with ESM and are installed
separately.
Deployment Overview
The following is an example of how various ESM components can be deployed in a network.
HPE ESM
6.9.1c
Page 8 of 94
ESM Installation Guide
Chapter 1: What Is ESM With CORR-Engine Storage?
ESM Communication Overview
The ArcSight Console, Manager, and SmartConnectors communicate using HTTP (HyperText Transfer
Protocol) over SSL (Secure Sockets Layer), often referred to as HTTPS (HyperText Transfer Protocol
Secure). The HTTPS protocol provides for data encryption, data integrity verification, and
authentication for both server and client.
SSL works over TCP (Transport Control Protocol) connections. The default incoming TCP port on the
Manager is 8443.
The Manager never makes outgoing connections to the Console or SmartConnectors. The Manager
connects to the CORR-Engine through a loop-back interface using a propriety protocol.
Effect on Communication When Components Fail
If any one of the software components is unavailable, it can affect communication between other
components.
If the CORR-Engine is unavailable for any reason, the Manager stops accepting events and caches any
events that were not committed to the CORR-Engine. The SmartConnectors also start caching new
events they receive, so there is no event data loss. The Console gets disconnected.
When the CORR-Engine is filled to capacity, as new events come in, the Manager starts deleting existing
events starting from the oldest event.
If the Manager is unavailable, the SmartConnectors start caching events to prevent event data loss. The
CORR-Engine is idle. The Console is disconnected.
HPE ESM
6.9.1c
Page 9 of 94
ESM Installation Guide
Chapter 1: What Is ESM With CORR-Engine Storage?
If a SmartConnector fails, whether event data loss will occur or not depends on the SmartConnector
type. SmartConnectors that listen for events from devices such as the SNMP SmartConnectors will stop
accepting events. However, a SmartConnector that polls a device, such as the NT Collector
SmartConnector, may be able to collect events that were generated while the SmartConnector was
down, after the SmartConnector comes back up.
Choosing between FIPS Mode or Default Mode
ESM supports the Federal Information Processing Standard (FIPS) 140-2 and Suite B. FIPS is a
standard published by the National Institute of Standards and Technology (NIST) and is used to
accredit cryptographic modules in software components. The US Federal government requires that all
IT products dealing with Sensitive, but Unclassified (SBU) information should meet FIPS 140-2
standards.
Depending on your requirements, you can choose to install the ESM components in either of these
modes:
l
Default mode (standard cryptography)
l
FIPS 140-2 mode
l
FIPS with Suite B mode
Mode Comparison
The following table outlines some of the basic differences between the three modes that ESM supports:
Mode
Default
Mode
Use of
SSL/TLS Default Cipher Suites
Keystore/
Truststore
SSL
Keypair and Certificates stored in
Keystore and cacerts, and
Truststore in JKS format
l
l
l
FIPS
140-2
Mode
TLS
FIPS
with
Suite B
Mode
TLS
HPE ESM
l
l
l
TLS_RSA_WITH_AES_128_CBC_
SHA
SSL_RSA_WITH_3DES_EDE_CBC_
SHA
More...
TLS_RSA_WITH_AES_128_CBC_
SHA
Keypair and Certificates stored in
NSSDB
SSL_RSA_WITH_3DES_EDE_CBC_
SHA
TLS_ECDHE_ECDSA_WITH_AES_
128_CBC_SHA
Keypair and Certificates stored in
NSSDB
Suite B 128 bits security level,
providing protection from
6.9.1c
Page 10 of 94
ESM Installation Guide
Chapter 1: What Is ESM With CORR-Engine Storage?
Mode
Use of
SSL/TLS Default Cipher Suites
Keystore/
Truststore
unclassified up to secret information
l
TLS_ECDHE_ECDSA_WITH_AES_
256_CBC_SHA
Suite B 192 bits security level,
providing protection from
unclassified up to top secret
information
Using PKCS #11
ESM supports the use of a PKCS#11 token such as 90Meter or the Common Access Card (CAC) (which
is used for identity verification and access control) to log into the Console. PKCS#11 is Public-Key
Cryptography Standard (PKCS), published by RSA Laboratories which describes it as “a technologyindependent programming interface, called Cryptoki, for cryptographic devices such as smart cards and
PCMCIA cards.”
PKCS#11 authentication is not supported with Radius, LDAP, and Active Directory authentication
methods.
Import Control Issues
If you are a customer in the United States, you can skip reading this section. If you are a customer
outside of the United States, you need to be aware of your country's restrictions on allowed
cryptographic strengths. The embedded JRE in ESM components, ship with the Java Cryptography
Extension (JCE) Unlimited Strength Jurisdiction Policy Files and they are enabled by default. These files
are:
l
jre\lib\security\local_policy.jar
l
jre\lib\security\US_export_policy.jar
This is appropriate for most countries. However, if your government mandates restrictions, back up the
above two *.jar files and use the restricted version files instead. They are available at:
jre\lib\security\local_policy.jar.original
jre\lib\security\US_export_policy.jar.original
Rename *.jar.original to *.jar.
The only impact of using the restricted version files would be that you cannot import unrestrictedstrength key pairs. Also, you cannot save the keystore if you use passwords that are longer than four
characters. No other ESM functionality is impacted.
HPE ESM
6.9.1c
Page 11 of 94
ESM Installation Guide
Chapter 1: What Is ESM With CORR-Engine Storage?
Directory Structure for ESM Installation
By default, ESM is installed in a directory tree under a single root directory. Other third-party software is
not necessarily installed under this directory, however. The path to this root directory is called
/opt/arcsight.
The directory structure below /opt/arcsight is also standardized across components and platforms.
The following table lists a few of the commonly used directories for the Manager.
Port
Directory
ESM
/opt/arcsight/manager/bin
Properties files
/opt/arcsight/manager/config
Log files
/opt/arcsight/manager/logs
References to ARCSIGHT_HOME
<ARCSIGHT_HOME> in the paths represents:
l
/opt/arcsight/manager for the ArcSight Manager
l
Whatever path you specified when you installed the ArcSight Console
l
Whatever path you specified when you installed an ArcSight SmartConnector.
HPE ESM
6.9.1c
Page 12 of 94
ESM Installation Guide
Chapter 2: Installing on an Appliance
Chapter 2: Installing on an Appliance
This section applies to users who have purchased ESM on an appliance from HPE. For instructions
about how to install ESM on your own hardware, go to the chapter on Installing Software ESM.
Read the Release Notes before you begin.
There are no software preparations necessary on the appliance and no opportunity to make any
preparatory adjustments before the First Boot Wizard starts.
Starting the Appliance for the First Time
When you power on the appliance, the Operating System First Boot Wizard (FBW) starts automatically.
This is a command line interface. The FBW asks you to supply the following information, one entry at a
time (the FBW indicates which values are optional):
1. At appliance login, log in as user root, using the password arcsight.
2. Set a new password for user root.
3. Set a new password for user arcsight.
4. Set the appliance hostname.
5. Specify the IP address (IPv4 only). You might need to get this and the following values from your
system administrator.
6. Specify the netmask.
7. Specify the default gateway.
8. Specify the primary DNS IP Address (IPv4 only)
9. Specify the secondary DNS IP Address (IPv4 only, and this is optional)
10. Specify the DNS Search Domains.
11. Specify the time zone. You can start to type and press Tab and the system will attempt to auto-fill
the time zone. For example you can type A, Tab and it fills in "America_". Press the Tab key twice for
a list of timezone entries that starts with "America_".
12. Enter the Date.
The date and time are optional. If you specify an NTP server, it overrides these date/time values. If
there is no NTP server, these date/time values reset the appliance system clock and if you leave
them blank, the system clock determines the date time.
13. Enter the Time.
14. Specify the NTP servers. List one NTP server per line. You can use IP addresses or host names.
Using an NTP server is recommended.
HPE ESM
6.9.1c
Page 13 of 94
ESM Installation Guide
Chapter 2: Installing on an Appliance
When you are done, it provides a list of what you have specified, for you to review. If you say No, it starts
over.
If you accept the specifications then press Enter to end the installation session and start the
Configuration Wizard.
Note: Although the installer session provides a command for starting the Configuration Wizard
manually, do not use it. The Configuration Wizard starts automatically when you press Enter to
end the installer session.
License file: Once the IP address is defined you can log in to the appliance from the machine where you
downloaded the license file and copy it to the appliance. The Configuration Wizard segment, which is
next, asks you to specify the location of the license file on the appliance.
Using the Configuration Wizard
When installing on an appliance, the configuration wizard starts automatically. (You do not need to
manually enter any command for that to happen.) When installing software ESM in GUI mode, the
Configuration Wizard starts automatically. Otherwise see the previous topic on how to start the
configuration wizard in console mode.
1. Read the Welcome message. If the license file is accessible, type yes to continue.
2. Under Language Options, select the language for interface displays. Press Enter to continue.
3. Under CORR-Engine Password, press Enter to continue with obfuscated passwords or type no
and Enter to allow them to show on screen.
4. Under CORR-Engine Password, set a password for the CORR-Engine and reenter it for the
Password confirmation. Press Enter. For information on password restrictions, see the
ESM Administrator's Guide section “Managing Password Configuration” in the chapter
“Configuration.”
5. Under CORR-Engine Configuration, enter the CORR-Engine storage allocation information and
press Enter.
System Storage Size - the size of the storage space set aside to store resources
Event Storage Size - the size of the storage space set aside to store events
Online Event Archive Size - the maximum number of gigabytes of disk space for event archives.
This only applies to default online event archive.
Retention Period - the amount of time that you want to retain the events before they are purged
from the system
6. Under Notification Emails, specify the following email addresses:
Error Notification Recipient: Specify one email address for the email account to receive email
notifications if the Manager goes down or encounters some other problem. If you need to specify
HPE ESM
6.9.1c
Page 14 of 94
ESM Installation Guide
Chapter 2: Installing on an Appliance
more email addresses, the Manager Configuration Wizard allows that, as described in the "Running
the Manager Configuration Wizard" section of the ESM Administrator's Guide.
From email address: The email address used for the notifications sender.
If the values are correct, type yes and Enter to continue. Emails are sent when the system detects
the following occurrences:
l
The subsystem status is changed. The email shows the change and who did it.
l
The report has been successfully archived.
l
The account password has been reset.
l
The Archive report generation fails.
l
There is too many notifications received by a destination.
The event archive location has reached the cap space. It will ask you to free up some space by
moving the event archives to some other place.
l
l
The user elects to email the ArcSight Console settings.
l
The user sends partition archival command.
l
An archive fails because there is not enough space.
l
The Connection to the database failed.
7. For the License File, enter the path and file name of the license file you downloaded and press
Enter.
8. Under Select the Product Mode, select whether you want to install in default mode or FIPS mode.
Press Enter to continue.
Caution:
l
l
l
l
If you choose to install the product in FIPS mode, be sure to install the Console in FIPS
mode too. Refer to "Installing ArcSight Console in FIPS Mode" on page 76 for instructions
on installing the Console in FIPS mode.
Once you have configured the software in FIPS mode, you will not be able to convert it to
default mode without reinstalling it.
Converting from default mode installation to FIPS mode is supported. If you need to do so
at any time, refer to the Administrator’s Guide for instructions.
By default, ESM uses a self-signed certificate. If you would like to use a CA-signed
HPE ESM
6.9.1c
Page 15 of 94
ESM Installation Guide
Chapter 2: Installing on an Appliance
certificate, you will have to import the CA-signed certificate manually after the
configuration wizard completes successfully. Refer to the Administrator’s Guide for ESM for
details on using a CA-signed certificate.
9. If you selected FIPS mode, confirm your selection. if not, skip to the Manager Information step.
10. If you selected FIPS mode on the Select the Cipher Suite Options panel. select the cipher suite.
Suite B defines two security levels of 128 and 192 bits. The two security levels are based on the
Advanced Encryption Standard (AES) key size that is used instead of the overall security provided
by Suite B. At the 128-bit security level, the 128 bit AES key size is used. However, at the 192-bit
security level, a 256 bit AES key size is used. Although a larger key size means more security, it also
means computational cost in time and resource (CPU) consumption. In most scenarios, the 128-bit
key size is sufficient.
11. Under Manager Information, enter the Manager’s hostname or IP address, set the user ID and
password for the admin user, and press Enter.
Caution: Manager host name is the local host name, IP address, or fully-qualified domain name
of the machine where the Manager is installed. This name is what all clients (for example,
ArcSight Console) specify to connect to the Manager. Using a host name and especially a fullyqualified domain name instead of an IP address is recommended for flexibility.
If you do not want the hostname on your DNS server, add a static host entry to the
/etc/hosts file to resolve the host name locally.
The Manager hostname is used to generate a self-signed certificate. The Common Name (CN)
in the certificate is the Manager host name that you specify in this screen.
Although the Manager uses a self-signed certificate by default, you can switch to using a CAsigned certificate if needed. You can do this after installation. Refer to the Administrator’s
Guide for instructions.
12. Under Packages, ESM Express does not license these packages. Press Enter to continue.
Otherwise, select the optional packages that you are licensed to use. In addition to these optional
packages, there are default standard content packages that are installed automatically on the
ArcSight Manager. These default packages provide essential system health and status operations,
and you can use them immediately to monitor and protect your network.
For more information about packages, see the ArcSight Administration and ArcSight System
Standard Content Guide.
13. Under About to Configure ESM.
Caution: Once you type yes and press Enter, the product is installed as specified.
14. When the configuration says Configuration Completed Successfully, type Yes and then Enter to
exit.
15. Important! This step is required in order to start the services. Log in as user root and run the
HPE ESM
6.9.1c
Page 16 of 94
ESM Installation Guide
Chapter 2: Installing on an Appliance
following script to set up the required services:
/opt/arcsight/manager/bin/setup_services.sh
After you have completed the installation, check the location and size of your storage volumes and
make any necessary changes. You can do this in the ArcSight Command Center. Refer to the
ArcSight Command Center User's Guide, the "Administration" chapter under "Storage and Archive”
section for details regarding your storage volumes.
You can rerun the wizard manually only if you exit it at any point before you reach the first
configuration screen called “About to Configure ESM v6.9.1c”. See "Rerunning the ESM
Configuration Wizard" on page 36 for details.
Keep these TCP Ports Open
On an appliance, these ports are already open. Make sure you do not use them.
Ports for external incoming connections:
8443/tcp
22/tcp (ssh)
TCP ports used internally for inter-component communication:
1976, 28001, 2812, 3306, 5555, 6005, 6009, 7777, 7778, 7779, 7780, 8005, 8009, 8080, 8088, 8089,
8666, 8766, 8808, 8880, 8888, 8889, 9095, 9090, 9123, 9124, 9999,45450
Enable Peering
This topic is for appliance installation using an ESM license that includes peering, By default appliances
ship with port 9000 disabled. Peering requires this port. For peering to work on an appliance, enable
port 9000 using the following commands:
[root@rhel7 ~]# firewall-cmd --zone=public --add-port=9000/tcp --permanent
[root@rhel7 ~]# firewall-cmd --reload
Use this command to check that port 9000 is enabled:
[root@rhel7 ~]# iptables-save | grep 9000
You should get response similar to this:
-A IN_public_allow -p tcp -m tcp --dport 9000 -m conntrack --ctstate NEW -j
ACCEPT
HPE ESM
6.9.1c
Page 17 of 94
ESM Installation Guide
Chapter 2: Installing on an Appliance
Configuring the Appliance for Out-of-Band Remote
Access
Configure the appliance for out-of-band remote access so that Customer Support can access and
troubleshoot the appliance if it becomes unresponsive. All appliance models are equipped with the HP
Integrated Lights-Out (iLO) advanced remote management card. Visit http://www.hp.com/go/iLO for
detailed information and documentation.
HPE ESM
6.9.1c
Page 18 of 94
Chapter 3: Installing Software ESM
We recommend that you read the ESM Release Notes before you begin installing ESM.
If you are installing ESM Express, which is on an appliance provided by HP, refer to the Configuration
Guide for ESM Express, which is available for download on Protect 7/24
(https://www.protect724.hpe.com).
If you are going to use the ESM High Availability Module with ESM and this is a new ESM installation,
install the HA Module first. Refer to the ESM High Availability Module Guide for instructions.
ESM is sensitive to the operating system and version. To ensure proper operation, this installer only
allows installation on the specific operating systems and versions listed in the HP ArcSight ESM Support
Matrix, which is available for download on Protect 7/24 (https://www.protect724.hpe.com).
Securing Your ESM System
Use the information in the following sections to protect your ArcSight components.
Protecting ArcSight Manager
Do not use demo SSL certificates in production. Make sure when switching that you remove the demo
CA from cacerts on all SmartConnectors and ArcSight Consoles.
Closely control access to files, using the principle of least privilege, which states that a user should be
given only those privileges that the user needs to complete his or her tasks. The following files are
particularly sensitive:
Note: <ARCSIGHT_HOME> is the root directory for a component. For example for the Manager
component, <ARCSIGHT_HOME> is: /opt/arcsight/manager.
l
l
l
l
l
<ARCSIGHT_HOME>\config\jetty\keystore (to prevent the ArcSight Manager
private key from being stolen)
<ARCSIGHT_HOME>\config\jetty\truststore (w/ SSL Client authentication only,
to prevent injection of new trusted CAs)
<ARCSIGHT_HOME>\config\server.properties (has keystore and database
passwords)
<ARCSIGHT_HOME>\config\jaas.config (w/ RADIUS or SecurID enabled only, has
shared node secret)
<ARCSIGHT_HOME>\config\client.properties (w/ SSL Client authentication
HPE ESM 6.9.1c
Page 19 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
only, has keystore passwords)
l
<ARCSIGHT_HOME>\reports\sree.properties (to protect the report license)
l
<ARCSIGHT_HOME>\reports\archive\*
l
(to prevent archived reports from being stolen)
<ARCSIGHT_HOME>\jre\lib\security\cacerts (to prevent injection of new
trusted CAs)
l
<ARCSIGHT_HOME>\lib\* (to prevent injection of malicious code)
l
<ARCSIGHT_HOME>\rules\classes\* (to prevent code injection)
If you are installing ESM on your own hardware (as opposed to an appliance), use a host-based firewall.
On the ArcSight Manager, block everything except for the following ports. Make sure you restrict the
remote IP addresses that may connect to those that actually need to talk.
Port
Flow
Description
22/TCP
Inbound
SSH log in (Unix only)
53/UDP
Inbound/Outbound
DNS requests and responses
8443/TCP
Inbound
SmartConnectors and Consoles
25/TCP
Outbound
SMTP to mail server
110/TCP
Outbound
POP3 to mail server, if applicable
143/TCP
Outbound
IMAP to mail server, if applicable
1645/UDP
Inbound/Outbound
RADIUS, if applicable
1812/UDP
Inbound/Outbound
RADIUS, if applicable
389/TCP
Outbound
LDAP to LDAP server, if applicable
636/TCP
Outbound
LDAP over SSL to LDAP server, if applicable
As another layer of defense (or if no host-based firewall is available), you can also restrict which
connections are accepted by the ArcSight Manager using the following properties in the
server.properties file:
xmlrpc.accept.ips=
agents.accept.ips=
Each of these properties takes a list of IP addresses or subnet specifications, separated by commas or
spaces. Once specified, only connections originating from those addresses are accepted.
l
The xmlrpc.accept.ips property restricts access for ArcSight Consoles.
HPE ESM
6.9.1c
Page 20 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
l
The agents.accept.ips property restricts access for SmartConnectors. For registration, the
SmartConnectors need to be in xmlrpc.accept.ips as well, so that they can be registered. (Being
"registered" does not mean you can then remove them.)
The format for specifying subnets is quite flexible, as shown in the following example:
xmlrpc.accept.ips=192.0.2.0 192.0.2.5
agents.accept.ips=10.*.*.*,192.0.2.0/255.255.0.0
Built-In Security
ESM user accounts have user types that control the functions which users can access in the ArcSight
Manager. The "Normal User" type has the most privileges. Where possible, use more restrictive types,
such as "Manager SmartConnector," "Management Tool," or "Archive Utility" for non-human user
accounts. This is particularly important when user passwords must be stored in scripts for unattended
execution.
Apply the principle of least privilege when creating user accounts in ESM and when granting access to
resources or events. Users should not have more privileges than their tasks require.
By default, the minimum length for passwords is six characters and the maximum length is 20
characters. For information on password restrictions see the Administrator's Guide, chapter 2.
"Configuration," "Managing Password Configuration," "Password Character Sets."
Physical Security for the Hardware
In addition to establishing security policies for passwords, keystores, and other software facilities, it is
important to provide physical security for the hardware used by the ESM system. Physical hardware
includes computers running ArcSight Console, and SmartConnector software, as well as the network
which connects them.
Physical access to computers running ArcSight software must be restricted.
l
Use the locking mechanisms provided by most rack-mount cases to prevent malicious/accidental
tampering with the machine
l
Use locks on disk drive enclosures
l
Use redundant power and uninterruptible power supplies (UPS)
l
Protect the BIOS (x86 systems only) or firmware:
l Disable all CD-ROM drives for booting so that the system can only be booted from the hard disk
l
Disable COM, parallel, and USB ports so that they cannot be used to extract data
l
Disable power management
HPE ESM
6.9.1c
Page 21 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
Operating System Security
l
l
l
l
l
l
l
l
l
On Linux, set up a boot loader password to prevent unauthorized people from booting into single
user mode (see the LILO or GRUB documentation for details).
On Linux, disable reboot by Ctrl-Alt-Del in /etc/inittab. Comment out the line that refers to
“ctrlaltdel.”
Set up a screen saver that prompts for a password with a moderately short delay (such as five
minutes).
Disable power management in the OS.
When installing the OS, select packages individually. Only install what you know will be needed. You
can always install missing packages as you encounter them.
Run automated update tools to obtain all security fixes. Use up2date on Red Hat Linux (may require
Red Hat Network subscription).
Uninstall (or at least turn off) all services that you do not need. In particular: finger, r-services, telnet,
ftp, httpd, linuxconf (on Linux), Remote Administration Services and IIS Services on Windows.
On Unix machines, disallow remote root logins (for OpenSSH, this can be done using the
PermitRootLogin no directive in /etc/ssh/sshd_config). This will force remote users to log in
as a non-root user and su to root, thus requiring knowledge of two passwords to gain root access to
the system. Restrict access to su, using a “wheel group” pluggable authentication module (PAM) so
that only one non-root user on the machine can su to root. Make that user different from the
arcsight user. That way, even if the root password is known and an attacker gains access through
ESM in some way, they won't be able to log in as root.
Rename the Administrator/root account to make brute force attacks harder.
General Guidelines and Policies about Security
Educate system users about “social engineering” tricks used to discover user account information. No
employee of HPE will ever request a user’s password. When HPE representatives are on site, the
administrator of the system will be asked to enter the password and, if needed, to temporarily change
the password for the HPE team to work effectively.
Educate users to use secure means of communication—such as SSL to upload or PGP for e-mail—when
transferring configuration information or log files to HPE.
Set up a login banner stating the legal policies for use of the system and the consequences of misuse.
(Instructions for creating a login banner vary by platform.) ArcSight Consoles can also display a custom
login banner. Contact the Customer Support using the HP SSO site for more information.
HPE ESM
6.9.1c
Page 22 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
Choose secure passwords. (No password used in two places, seemingly random character sequences,
eight characters or longer, containing numbers and special (non-letter) characters). For information on
password restrictions see the Administrator's Guide, chapter 2. "Configuration," "Managing Password
Configuration."
Passwords are used in the following places—if any one is breached, the system is compromised:
l
All database accounts (arcsight)
l
The “arcsight” user and root user on the system that runs the ArcSight Manager
l
All users created in ESM
l
The SSL keystores
l
The boot loader (Linux)
l
The BIOS (x86 systems only)
l
The RADIUS node secret
l
The LDAP password for ArcSight Manager (w/ basic authentication only), where applicable
l
The Active Directory domain user password for ArcSight Manager where applicable
Consider purchasing and using a PKI solution to enable SSL client authentication on Consoles and
SmartConnectors.
Consider purchasing and using a two-factor authentication solution such as RSA SecurID.
Make sure that all the servers with which ESM interacts (DNS, Mail, RADIUS, etc.) are hardened
equivalently.
Use a firewall and intrusion detection systems to secure the network that the ArcSight Manager CORR_
Engine use.
Preparing to Install
Before you run the Software ESM installation file, you must prepare your system.
System Requirements
The hardware requirements for ESM 6.9.1c are as follows:
Minimum
Mid-Range
High Performance
Processors
8 cores (16 preferred)
32 cores
40 cores
Memory
48 GB RAM (64 preferred)
192 GB RAM
512 GB RAM
HPE ESM
6.9.1c
Page 23 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
Hard Disk
Minimum
Mid-Range
High Performance
Six 600 GB disks (1.5 TB)
(RAID 10)
20 1 TB disks (10 TB)
(RAID 10)
12 TB
(RAID 10)
15,000 RPM
10,000 RPM
Solid state
Caution: The "Minimum" values apply to systems running base system content at low EPS (typical
in lab environments). It should not be used for systems running high number of customer-created
resources, or for systems that need to handle high event rates. Use the "Mid Range" or "High
Performance" specifications for production environments that handle a sizable EPS load with
additional content and user activity.
Using Pattern Discovery or large numbers of Assets and Actors puts additional load on the system
that can reduce the search and event processing performance. For further assistance in sizing your
ESM installation, contact your HP ArcSight Sales or Field Representative.
If you anticipate that you will have large lists (a list with roughly five million entries) or 500,000
Actors, ensure that your system meets the Mid-Range requirements or better.
Monitor Requirement:
For displaying the ArcSight Command Center, use a monitor that has a width of at least 1450 pixels.
This is the minimum width needed to display all of the top-menu items without cutting any of them off.
This minimum width also applies on a larger monitor when reducing the size of the browser window.
Supported Platforms
ESM 6.9.1c is supported on 64-bit Red Hat Enterprise Linux and CentOS. See the HP ArcSight ESM
Support Matrix for the supported version numbers. Install them using at least the "Web Server" option
with added "Compatibility Libraries" and "Development Tools" at the time of installation. ESM is sensitive
to the operating system and version. To ensure proper operation, this installer only allows installation
on the specific operating systems and versions listed in the HP ArcSight ESM Support Matrix. This
document is available for download on Protect 7/24
(https://www.protect724.hpe.com).
Note:
l
l
To install the product in GUI mode, install the X Windows system package. X Window is entirely
optional. If you use it, use xorg-x11-server-utils-7.5-13.el6.x86_64 or a later version
for RHEL or CentOS. If you do not use X Window, you can install ESM in console mode.
The XFS and EXT4 file system formats are supported during installation.
HPE ESM
6.9.1c
Page 24 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
l
l
l
ESM configures itself to the file system upon which it is first installed; you therefore cannot
change the file system type after installation, even during an upgrade.
The atd service must be running all the time. At the end of the ESM installation, if the service
is not already running, it starts when you run the setup_services.sh command.
When you install RHEL or CentOS, the installation offers you certain options. Be sure to choose
the Web Server, Compatibility Libraries, and the Development Tools options.
Download the Installation Package
The ESM6.9.1c installation package is available for download from HP at
https://softwaresupport.hp.com/. Download the ArcSightESMSuite-6.9.1.xxxx.0.tar file and
copy it on to the system where you will be installing ESM. The xxxxx in the file name stands for the build
number.
HPE provides a digital public key to enable you to verify that the signed software you received is indeed
from HPE and has not been manipulated in any way by a third party.
Visit the following site for information and instructions:
https://h20392.www2.hpe.com/portal/swdepot/displayProductInfo.do?productNumber=HPLinuxCod
eSigning
After you download the .tar file from the HP Software Depot, initiate license procurement by following
the instructions in the Electronic Delivery Receipt you receive from HP in an email after placing the
order.
Note: You do not need to unzip the license zip file. ESM recognizes the license file in the zipped
state.
If you plan to install the Risk Insight software with ESM, create an new partition with at least 25 GB for it
in addition to the space allocation you make for ESM.
Consult the ArcSight Risk Insight Deployment Guide for details.
Prepare the System
1. Log in as user root.
2. Run the following command to untar the file:
tar xvf ArcSightESMSuite-6.9.1.xxxx.0.tar
When you untar the ArcSightESMSuite-6.9.1.xxxx.0.tar file, It places the prepare_
system.sh script in a sub-directory called Tools in the location where you untar the file.
3. Run prepare_system.sh
HPE ESM
6.9.1c
Page 25 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
4. Change ownership of all the files and folders that were extracted from the tar file to be owned by
user arcsight.
5. Reboot the system.
6. Verify that it ran correctly. Log in as user arcsight and run:
ulimit -a
Check for the following two lines:
open files 65536
max user processes 10240
Keep these TCP Ports Open
For Software ESM, before installation, open the following ports on your system, if not already open,
and ensure that no other process is using them.
Ports for external incoming connections:
8443/tcp
9000/tcp
694/udp (for HA)
7789/tcp (for HA)
22/tcp (ssh)
TCP ports used internally for inter-component communication:
1976, 28001, 2812, 3306, 5555, 6005, 6009, 7777, 7778, 7779, 7780, 8005, 8009, 8080, 8088, 8089,
8666, 8766, 8808, 8880, 8888, 8889, 9000, 9095, 9090, 9123, 9124, 9999, 45450
Install the Time Zone Package
ESM uses the time zone update package in order to automatically handle changes in time zone or
changes between standard and daylight savings time. During installation, ESM checks to see if the
appropriate operating system time zone package is installed. If it is not, you have the option of exiting
the installer to install the latest operating system timezone update or continuing the ESM installation
and skipping the timezone update for ESM components. We recommend installing the time zone
update package.
For RHEL 7.1 and CentOS 7.1 use tzdata-2015b-1.el7.noarch.rpm.
Earlier versions are acceptable as far back as 2014f.
On RHEL or CentOS 7.1
To install it on RHEL or CentOS 7.1, use these commands:
rpm -Uvh <package>
timedatectl set-timezone <time_zone>
HPE ESM
6.9.1c
Page 26 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
On RHEL or CentOS 6.7
To install it on RHEL or CentOS 6.7, use the command:
rpm -Uvh <package>
Check to make sure that the /etc/localtime link is pointing to a valid time zone by running the
following command:
ls -altrh /etc/localtime
You should get a response similar to this (below), where <ZONE> is your time zone such as
America/Los_Angeles.
lrwxrwxrwx. 1 root root 39 Nov 27 08:28 /etc/localtime ->
/usr/share/zoneinfo/<ZONE>
Verify that /etc/localtime is pointing to the correct time zone or use the date command.
If you do not install at this time...
If you quit the installation to fix these, you can simply run the installation again.
If you complete the installation without fixing these, you can still set up the time zone package after
completing the installation. Use the following procedure after ensuring that you have downloaded and
installed the correct package and the link is set correctly. (Remember, this is for after the installation is
complete.):
1. As user arcsight, shut down all arcsight services. (This is important.) Run
/etc/init.d/arcsight_services tryForceStop all
2. As user root, run the following command (this is one line):
/opt/arcsight/manager/bin/arcsight tzupdater /opt/arcsight /opt/arcs
ight/manager/lib/jre-tools/tzupdater
3. Monitor for any failure.
4. Restart all arcsight services.
Set Directory Sizes
Make sure that the partition in which your /tmp directory resides has at least 5 GB of space.
Make sure that the partition in which your /opt/arcsight directory resides has at least 50 GB of
space.
Sizing Guidelines for CORR-Engine
When installing ESM 6.9.1c, the default CORR-Engine storage sizes are automatically calculated based
on your hardware according to the default values in the table below. These are the recommended sizing
HPE ESM
6.9.1c
Page 27 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
guidelines. You can change any of the default storage sizes in the “CORR-Engine Configuration” panel
of the wizard, but when doing so, be sure that you take the minimum and maximum values allowed into
consideration.
System Storage - non-event storage, for example, resources, trends, and lists
Event Storage - storage for events
Online Event Archive - archive of online events
Recommended
Minimum Maximum
System
Storage
Size
The default is about one sixth of Usable Space, from at least 3
GB up to a maximum of 1,500 GB. During installation, it is
recommended that you accept the default.
3 GB
1,500 GB
Event
Storage
Size
Specify about two thirds of the Usable Space shown during
installation.
10 GB
12 TB
Event
Archive
Size
You may specify the remaining space after the System and
Event storage have been allocated.
1 GB
No limit
The system reserves 10 percent of the /opt/arcsight partition for its own use.
During installation, the system will show the size of the /opt/arcsight partition as "Available Space," and
the size of that partition less 10 percent reserved space as "usable Space." The maximum event storage
volume size is calculated by the system using this formula:
Maximum Event Storage = /opt/arcsight partition x 0.9 - system storage - event archives.
After installation, the allocated event storage space consists of a default storage group and an internal
storage group whose size is initially set by the installer. These storage groups do not fill the maximum
size of the event storage volume. You may expand the size of these storage groups or add up to four of
your own storage groups until the allocated size of the event storage reaches the maximum size of the
event storage volume. Use the ArcSight Command Center user interface to add or change the size of
storage groups.
In the ArcSight Command Center, select Administration > Storage and Archive to see and change
the storage allocations. Refer to the ArcSight Command Center User's Guide for details.
The following diagrams clarify the various terms used in the configuration wizard and in the ArcSight
Command Center user interface:
HPE ESM
6.9.1c
Page 28 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
Export Language UTF File
Run the following command:
export LC_ALL=[language].UTF-8
...where [language] is one of these:
en_US (English)
zh_CN (Simplified Chinese)
zh_TW (Traditional Chinese)
ja_JP (Japanese)
fr_FR (French)
ko_KR (Korean)
ru_RU (Russian)
For example: export LC_ALL=en_US.UTF-8
HPE ESM
6.9.1c
Page 29 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
.
Starting the Installer
Start the installation while logged in as user arcsight.
If not already granted, give the ArcSightESMSuite.bin file the execute permission. To do so,
enter:
chmod +x ArcSightESMSuite.bin
Run the installation file as follows:
./ArcSightESMSuite.bin -i console
(or ./ArcSightESMSuite.bin, for GUI mode, if you are using X Window.)
The installation begins.
Note:
l
l
l
To run in GUI mode, X Window must be running. If it is not, the installer automatically runs in
Console mode. GUI mode is entirely optional.
To run in Console mode, make sure X Windows is not running. GUI mode requests the same
information as console mode and is not documented separately.
The log files for this installation appear in the /home/arcsight directory.
The next topic picks up after the installer has started.
Running the Installation File
The following steps describe the ESM installer.
1. Read the Introduction message and press Enter.
2. On the License Agreement panel, press Enter to page through the agreement. In GUI mode, the “I
accept the terms of the License Agreement” radio button is disabled until you scroll to the bottom
of the agreement text. If you accept the License Agreement, type y and press Enter.
3. Read the Special Notice and press Enter.
4. Under Choose Link Location, type the number for the location where you would like the installer
to place the links for this installation and press Enter.
5. Review the Pre-Installation Summary. Press Enter to continue.
Under Installing a progress bar appears.
The Suite Installer installs each component.
HPE ESM
6.9.1c
Page 30 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
l
l
In Console mode, after the components are installed it says Installation Complete. Press Enter to
exit the installer. Go to the next topic, "Starting the Configuration Wizard In Console Mode" below.
In GUI mode, after the components are installed, the Configuration Wizard GUI opens automatically.
Go to "Using the Configuration Wizard" below for details on configuring ESM.
Note: In GUI mode, if you get a dialog box reporting an error or problem and the action button
says Quit, use the Quit button. If you use the X in the upper right corner of the dialog, the
process does not quit, but cannot complete successfully with the reported error.
Starting the Configuration Wizard In Console Mode
If you are installing software ESM in GUI mode or installing ESM Express, the configuration wizard
starts automatically and you can skip this step during initial installation.
When installing software ESM in console mode (from the command line), the installation stops at this
point when the Suite Installer is done, but it does not automatically continue with the configuration
wizard. You start the configuration wizard manually by issuing the following command:
/opt/arcsight/manager/bin/arcsight firstbootsetup -boxster -soft -i console
Using the Configuration Wizard
When installing on an appliance, the configuration wizard starts automatically. (You do not need to
manually enter any command for that to happen.) When installing software ESM in GUI mode, the
Configuration Wizard starts automatically. Otherwise see the previous topic on how to start the
configuration wizard in console mode.
1. Read the Welcome message. If the license file is accessible, type yes to continue.
2. Under Language Options, select the language for interface displays. Press Enter to continue.
3. Under CORR-Engine Password, press Enter to continue with obfuscated passwords or type no
and Enter to allow them to show on screen.
4. Under CORR-Engine Password, set a password for the CORR-Engine and reenter it for the
Password confirmation. Press Enter. For information on password restrictions, see the
ESM Administrator's Guide section “Managing Password Configuration” in the chapter
“Configuration.”
5. Under CORR-Engine Configuration, enter the CORR-Engine storage allocation information and
press Enter.
System Storage Size - the size of the storage space set aside to store resources
Event Storage Size - the size of the storage space set aside to store events
Online Event Archive Size - the maximum number of gigabytes of disk space for event archives.
This only applies to default online event archive.
HPE ESM
6.9.1c
Page 31 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
Retention Period - the amount of time that you want to retain the events before they are purged
from the system
6. Under Notification Emails, specify the following email addresses:
Error Notification Recipient: Specify one email address for the email account to receive email
notifications if the Manager goes down or encounters some other problem. If you need to specify
more email addresses, the Manager Configuration Wizard allows that, as described in the "Running
the Manager Configuration Wizard" section of the ESM Administrator's Guide.
From email address: The email address used for the notifications sender.
If the values are correct, type yes and Enter to continue. Emails are sent when the system detects
the following occurrences:
l
The subsystem status is changed. The email shows the change and who did it.
l
The report has been successfully archived.
l
The account password has been reset.
l
The Archive report generation fails.
l
There is too many notifications received by a destination.
The event archive location has reached the cap space. It will ask you to free up some space by
moving the event archives to some other place.
l
l
The user elects to email the ArcSight Console settings.
l
The user sends partition archival command.
l
An archive fails because there is not enough space.
l
The Connection to the database failed.
7. For the License File, enter the path and file name of the license file you downloaded and press
Enter.
8. Under Select the Product Mode, select whether you want to install in default mode or FIPS mode.
Press Enter to continue.
Caution:
l
l
If you choose to install the product in FIPS mode, be sure to install the Console in FIPS
mode too. Refer to "Installing ArcSight Console in FIPS Mode" on page 76 for instructions
on installing the Console in FIPS mode.
Once you have configured the software in FIPS mode, you will not be able to convert it to
HPE ESM
6.9.1c
Page 32 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
default mode without reinstalling it.
l
l
Converting from default mode installation to FIPS mode is supported. If you need to do so
at any time, refer to the Administrator’s Guide for instructions.
By default, ESM uses a self-signed certificate. If you would like to use a CA-signed
certificate, you will have to import the CA-signed certificate manually after the
configuration wizard completes successfully. Refer to the Administrator’s Guide for ESM for
details on using a CA-signed certificate.
9. If you selected FIPS mode, confirm your selection. if not, skip to the Manager Information step.
10. If you selected FIPS mode on the Select the Cipher Suite Options panel. select the cipher suite.
Suite B defines two security levels of 128 and 192 bits. The two security levels are based on the
Advanced Encryption Standard (AES) key size that is used instead of the overall security provided
by Suite B. At the 128-bit security level, the 128 bit AES key size is used. However, at the 192-bit
security level, a 256 bit AES key size is used. Although a larger key size means more security, it also
means computational cost in time and resource (CPU) consumption. In most scenarios, the 128-bit
key size is sufficient.
11. Under Manager Information, enter the Manager’s hostname or IP address, set the user ID and
password for the admin user, and press Enter.
Caution: Manager host name is the local host name, IP address, or fully-qualified domain name
of the machine where the Manager is installed. This name is what all clients (for example,
ArcSight Console) specify to connect to the Manager. Using a host name and especially a fullyqualified domain name instead of an IP address is recommended for flexibility.
If you do not want the hostname on your DNS server, add a static host entry to the
/etc/hosts file to resolve the host name locally.
The Manager hostname is used to generate a self-signed certificate. The Common Name (CN)
in the certificate is the Manager host name that you specify in this screen.
Although the Manager uses a self-signed certificate by default, you can switch to using a CAsigned certificate if needed. You can do this after installation. Refer to the Administrator’s
Guide for instructions.
12. Under Packages, ESM Express does not license these packages. Press Enter to continue.
Otherwise, select the optional packages that you are licensed to use. In addition to these optional
packages, there are default standard content packages that are installed automatically on the
ArcSight Manager. These default packages provide essential system health and status operations,
and you can use them immediately to monitor and protect your network.
For more information about packages, see the ArcSight Administration and ArcSight System
Standard Content Guide.
13. Under About to Configure ESM.
HPE ESM
6.9.1c
Page 33 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
Caution: Once you type yes and press Enter, the product is installed as specified.
14. When the configuration says Configuration Completed Successfully, type Yes and then Enter to
exit.
15. Important! This step is required in order to start the services. Log in as user root and run the
following script to set up the required services:
/opt/arcsight/manager/bin/setup_services.sh
After you have completed the installation, check the location and size of your storage volumes and
make any necessary changes. You can do this in the ArcSight Command Center. Refer to the
ArcSight Command Center User's Guide, the "Administration" chapter under "Storage and Archive”
section for details regarding your storage volumes.
You can rerun the wizard manually only if you exit it at any point before you reach the first
configuration screen called “About to Configure ESM v6.9.1c”. See "Rerunning the ESM
Configuration Wizard" on page 36 for details.
Handling a Time Zone Update Error
There are two possible errors that can happen when the installer tries to update the time zone
information for the ESM components.
1. A timezone version 2014f or later rpm for your operating system is not installed.
2. The /etc/localtime link is pointing to invalid or non-existent timezone.
You can choose to continue with the installation even if the right timezone package is unavailable or
incorrectly setup. If you choose to do so, you can update timezone info for the ESM components after
the installation.
Use the following procedure after ensuring that you have downloaded and installed the correct
package and the link is set correctly. (Remember, this is for after the installation is complete.):
1. As user arcsight, shut down all arcsight services. (This is important.) Run
/opt/arcsight/services/init.d/arcsight_services tryforcestop all
2. As user root, run the following command (this is one line):
/opt/arcsight/manager/bin/arcsight tzupdater /opt/arcsight /opt/arcs
ight/manager/lib/jre-tools/tzupdater
3. Monitor for any failure.
4. Restart all arcsight services.
HPE ESM
6.9.1c
Page 34 of 94
ESM Installation Guide
Chapter 3: Installing Software ESM
Uninstalling ESM
Use the following procedure to uninstall ESM.
1. Log in as user root.
2. Run the following command:
/opt/arcsight/manager/bin/remove_services.sh
3. Log in as user arcsight.
4. Shut down any arcsight processes that are still running.
To check for running arcsight processes, run:
ps -elf | grep "/opt/arcsight"
To shut down any arcsight processes that are running, run:
kill -9 <process_id_number>
5. Run the uninstaller program from either the directory where you have created the links while
installing the product or if you had opted not to create links, then run this from the
/opt/arcsight/suite/UninstallerData directory:
./Uninstall_ArcSight_ESM_Suite_6.9.1
Alternatively, you can run the following command from the /home/arcsight (or wherever you
installed the shortcut links) directory:
./Uninstall_ArcSight_ESM_Suite_6.9.1
6. Verify that the /tmp and /opt/arcsight directories contain no ESM-related files. If that is not
the case:
a. While logged in as user arcsight kill all arcsight processes.
b. Delete all remaining arcsight-related files/directories in /opt/arcsight/ and /tmp directory
manually.
c. Delete any links created during installation.
HPE ESM
6.9.1c
Page 35 of 94
Chapter 4: Post-Installation Considerations
This section includes information about rerunning the installation and configuration wizard.
Rerunning The Installer
For software ESM, if the installation is interrupted and the process exits (for any reason) before you get
to "File Delivery Complete:"
1. Remove all install.dir.xxxx directories from the /tmp directory.
2. Remove all directories and files in the /opt/arcsight directory.
3. From wherever you saved it, rerun the installer, ./ArcSightESMSuite.bin.
.
Rerunning the ESM Configuration Wizard
You can rerun the wizard manually only if you exit it at any point before the actual configuration begins.
That section is entitled: "About to Configure ESM"
If for any reason you cancel out of the wizard or run into an error before the configuration begins, you
can rerun the wizard manually.
1. To rerun the configuration wizard use the following command:
rm /opt/arcsight/manager/config/fbwizard*
2. To run the First Boot Wizard, run the following from the /opt/arcsight/manager/bin
directory while logged in as user arcsight:
In GUI mode (software ESM only)
./arcsight firstbootsetup -boxster -soft
In console mode
./arcsight firstbootsetup -boxster -soft -i console
For software ESM, Make sure that X-Window is not running when running the first boot wizard in
console mode.(X Window is not installed on the appliance.)
If you encounter a failure during the configuration stage, uninstall and reinstall ESM. On an
appliance, restore the appliance to it's factory settings and start over. See "Restore Appliance
Factory Settings" on page 92.
HPE ESM 6.9.1c
Page 36 of 94
ESM Installation Guide
Chapter 4: Post-Installation Considerations
Setting Up ESM Reports to Display in a Non-English
Environment
To enable international characters in string-based event fields to be retrieved by queries, you need to
store such characters correctly. Following the processes in this section allows ESM to correctly store and
recognize international characters.
On the Manager
This procedure is required only if you plan to output reports that use international characters in PDF
format. You will need to purchase the ARIALUNI.TTF font file.
1. On the Manager host, place the font file ARIALUNI.TTF in a folder. For example:
/usr/share/fonts/somefolder
2. Modify the ESM reports properties file, sree.properties, located in
/opt/arcsight/manager/reports/ directory by default.
Add the following line:
font.truetype.path=/usr/share/fonts/somefolder
Save the file.
3. Restart the Manager by running:
/etc/init.d/arcsight_services restart manager
4. In the ArcSight Console, select the Arial Unicode MS font in all the report elements, including the
report template. This is described in the next topic.
On the Console
Set preferences in the Console and on the Console host machine.
1. Install the Arial Unicode MS font on the Console host operating system if not already present.
2. Edit the following script located in <ARCSIGHT_HOME>/current/bin/scripts directory by
default:
On Windows: Edit console.bat
On Linux: No edits required. The coding is set correctly.
Find the section ARCSIGHT_JVM_OPTIONS and append the following JVM option:
" -Dfile.encoding=UTF8"
HPE ESM
6.9.1c
Page 37 of 94
ESM Installation Guide
Chapter 4: Post-Installation Considerations
3. In the ArcSight Console Preferences menu, set Arial Unicode MS as the default font:
Go to Edit > Preferences > Global Options > Font
On Windows: Select Arial Unicode MS from the drop-down
On Linux: Enter Arial Unicode MS
4. Set the font preferences for your reports, as described in, "Using Report Templates" in the ArcSight
Console User's Guide.
Improving the Performance of Your Server
For an appliance, you can ignore this topic because the appliance is already set up for top performance.
For software ESM on your own hard ware, you can improve the server performance by tuning your
BIOS as follows:
l
l
l
l
l
l
HyperThreading - Disable this. This setting exists on any Intel processor that supports
HyperThreading. Most recent server class processors have this. AMD processors do not have an
equivalent setting.
Intel VT-d - Disable this. This setting is specific to Intel processors and is likely to be present on most
recent server class processors. AMD has an equivalent feature named AMD-Vi.
HP Power Regulator - set to Static High Performance: This setting tells the CPU(s) to always run at
high speed, rather than slowing down to save power when the system senses that load has
decreased. Most modern CPUs have some equivalent setting.
Thermal Configuration - set to Increased cooling: This setting increases fan speed in the server to
help deal with the increased heat resulting from running the CPU(s) at high speed all the time.
Minimum Processor Idle Power Package State - This setting tells the CPU not to use any of its Cstates (various states of power saving in the CPU). All CPUs have C-states, so most servers have a
setting like this.
HP Power Profile - set this to Maximum Performance. This is not likely to have an equivalent on
non-HP servers, although some of the individual settings may exist.
This setting changes the following:
l
QPI link power management (link between physical CPU sockets) gets disabled
l
PCIe support gets forced to Gen 2
l
C-states get disabled as part of this profile
l
This setting also disables the lower speed settings on the CPU(s) so they run at high speed all the
time
HPE ESM
6.9.1c
Page 38 of 94
ESM Installation Guide
Chapter 4: Post-Installation Considerations
The Next Steps
l
l
l
l
l
Install ArcSight Console
Download the ArcSight Console and install it on a supported platform. Refer to the chapter on
installing the Console, for details on how to do this. For performance reasons, install the ArcSight
Console on a different machine than your ESM installation.
Access ArcSight Command Center
Refer to the ArcSight Command Center User’s Guide for more information on using the ArcSight
Command Center.
Read the Release Notes
The release notes for this release are available on Protect 724.
Download Use Cases
To get up and running quickly, HP ArcSight now offers Security Use Case packages available for
download at https://saas.hpe.com/marketplace/arcsight. These packages provide essential security
monitoring for network systems (such as IDS/IPS, VPN, Firewall), and packages that monitor and
analyze the event stream for critical security concerns, such as anomalous traffic and suspicious
outbound traffic.
Remote Access to the Appliance
As an option, you can configure the appliance for out-of-band remote access so that Customer
Support can access and troubleshoot the appliance if it becomes unresponsive. All appliance models
are equipped with HP Integrated Lights-Out (iLO) Advanced remote management card. Visit
http://www.hp.com/go/iLO for detailed information and documentation.
HPE ESM
6.9.1c
Page 39 of 94
Chapter 5: Installing ArcSight Console
The ArcSight Console provides a host-based interface (as opposed to the browser-based interface of
the ArcSight Command Center) to ESM. This chapter explains how to install and configure the ArcSight
Console in default mode. To install the Console in FIPS mode, see "Installing ArcSight Console in FIPS
Mode" on page 76. Section "Choosing between FIPS Mode or Default Mode" on page 10 lists the basic
differences between the modes.
Make sure the Manager is running before installing the ArcSight Console. Typically, ArcSight Console is
deployed on several perimeter machines located outside the firewall which protects the ArcSight
Manager.
Console Supported Platforms
Refer to the HP ArcSight ESM Support Matrix document available on the Protect 724 site for the most
current information on supported platforms and browsers.
Required Libraries for RHEL and CentOS (64 Bit)
On the RHEL and CentOS 6.x and later 64-bit workstations, the Console requires the latest versions of
following libraries:
pam-1.1.1-10.el6.x86_64.rpm
pam-1.1.1-10.el6.i686.rpm
libXtst-1.0.99.2-3.el6.x86_64.rpm
libXtst-1.0.99.2-3.el6.i686.rpm
libXp-1.0.0-15.1.el6.x86_64.rpm
libXp-1.0.0-15.1.el6.i686.rpm
libXmu-1.0.5-1.el6.x86_64.rpm
libXmu-1.0.5-1.el6.i686.rpm
libXft-2.1.13-4.1.el6.x86_64.rpm
libXft-2.1.13-4.1.el6.i686.rpm
libXext-1.1-3.el6.x86_64.rpm
libXext-1.1-3.el6.i686.rpm
libXrender-0.9.7-2.el6.i686.rpm
gtk2-engines-2.18.4-5.el6.x86_64.rpm
gtk2-2.18.9-6.el6.x86_64.rpm
compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm
compat-libstdc++-33-3.2.3-69.el6.i686.rpm
HPE ESM 6.9.1c
Page 40 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
compat-db-4.6.21-15.el6.x86_64.rpm
compat-db-4.6.21-15.el6.i686.rpm
Installing the Console The notes that follow include important considerations for Installing the ArcSight Console on different
operation systems.
Note: Linux:
Do not attempt to install the Console as the root user on Linux machines. If you do, the installer
prompts you to change ownership of certain directories after the installation completes, so we
recommend you perform all of the following steps as a non-root user.
This issue does not apply to Windows machines.
Note: On Macintosh platforms, please make sure that:.
l
l
l
You are using an Intel processor based system.
Keep in mind that keytoolgui does not work on the Mac, so use keytool commands, documented
in the ESM Administrator's Guide, whenever you need to manage the keystore or certificates.
Before you start the Console, make sure to set up a default printer to which to print. if you open
a channel, select some rows, right-click on them and select Print Selected Rows from the
resulting menu, the Console will crash if a default printer is not set up.
Make sure that ESM is installed before installing the ArcSight Console.
1. To install ArcSight Console, run the self-extracting archive file that is appropriate for your target
platform. Go to the directory where the ArcSight Console Installer is located.
Platform
Installation File
Linux
ArcSight-6.9.1.nnnn.0-Console-Linux.bin
Windows
ArcSight-6.9.1.nnnn.0-Console-Win.exe
Macintosh
ArcSight-6.9.1.nnnn.0-Console-MacOSX.zip
The location of the installer's log files are shown below:
Platform
Installation Log Files
Linux
/home/<user>
Windows
C:\Users\<user>
HPE ESM
6.9.1c
Page 41 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
Platform
Installation Log Files
Macintosh
/Users/<user>
2. Click Next in the Installation Process Check screen.
3. Read the introductory text in the Introduction panel and click Next.
4. On the License Agreement panel, the “I accept the terms of the License Agreement” radio button
is disabled until you scroll to the bottom of the agreement text. After you have read the text, click
the “I accept the terms of the License Agreement” radio button and click Next.
5. Read the text in the Special Notice panel and click Next.
6. On the Choose ArcSight installation directory panel, you can accept the default installation
directory, click Choose to navigate to an existing folder, or type in a path to where you want to
install the Console. If you specify a folder that does not exist, the folder is created for you.
Caution: Do not use spaces in install paths. This includes Linux, Macintosh, and Windows
systems. The Console installer does not display any error message, but the Console will not
start.
7. On the Choose Shortcut Folder panel, select where you would like to create a shortcut for the
Console and uninstall icons and click Next.
8. View the summary in the Pre-Installation Summary screen and click Install if you are satisfied
with the paths listed. If you want to make any changes, use the Previous button to do so.
You can view the installation progress in the progress bar.
Note: On Windows, when the installer is configuring the Console (the Please Wait panel), you
might see a message that the TZData update was not successful. If you get that message, click OK
and continue. The Console installs successfully. Usually, TZData is correctly updated regardless of
this message. To make sure check that the time stamp on the files in the
C:\arcsight\Console\current\jre\lib\zi.tzdata_2014j_1\ directory matches the date
and time when you installed the Console. If the time stamp is old or the files are missing, uninstall
then re-install the Console.
Configuring the ArcSight Console
After the Console has been installed, you will need to configure it.
1. The wizard asks if you would like to transfer configuration options from an existing installation of
ArcSight Console. Choose No, I do not want to transfer the settings to create a new, clean
installation and click Next.
2. Select the mode in which you would like to configure the Console, Default or FIPS.
Select the same mode in which the Manager is installed.
HPE ESM
6.9.1c
Page 42 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
If you select Run console in FIPS mode, you get a warning that once you switch to FIPS mode you
cannot revert to default mode and are asked if you want to continue.
(FIPS mode only) You will be prompted to select a cipher suite. The choices are:
l FIPS 140-2
l
FIPS with Suite B 128 bits
l
FIPS with Suite B 192 bits.
Suite B defines two security levels of 128 and 192 bits. The two security levels are based on the
Advanced Encryption Standard (AES) key size that is used instead of the overall security provided
by Suite B. At the 128-bit security level, the 128 bit AES key size is used. However, at the 192-bit
security level, a 256 bit AES key size is used. Although a larger key size would mean more security, it
would also mean computational cost in terms of time and resource (CPU) consumption. In most
scenarios, the 128-bit key size is sufficient.
Click Next.
3. Enter the host name of the Manager to which the Console will connect.
Caution: Do not change the Manager’s port number.
Click Next.
4. Select Use direct connection option and click Next. You can set up a proxy server and connect to
the Manager using that server if you cannot connect to the Manager directly.
If you select the Use proxy server option, you will be prompted to enter the proxy server
information Proxy Host Name and Proxy Host.
Enter the Proxy Host name and click Next.
5. The ArcSight Console configuration wizard prompts you to choose the type of client
authentication you want to use. The choices are:
l
Password Based Authentication
l
Password Based and SSL Client Based Authentication
l
Password Based or SSL Client Based Authentication
l
SSL Client Only Authentication
Caution: In order to use PKCS#11 authentication, you must select the Password Based or
SSL Client Based Authentication method.
Note: Password Based and SSL Client Based Authentication option currently supports
only client keystore for SSL based authentication. Using PKCS#11 token as your SSL Client
Based authentication method within the Password Based and SSL Client Based
HPE ESM
6.9.1c
Page 43 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
Authentication option is not currently supported.
If you select Password Based Authentication, you to log in with a user name and password.
If you select Password Based and SSL Client Based Authentication, you need a client certificate
to log in, in addition to your user name and password. Follow the procedure described in ESM
Administrator’s Guide to set up the client certificate.
If you selected Password Based or SSL Client Based Authentication or SSL Client Only
Authentication, you will be required to select your SSL client based authentication method. The
choices are:
l
Client Key Store
l
PKCS#11 Token
If you plan to use a PKCS #11 token, you should have the token’s software and hardware already set
up. If you have not set up the token yet, you can select Client Key Store and continue with the
installation. After you have finished installing the Console, you can refer to "Setting Up to Use a
PKCS#11 Provider " on page 61 for instructions on how to set up the token.
If you select Client Key Store, you will see a message reminding you to set up the client certificate
after the installation completes.
After completing the Configuration Wizard, follow the procedure described in ESM Administrator’s
Guide to set up the client certificate.
6. The ArcSight Console configuration wizard prompts you to specify the default web browser you
want to use to display reports, Knowledge Centered Support articles, and other web page content.
Specify the location of the executable for the web browser that you want to use to display the
Knowledge Centered Support articles and other web pages launched from the ArcSight Console.
Browse to and select the Browser Executable and click Next.
7. Select whether this installation of the Console will be used by a single user or multiple users.
You can choose from these options:
l
This is a single system user installation. (Recommended)
Select this option when:
HPE ESM
6.9.1c
Page 44 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
There is only one system account on this machine that one or more Console users will use to
connect to the Console. For example, a system account, admin, is used by Console users Joe,
Jack, Jill, and Jane.
o
OR
All Console users who will use this machine to connect to the Console have their own user
accounts on this machine AND these users have write permission to the ArcSight Console’s
\current directory.
o
Advantage: Logs for all Console users are written to one central location in ArcSight
Console’s \current\logs directory. The user preferences files (denoted by
username.ast) for all Console users are located centrally in ArcSight Console’s \current.
Disadvantage: You cannot use this option if your security policy does not allow all Console
users to share a single system user account or all users to write to the ArcSight Console’s
\current directory.
l
Multiple users will use this installation
Select this option when:
o
All Console users who will be using this machine to connect to the Console have their own
user accounts on this machine
AND
o
These users do not have write permission to the ArcSight Console’s \current\logs
directory
By selecting this option, each user’s log and preferences files are written to the user’s local
directory (for example, Document and Settings\username\.arcsight\console on
Windows) on this machine.
Advantage: You do not have to enable write permission for all Console users to the Console’s
\current directory.
Disadvantages: Logs are distributed. Therefore, to view logs for a specific time period, you will
have to access them from the local directory of the user who was connected at that time.
If you do not enable write permission for all the Console users to the Console’s \current
directory, they can only run the following commands (found in the Console’s \bin\scripts)
from the Console command-line interface:
o
sendlogs
o
console
o
exceptions
o
portinfo
o
websearch
All other commands require write permission to the Console’s \current directory.
HPE ESM
6.9.1c
Page 45 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
Note: The location from which the Console accesses user preference files and to which it writes
logs depends on the option you select above. Therefore, if you switch between these options
after the initial configuration, any customized user preferences may appear to be lost. For
example, your Console is currently configured with the “This is a single system user installation”
option on a Windows machine. Console user Joe’s customized preferences file is located in the
Console’s <ARCSIGHT_HOME>\current. Now, you run the consolesetup command and
change the setting to ‘Multiple system users will use this installation.’ Next time Joe connects to
the Console, the Console will access Joe’s preference file from Document and
Settings\joe\.arcsight\console, which will contain the default preferences.
On Windows, when the installer is configuring the Console (the Please Wait panel), you might see a
message that the TZData update was not successful. If you get that message, click OK and continue.
The Console installs successfully. Usually, TZData is correctly updated regardless of this message.
To make sure check that the time stamp on the files in the
C:\arcsight\Console\current\jre\lib\zi.tzdata_2014j_1\ directory matches the date
and time when you installed the Console. If the time stamp is old or the files are missing, uninstall
then re-install the Console.
8. You have completed configuring your ArcSight Console. Click Finish on the final panel to close the
configuration wizard.
9. Click Done in the next screen.
10. For best results, install the ArcSight Console on an operating system that is set to the same locale
as the Manager. During startup, the ArcSight Console and the Manager automatically detect and
use the locale from the operating system.
However, if you are installing the Console on a Linux machine, edit the file
/home/arcsight/.bash_profile by adding the line:
export LANG=[language].UTF-8
...where [language] is one of these:
en_US (English)
zh_CN (Simplified Chinese)
zh_TW (Traditional Chinese)
ja_JP (Japanese)
fr_FR (French)
ko_KR (Korean)
ru_RU (Russian)
Importing the Console’s Certificate into the Browser
The online help from the Console is displayed in a browser. Follow these steps in order to view the
online help in a browser if you are using SSL Client Based Authentication mode:
HPE ESM
6.9.1c
Page 46 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
1. Export the keypair from the Console. For more information, refer to the ESM Administrator’s Guide
in the "Export a Key Pair" topic.
2. Import the Console’s keypair into the browser.
You have installed the ArcSight Console successfully. Please be sure to install any available patches for
the Console. Refer to the ArcSight ESM Patch Release Notes for instructions on how to install a patch
for the Console.
Character Set Encoding
Install the Console on a machine that uses the same character set encoding as the Manager.
If the character encodings do not match, then user IDs and passwords are restricted to using the
following characters:
a-z A-Z 0-9_@.#$%^&*+?<>{}|,()-[]
If the Console encoding does not match and a user ID contains other characters, that user should not
save any custom shortcut key (hot key) schema. The user ID is not properly encoded in the keymap .xml
file and that makes it impossible to establish the user’s shortcut schema during login. In that
circumstance, all logins fail on that Console.
If you must use a non-UTF-8 encoding, and you must have user IDs with other characters in them,
custom shortcut keys are not supported on any Console where these users would log in. In that
situation, add the following property to the console.properties file:
console.ui.enable.shortcut.schema.persist=false. This property prevents custom shortcut
key schema changes or additions.
If the Console encoding does not match and a password contains other characters, that user cannot
log in from that Console, as the password hash won’t match the one created on the Manager when the
password was created.
Starting the ArcSight Console
Note: On the ArcSight Console machine, for any special IPv4/IPv6 configurations that do not
match the DNS server entries, you can instruct the ArcSight Console how to connect to ESM by
providing an additional option, java.net.preferIPv6Addresses. Do that by setting the
environment variable ARCSIGHT_JVM_NET_OPTIONS.
For example, to instruct an ArcSight Console using IPv6 DNS entries, use the following commands:
On Unix
export ARCSIGHT_JVM_NET_OPTIONS=-Djava.net.preferIPv6Addresses=true
On Windows
HPE ESM
6.9.1c
Page 47 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
set ARCSIGHT_JVM_NET_OPTIONS=-Djava.net.preferIPv6Addresses=true
After installation and setup is complete, start ArcSight Console using the shortcuts installed or open a
command window on the Console’s bin directory and run:
On Windows:
arcsight console
On Unix:
./arcsight console
Depending on the client authentication method you selected when installing the Console, you will see
the following buttons on the login screen:
If you selected...
You will see the following buttons...
Password Based Authentication
Login
Cancel
Password Based and SSL Client
Based Authentication
Login
Password Based or SSL Client
Based Authentication
If you selected Client Keystore as your authentication method,
you will see
Cancel
l
Login (username and password)
l
SSL Client Login
l
Cancel
If you selected PKCS#11 Token, you will see
SSL Client Only Authentication
l
PKCS #11 Login
l
Login
l
Cancel
If you selected Client Keystore as your authentication method,
you will see
l
The user ID and Password fields are grayed out (disabled)
because login authentication is by client keystore.
l
Login
l
Cancel
If you selected PKCS #11 Token, you will see
HPE ESM
6.9.1c
Page 48 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
If you selected...
You will see the following buttons...
l
PKCS #11 Login (SSL client authentication)
l
Cancel
Note: Under certain circumstances, you might see a Login Failed message that, for the cacerts
folder, access is denied. Ensure that the arcsight user has write access to the cacerts file. If this does
not clear the problem, and you are on a Windows system, the cause may be due to file locks on the
cacerts file. These may be cleared by rebooting your computer.
Logging into the Console
Note: While logging into a Manager that has been configured to use Password Based or SSL Client
Based Authentication, if you try to log in using a certificate and the login fails, all subsequent
attempts to use the username/password login will also fail during the same session. To work around
this, restart the Console.
To start the Console, click Login. When you start the Console for the first time, after you click Login,
you will get a dialog asking you whether you want to trust the Manager’s certificate. The prompt will
show details specific to your settings. Click OK to trust the Manager’s certificate. The certificate will be
permanently stored in the Console’s truststore and you will not see the prompt again the next time you
log in.
Reconnecting to the ArcSight Manager
If the ArcSight Console loses the connection to the ArcSight Manager (for example, because the
Manager was restarted), 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.
Connections to the ArcSight Manager cannot be re-established while the ArcSight Manager is
restarting or if the Manager refuses the connection. In addition, you may see connection exceptions
during the Retry process while the connection is lost or ArcSight Manager is restarting.
Reconfiguring the ArcSight Console
You can reconfigure ArcSight Console at any time by running the following command within a
command window from the Console’s bin directory:
On Windows: arcsight consolesetup
On Linux: ./arcsight consolesetup
HPE ESM
6.9.1c
Page 49 of 94
ESM Installation Guide
Chapter 5: Installing ArcSight Console
and follow the prompts.
Uninstalling the ArcSight Console
Before uninstalling the ArcSight Console, exit the current session.
To uninstall on Windows, run the Start > All Programs > ArcSight ESM 6.9c Console > Uninstall
ArcSight ESM Console 6.9c program. If a shortcut to the Console was not installed on the Start menu,
locate the Console’s UninstallerData folder and run:
ArcSight_ESM_Console_6.9.1c.exe
To uninstall on Unix hosts, run the uninstaller program from either the directory where you created the
links while installing the product or if you had opted not to create links, then run this from the
/opt/arcsight/console/current/UninstallerData directory:
./ArcSight_ESM_Console_6.9.1c
Alternatively, you can run the following command from the /home/arcsight (or wherever you
installed the shortcut links) directory:
./Uninstall_ArcSight_ESM_Console_6.9.1c
Note: The UninstallerData directory contains a file .com.zerog.registry.xml with Read,
Write, and Execute permissions for everyone. On Windows hosts, these permissions are required for
the uninstaller to work. However, on UNIX hosts, you can change the permissions to Read and
Write for everyone (that is, 666).
HPE ESM
6.9.1c
Page 50 of 94
Appendix A: Troubleshooting
The following information may help solve problems that might occur when installing or using ESM. In
some cases, the solution can be found here or in other ESM documentation, but HP ArcSight Customer
Support is available if you need it.
If you intend to have HP ArcSight Customer Support guide you through a diagnostic process, please
prepare to provide specific symptoms and configuration information.
Location of Log Files for Components
The log files can be found in the following location:
Log file name
location
Description
First Boot Wizard Logs
fbwizard.log
/opt/arcsight/manager/logs/default/
Contains
detailed
troubleshootin
g information
logged during
the steps in
"Using the
Configuration
Wizard" on
page 31.
firstbootsetup.lo
g
/opt/arcsight/manager/logs/
Contains brief
troubleshootin
g information
about
commands that
ran during the
steps in "Using
the
Configuration
Wizard" on
page 31.
CORR-Engine Log Files
HPE ESM 6.9.1c
Page 51 of 94
ESM Installation Guide
Appendix A: Troubleshooting
Log file name
location
logger_server.log /opt/arcsight/logger/current/arcsight/logger/lo
gs
Description
Contains
troubleshootin
g information
about the
CORR-Engine
logger_
server.out.log
/opt/arcsight/logger/current/arcsight/logger/lo
gs
CORR-Engine
stdout log file
arcsight_
logger.log
/opt/arcsight/logger/current/arcsight/logger/lo
gs
Logs for
setting up the
CORR-Engine
logger_init_
driver.log
/opt/arcsight/logger/current/arcsight/logger/lo
gs
Logs for
setting up the
CORR-Engine
logger_init.sh.log
/opt/arcsight/logger/current/arcsight/logger/lo
gs
Logs for
setting up the
CORR-Engine
logger_
wizard.log
/opt/arcsight/logger/current/arcsight/logger/lo
gs
Logs for
setting up the
CORR-Engine
logger_
wizard.out.log
/opt/arcsight/logger/current/arcsight/logger/lo
gs
Logs for
setting up the
CORR-Engine
server.log
/opt/arcsight/manager/logs/default
Contains
troubleshootin
g information
about the
Manager
server.std.log
/opt/arcsight/manager/logs/default
Contains the
stdout output
of the Manager
server.status.log
/opt/arcsight/manager/logs/default
Contains a
dump of all the
MBeans, the
Manager Log Files
HPE ESM
6.9.1c
Page 52 of 94
ESM Installation Guide
Appendix A: Troubleshooting
Log file name
location
Description
memory status,
thread status,
etc.
Log file for services
arcsight_
services.log
/opt/arcsight/services/logs/
Contains
information
from
commands that
manage
ArcSight
service
processes.
monit.log
/opt/arcsight/services/monit/data/
Contains
timing
information
from startup
and shutdown
of ArcSight
service
processes.
If You Encounter an Unsuccessful Installation
Here is what to do if you encounter an unsuccessful installation, or if your installation is corrupted.
For an appliance, restore the factory settings. See "Restore Appliance Factory Settings" on page 92.
For software ESM, there are two possible cases.
Case 1 – If your installation became corrupted after running setup_services.sh, run the following
script as root user:
remove_services.sh
Then run the Recovery procedure below.
Case 2 –If your installation became corrupted before running setup_services.sh, run the recovery
procedure.
Recovery Procedure – Run this for either case 1 or case 2, above.
HPE ESM
6.9.1c
Page 53 of 94
ESM Installation Guide
Appendix A: Troubleshooting
1. After exiting the uninstall process, stop any ArcSight services that are currently running. Either:
a. Log in as user root.
b. run the following command.
/opt/arcsight/manager/bin/remove_services.sh
2. Delete all ArcSight-related files/directories under /opt/arcsight and /tmp directory.
3. Delete any shortcuts created during installation (by default in the home directory of the arcsight
user).
4. For Software ESM, re-install the product.
Customizing the Manager
The First Boot Wizard allows you to configure the Manager and the CORR-Engine Storage. To
customize a component further, you can follow these instructions to start the setup program for the
component:
While logged in as user arcsight,
1. Stop the Manager if it is running:
/etc/init.d/arcsight_services stop manager
2. Run the following command from /opt/arcsight/manager/bin directory:
./arcsight managersetup
3. Follow the prompts on the wizard screens. See the Administrator’s Guide for information on any
specific screen.
4. Restart the Manager after the wizard completes by running:
/etc/init.d/arcsight_services start manager
Fatal Error when Running the First Boot Wizard
If you encounter a fatal error while running the First Boot Wizard, the wizard will display an error
message and then exit. Check the log files for the particular component for any error messages. The log
files are listed in the section "Location of Log Files for Components" on page 51.
To resolve this issue, try the following steps:
1. Check the /opt/arcsight/manager/logs/default/fbwizard.log file to figure out where
the error occurred.
HPE ESM
6.9.1c
Page 54 of 94
ESM Installation Guide
Appendix A: Troubleshooting
2. Check to make sure that all the required TCP ports mentioned in the section "Keep these TCP
Ports Open" on page 26 are open.
3. If your error occurred before any component got configured, log in as user root and do the
following:
Clear out (delete) the contents of the /opt/arcsight directory.
Rerun the setup using the following commands:
cd
/home/arcsight/install.esm/ESMComponents/service/opt/arcsight/services/bin
/scripts
(All one line.)
./esm_setup.sh
If the above steps do not work, for example, if the setup has already started to configure the Manager
or if your installation is corrupted, then restore the factory settings. See "Restore Appliance Factory
Settings" on page 92.
Changing the Hostname of Your Machine
Wherever you see "hostname," you may assume it means "hostname or IP address." If you have
configured peering, make sure to re-establish the peer relationship.
If you are using the High Availability module, the procedure is different. Refer to the ArcSight High
Availability Module User's Guide for the proper procedure.
In case you want to change the IP address of your machine after running the First Boot Wizard
successfully, follow these steps:
Note: Run the Manager setup command when logged in as user arcsight.
1. Stop all ArcSight services by running (as user arcsight):
/etc/init.d/arcsight_services stop all
2. Change the hostname of your machine.
3. Reboot the machine.
4. As the user arcsight, stop the Manager by running:
/etc/init.d/arcsight_services stop manager
5. As the user arcsight, run the Manager’s setup program from the /opt/arcsight/manager/bin
directory:
./arcsight managersetup
HPE ESM
6.9.1c
Page 55 of 94
ESM Installation Guide
Appendix A: Troubleshooting
a. Enter the new host name (that you set for your machine in the steps above), in the Manager
Host Name field when prompted by the wizard – and in every other field where the old
hostname is displayed.
b. Make sure to select the self-signed keypair option when prompted by the wizard and enter the
required information to generate the self-signed certificate containing the new host name.
6. As the user arcsight, start the Manager by running:
/etc/init.d/arcsight_services start manager
7. As the user arcsight, see if the manager is running yet by running the command.
/etc/init.d/arcsight_services status manager
Run this command about once a minute, until you see the line “manager service is available." Then
you can continue with the next step.
8. Import the Manager’s newly-generated certificate on all clients (Console and connectors) that
access the Manager. Use keytoolgui. See the “Using Keytoolgui to Import a Certificate” section in
the “Configuration” chapter in the ESM Administrator’s Guide available on the HP ArcSight
Customer Support download site for details.
9. Test to make sure that
l
The clients can connect to the Manager
l
Peer configuration works as expected. If not, redo the peer configuration.
Changing the Host Name of the Machine
after Running the First Boot Wizard
Wherever you see "host name," you may assume it means "host name or IP address."
If you have configured peering, make sure to re-establish the peer relationship when you are done.
If you are using the High Availability module, the procedure is different. Refer to the ArcSight High
Availability Module User's Guide for the proper procedure.
Note: Run the managersetup command when logged in as user arcsight.
In case you want to change the host name or IP of the machine after running the First Boot Wizard
successfully, follow these steps:
1. Stop all services by running (as user arcsight):
/etc/init.d/arcsight_services stop all
2. Change the host name or IP address of your machine.
HPE ESM
6.9.1c
Page 56 of 94
ESM Installation Guide
Appendix A: Troubleshooting
3. Reboot the machine.
4. As the user arcsight, stop the Manager by running:
/etc/init.d/arcsight_services stop manager
5. As the user arcsight, run the Manager’s setup program from the /opt/arcsight/manager/bin
directory as user arcsight:
./arcsight managersetup
a. Enter the new host name or IP (that you changed for your machine in the steps above), in the
Manager Host Name field when prompted by the wizard.
b. Make sure to select the self-signed keypair option when prompted by the wizard and enter the
required information to generate the self-signed certificate containing the new host name or
IP.
If you are in FIPS mode, you do not get an option to regenerate a keypair. Manually delete the
key pair, regenerate it, and go to the next step to restart the Manager.
6. As the user arcsight, start the Manager by running:
/etc/init.d/arcsight_services start manager
7. Start ArcSight Command Center by running:
https://<IP address>:8443/
Where <IP address> is the host name or IP address of the ESM or ESM Express. (Host names with
underscores do not work on IE, so use the IP address.)
8. Import the Manager’s certificate on all clients (Console and connectors) that will be accessing the
Manager. You can do so using the keytool. See the “Import a Certificate” topic in the “SSL
Authentication” chapter in the ESM Administrator’s Guide, available on the HP ArcSight Customer
Support download site for details on how to do this.
9. Test to make sure that the clients can connect to the Manager.
HPE ESM
6.9.1c
Page 57 of 94
Appendix B: Default Settings For Components
This appendix gives you the default settings for each software component in ESM.
You can always customize any component by running its setup program.
General Settings
Setting
default password for truststore
changeit
default password for cacerts
changeit
default password for keystore
password
CORR-Engine Settings
The following are some of the default values that have been pre-configured in the CORR-Engine for
you:
Setting
Default Value
Location of Logger
/opt/arcsight/logger
Database user name
arcsight
Database Port
3306
Manager Settings
Note: The Manager uses a self-signed certificate, which gets generated for you when you configure
the system using the First Boot Wizard. When you log into the Console for the very first time you
will be prompted to accept the Manager’s certificate. You can either click Yes in that dialog or
optionally import the Manager’s certificate manually at a later time.
HPE ESM 6.9.1c
Page 58 of 94
ESM Installation Guide
Appendix B: Default Settings For Components
The following are some of the default values that have been pre-configured in the Manager for you:
Setting
Default Value
Location of Manager
/opt/arcsight/manager
Manager host name
Host name or IP address of ESM
Manager Port
8443
Manager Java Heap Memory
16 GB
Authentication Type
Password Based
Type of certificate used
Self-signed certificate
Default password for keystore
password
Default password for cacerts
changeit
Default password for truststore
changeit
Default password for nssdb and
nssdb.client (both used in FIPS
mode)
changeit
E-mail Notification
Internal SMTP server. If you want to use an External SMTP
server,
1. Stop the Manager by running the following command (as
user arcsight):
/etc/init.d/arcsight_services stop manager
2. Run the following command from the
/opt/arcsight/manager/bin directory and set up the
external SMTP server when prompted:
./arcsight managersetup
3. Start the Manager by running (as user arcsight):
/etc/init.d/arcsight_services start manager
Sensor Asset Auto Creation
true
Packages/default content
installed
Default system content
HPE ESM
6.9.1c
Page 59 of 94
Appendix C: Using PKCS
Public-Key Cryptography Standard (PKCS) comprises standards used for reliable and secure public key
cryptography. Public Key Cryptography works by encrypting the data at the sender's end and
decrypting it at the receiver's end.
ESM supports the use of a PKCS#11 token such as the Common Access Card (CAC) or 90Meter for
identity verification and access control. It is used to log into the Manager from a user interface. PKCS#11
is Public-Key Cryptography Standard (PKCS), published by RSA Laboratories which describes it as “a
technology-independent programming interface, called Cryptoki, for cryptographic devices such as
smart cards and PCMCIA cards.”
You can use the PKCS#11 token to log in regardless of the mode in which ArcSight Console is running,
in FIPS 140-2 mode or default mode.
PKCS#11 authentication is not supported with Radius, LDAP and Active Directory authentication
methods.
PKCS#11
PKCS#11, one of the PKCS standards, is an API defining a generic interface to cryptographic tokens,
software tokens and hardware tokens such as hardware security modules and smartcards. A
cryptographic token is a security device that is used to authorize the use of the software or hardware,
such as the smartcard, Common Access Card (CAC), or 90Meter. The credentials of the authorized user
are stored on the hardware itself. ESM uses the PKCS#11 interface provided by the Network Security
Services (NSS) cryptographic module to communicate with it (the NSS cryptographic module). The use
of PKCS #11 is an example of client-side authentication.
PKCS#11 Token Support in ESM
ESM supports any PKCS#11 Token vendor that supports PKCS#11 2.0 or above. Make sure that the
vendor’s driver and the PKCS#11 driver DLL are installed on the machine on which you plan to use the
PKCS#11 token.
Before you use the PKCS#11 token, make sure that you have installed the provider software on the
ArcSight Console system with which you plan to use the PKCS#11 token. Refer to your PKCS#11 token
provider’s documentation on how to install and configure your cryptographic device.
You can use a PKCS#11 token regardless of the mode in which the ESM client is running (FIPS 140-2
mode or default mode). However, you must configure the ESM Manager to use “Password or SSL
Authentication” when communicating with clients, which you set up by running the Manager
HPE ESM 6.9.1c
Page 60 of 94
ESM Installation Guide
Appendix C: Using PKCS
Configuration Wizard, as documented in the chapter by that name in the Administrator Guide. It is
easier to use the ArcSight Command Center, as follows:
1. Log in to the Command Center.
2. Go to the Administration tab.
3. Select Configuration Management, on the left.
4. Select Authentication Configuration.
5. Select Password or SSL Client Based authentication.
6. Restart the ArcSight Manager.
To use a PKCS #11 token, make sure that the token’s CA’s root certificate and the certificate itself are
imported into the ArcSight Manager’s truststore. In the ArcSight Command Center, you can edit the
External ID to match the common name on the Admin tab.
PKCS#12
PKCS#12, also a PKCS standard, defines a file format, the .pfx file format, which is used to store private
keys and their accompanying public key in a single encrypted file in the NSS DB. The .pfx files are
password protected. Key pairs stored in NSS DB are required to be stored in this format. When the
ArcSight Manager is configured to run in FIPS mode, its key pairs are stored in the .pfx format in the
NSS DB. PKCS #12 is applicable to server-side authentication.
Setting Up to Use a PKCS#11 Provider
Even though ESM supports authentication through any PKCS#11 token, this appendix covers how to
use the ActivClient’s Common Access Card (CAC) as an example. The steps to set up a CAC card are:
1. "Install the PKCS#11 Provider’s Software" below on each client machine. That includes the ArcSight
Console and every machine using a browser to access the ArcSight Command Center.
2. "Map a User’s External ID to the Subject CN" on the next page
3. "Obtain the CAC/90Meter’s Issuers’ Certificate" on page 64
4. "Extract the Root CA Certificate From the CAC/90Meter Certificate" on page 65
5. "Import the CAC/90Meter Root CA Certificate into the ArcSight Manager" on page 67
6. "Select Authentication Option in ArcSight Console Setup" on page 69
Install the PKCS#11 Provider’s Software
Before you use the PKCS#11 token, make sure that you have installed its software on each client system.
That includes the ArcSight Console and any machine with a browser from which you intend to access a
HPE ESM
6.9.1c
Page 61 of 94
ESM Installation Guide
Appendix C: Using PKCS
web-based interface. Refer to your PKCS#11 provider’s documentation on how to install and configure
it.
Note: Install both the 32-bit version and the 64-bit version of the ActivClient software if you are on
a 64-bit system. You can do so by double-clicking on the setup.exe link instead of the .msi files
for the specific platform.
Install a proper PKCS#11 provider, such as 90Meter or ActivClient. Copying separate dlls might not be
enough. In some cases a library specified in arcsight consolesetup is just an entry point that needs
other provider modules.
For ActivClient on 64-bit platforms always install both 32 and 64-bit components of ActivClient 6.2 or
7.0.2.
For 90Meter, install SCM_1.2.25_64Bit_S.msi. This comes with the 32-bit library as part of your install,
which is required.
Map a User’s External ID to the Subject CN
The CAC/90Meter card contains three types of certificate, Signature, Encryption, and ID certificates.
The following instructions relate to identity certificate, which is used for SSL handshake during
PKCS#11 login.
Map the Common Name (CN) on the PKCS#11 token to a User’s External ID on the ArcSight Manager.
The external user ID must be identical to the Common Name that appears in the PKCS#11 token’s ID
certificate (include any spaces and periods that appear in the Common name). For example
john.smith.9691998563.This allows the ArcSight Manager to know which user is represented by the
identity stored in the PKCS#11 token.
You can do this in the Command Center’s Admin tab under User Management, when adding or editing
a user.
The following screen shots demonstrate how to find the CN and map it to the User's External ID for
ActivClient. It is just an example. For other PKCS#11 providers you would perform similar steps using
different UI specific to the provider. Refer to the provider's documentation for instructions.
1. Obtain the Subject CN from the CAC/90Meter card.
a. Insert the CAC/90Meter card into the reader if not already inserted.
b. Start the ActivClient Software by clicking Start > ActivIdentity > ActivClient > User Console.
HPE ESM
6.9.1c
Page 62 of 94
ESM Installation Guide
Appendix C: Using PKCS
c. Double-click My Certificates in the following screen:
d. Double click ID Certificate in the following screen:
e. Click on the Advanced tab and copy the contents in the Common name text box. You will have
to copy it by hand on to a sheet of paper. Using the context menu to copy is not supported.
2. In the Command Center, go to the Administration tab to edit the user to make the external ID
match the CN.
a. Select User Management, on the left.
b. In the hierarchy tree on the left, click on the group containing the user.
HPE ESM
6.9.1c
Page 63 of 94
ESM Installation Guide
Appendix C: Using PKCS
c. To edit a user, click anywhere on the user’s row in the list.
The user details fields appear in the lower half of the list.
d. In the External ID field, enter the CN you obtained in step 1 and click Save. It must be identical,
character by character.
Alternately, you can make the external ID match the CN in the ArcSight Console:
a. In the ArcSight Console, go to Resources > Users > [user group] and double-click the user
whose External ID you want to map to the CAC/90Meter card common name. This opens the
Inspect/Edit pane for that user.
b. Enter the CN you obtained in step 1 into the External User ID field and click Apply.
Obtain the CAC/90Meter’s Issuers’ Certificate
PKCS#11 Token authentication is based on SSL client-side authentication. In the case of the Common
Access Card, the key pair for the client (the CAC/90Meter device) is stored within the card itself. You
need to export the CAC/90Meter’s certificate from its keystore so that you can extract the root CA and
any intermediate certificates from this certificate.
If your certificate is issued by an intermediate CA, export not only the issuer (the intermediate root CA)
certificate, but also its top root CA certificate.
Option 1:
You can obtain the CAC/90Meter card’s certificate signer’s root CA certificate and any intermediate
signers’ certificates from the PKI administrator.
Option 2:
You can export the CAC/90Meter card’s certificate and any intermediate signers’ certificates from its
keystore and then extract the root CA certificate from this certificate.
The steps to extract the CAC/90Meter card’s certificate from the card are:
1. Insert the CAC/90Meter card into the reader if not already inserted.
2. Start the ActivClient Software by clicking Start->ActivIdentity->ActivClient->User Console.
3. Double-click My Certificates in the following screen:
HPE ESM
6.9.1c
Page 64 of 94
ESM Installation Guide
Appendix C: Using PKCS
4. Double click ID Certificate in the following screen:
5. Click Export this certificate... in the following screen:
6. Enter a name for the certificate in the File name box and navigate to a location on your machine
where you want to export it to and click Save.
7. When you see the success message, click OK.
8. Exit the ActivClient window.
Extract the Root CA Certificate From the CAC/90Meter
Certificate
The CAC/90Meter certificate signer’s CA root certificate and any intermediate signers’ certificate(s)
have to be imported into the ArcSight Manager’s truststore.
HPE ESM
6.9.1c
Page 65 of 94
ESM Installation Guide
Appendix C: Using PKCS
Extract all intermediate certificates too (if any exist) using the following steps:
1. Double-click the certificate that you exported. The Certificate interface opens.
2. Click the Certification Path tab and select the root certificate as shown in the example below:
3. Click View Certificate.
4. Click the Details tab and click Copy to File....
HPE ESM
6.9.1c
Page 66 of 94
ESM Installation Guide
Appendix C: Using PKCS
5. The Certificate Export Wizard opens. Follow the prompts in the wizard screens and accept all the
defaults.
6. Enter a name for the CAC/90Meter root CA certificate file when prompted and continue with the
wizard by accepting all the defaults. The certificate is exported to the same location as the
CAC/90Meter certificate from which you extracted it.
7. Exit the Certificate dialog.
Import the CAC/90Meter Root CA Certificate into the
ArcSight Manager
This procedure is slightly different depending on whether you are in FIPS or default mode:
FIPS Mode - Import into the ArcSight Manager’s nssdb
To import the certificate into the ArcSight Manager’s nssdb:
HPE ESM
6.9.1c
Page 67 of 94
ESM Installation Guide
Appendix C: Using PKCS
1. If the ArcSight Manager is running, log in as user arcsight and use this command:
/etc/init.d/arcsight_services stop manager
2. Import the PKCS#11 token signer’s CA root certificate by running:
./arcsight runcertutil -A -n CACcert -t “CT,C,C” -d
<ARCSIGHT_HOME>\config\jetty\nssdb -i <absolute_path_to_root_cert>
Caution: For the -t option, be sure to use CT,C,C protocols only and in the same order that it
is shown above.
3. Restart the ArcSight Manager while logged in as user arcsight by running:
/etc/init.d/arcsight_services start manager
Default Mode - Import into ArcSight Manager’s Truststore
Use the following procedure to import the PKCS#11 token’s root CA certificate into the ArcSight
Manager’ truststore.
If you do not have X Window installed, use the keytool command:
1. If the ArcSight Manager is running, log in as user arcsight and use this command to stop it:
/etc/init.d/arcsight_services stop manager
2. From <ARCSIGHT_HOME> launch arcsight keytool -store managercerts -list to see
what's in ESM's trust store. There is no need to specify the exact location of ESM trust store, the
tool uses ESM's config file to find it.
3. To remove certificate with alias myKey, run arcsight keytool -store managercerts -delete -alias
myKey
4. To add a certificate and set an alias with spaces, such as JITC root CA 1 run:
arcsight keytool -store managercerts -importcert -file /tmp/NSS-DoDvirtualJITC-SubCA1.cer -alias "JITC root CA 1"
Do not miss the prompt: "Trust this certificate? [no]: yes" after the certificate key extensions are
printed on the screen.
To get the list of keystore contents, run arcsight keytool -store managercerts -list.
If you have X Window installed, you may use keytoolgui instead of keytool:
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 bin directory.
./arcsight keytoolgui
2. Click File->Open keystore and navigate to the truststore directory
(/opt/arcsight/manager/config/jetty/truststore) of the component.
3. Select the store named truststore and click Open.
HPE ESM
6.9.1c
Page 68 of 94
ESM Installation Guide
Appendix C: Using PKCS
4. Enter the password for the truststore when prompted. The default password is changeit.
5. Click Tools->Import Trusted Certificate and navigate to the location of the certificate that you
want to import.
6. Click Import.
7. When you see the message that the certificate information will be displayed, click OK.
8. The Certificate details are displayed. Click OK.
9. When asked if you want to accept the certificate as trusted, click Yes.
10. Enter an alias for the Trusted Certificate you just imported and click OK.
11. When you see the message that the import was successful, click OK.
12. Save the truststore file.
13. As user arcsight, restart the ArcSight Manager by running:
/etc/init.d/arcsight_services start manager
Select Authentication Option in ArcSight Console Setup
The authentication option on the ArcSight Console should match the authentication option that you
set on the ArcSight Manager. Run the ArcSight Console setup program and either confirm or change
the authentication on the ArcSight Console to match that of the ArcSight Manager. To do so:
1. Stop the ArcSight Console if it is running.
2. Run the ArcSight Console’s setup program from the ArcSight Console’s bin directory:
./arcsight consolesetup
3. Follow the prompts in the wizard screens by accepting all the defaults until you see the screen for
the authentication option. The choices are:
l
Password Based Authentication
l
Password Based and SSL Client Based Authentication
l
Password Based or SSL Client Based Authentication
l
SSL Client Only Authentication
4. Select the option for Password or SSL Client Based Authentication. You should also have
chosen that option when you set up the ArcSight Manager.
5. Follow the prompts in the next few screens by accepting the defaults.
6. On the Select client keystore type screen select the PKCS#11 Token option.
7. Enter the path or browse to the PKCS #11 library when prompted.
If you are using a vendor other than ActivClient, this should point to the library location for that
installation.
HPE ESM
6.9.1c
Page 69 of 94
ESM Installation Guide
Appendix C: Using PKCS
If you are using ActivClient, by default the PKCS #11 library is located in:
On 32-bit Windows:
C:\Program Files\ActivIdentity\ActivClient\acpkcs211.dll
On 64-bit Windows:
C:\Program Files (x86)\ActivIdentity\ActivClient\acpkcs211.dll
(this is the 32-bit version of the ActivClient library)
For 90Meter, always use the 32-bit library:
C:\Program Files\90meter\CACPIVMD\pkcs11\x86\LitPKCS11.dll
8. Complete the setup program by accepting all the defaults.
9. Restart any running ArcSight Consoles.
Logging in to the ArcSight Console Using PKCS#11 Token
When you start the ArcSight Console, you will see a screen with a PKCS #11 login button.
You have the option to log in using one of the following methods:
l
Username and password combination (For this option, disconnect the CAC/90Meter card.)
l
PKCS#11 Login
To log in using a PKCS#11 token, select the PKCS #11 Login option. On the ActivClient Login dialog,
enter the PIN number of your ActivClient card in the PIN text box.
Logging in to an ESM Web UI Using PKCS#11 Token
Use a supported web browser such as Firefox or Internet Explorer to connect to the ArcSight Command
Center.
1. Make sure that the PKCS#11 token is securely placed in its card reader.
2. Go to this web site: https://<hostname>:8443/.
If you are using Firefox, be sure to configure Firefox to work with ActivClient by loading the
ActivClient module. For connections using a web browser you might need to configure the browser
for some PKCS#11 providers:
a. Open Tools > Options and go to the Advanced > Certificates tab.
b. In Security Devices -select Add a new module.
c. For "ActiveIdentity" specify 32-bit dll by pointing to
C:\Program Files (x86)\ActivIdentity\ActivClient\acpkcs211.dll
For 90Meter everything is configured automatically.
d. Use the Log In button to login to the module and enter the PIN when asked. Be sure to use the
Log Out button to prevent auto-authentication.
HPE ESM
6.9.1c
Page 70 of 94
ESM Installation Guide
Appendix C: Using PKCS
e. Restart Firefox and now you can log in to the ArcSight Command Center without any
credentials.
3. You will be requested to enter your PIN.
If using Firefox, you see an exception. Click Add exception, then generate and confirm the
certificate key. When you see the User Identification Request dialog. Click OK.
4. At the ArcSight Command Center login, do not enter any user ID or password. Leave them both
blank and click Login. User authentication is resolved after you enter the PKCS#11 PIN in the dialog
that appears next.
5. Enter your PIN in the Confirmation dialog. The dialog’s title and appearance varies, depending on
the PKCS#11 token configuration.
HPE ESM
6.9.1c
Page 71 of 94
Appendix D: Installing ESM in FIPS Mode
ESM supports the Federal Information Processing Standard 140-2 (FIPS 140-2) and Suite B. You can
choose to install the product components in FIPS mode if you have the requirement to do so.
Note: When the Manager is installed in FIPS mode, all other components must also be installed in
FIPS mode.
If you are using FIPS mode, you cannot use the ArcSight Console on a Mac.
What is FIPS?
FIPS 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.
Note: To be FIPS 140-2 compliant, you need to have all components configured in the FIPS 140-2
mode. Even though an ArcSight Manager running in FIPS mode can accept connections from nonFIPS mode components, if you opt for such a mixed configuration, you will not be considered FIPS
140-2 compliant. We recommend that you run all components in FIPS mode in order to be fully FIPS
140-2 compliant.
Mozilla’s Network Security Services (NSS) is an example of FIPS certified cryptographic module. It is the
core and only cryptographic module used by ESM in FIPS mode. NSS is an open source security library
and collection of security tools. It is FIPS 140-2 compliant and validated. The NSS cryptographic module
provides a PKCS #11 interface for secure communication with ESM. You can configure NSS to use either
an internal module or the FIPS module. The FIPS module includes a single built-in certificate database
token, the "Network Security Services Database (NSS DB)" below, which handles both cryptographic
operations and the communication with the certificate and key database files.
Network Security Services Database (NSS DB)
A difference between default mode and FIPS mode is that in default mode you use the keystore and
truststore to store key pairs and certificates respectively in JKS format, whereas in FIPS mode both key
pairs and certificates are stored in NSS DB. Key pairs are stored in the .pfx format (in compliance with
PKCS #12 standard) in NSS DB. The NSS DB is located in:
HPE ESM 6.9.1c
Page 72 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
/opt/arcsight/manager/config/jetty/nssdb on the ArcSight Manager
l
<ARCSIGHT_HOME>/current/config/nssdb.client on the ArcSight Console
l
Note: The default password for the NSS DB on every component is changeit. However, we
recommend that you change this password by following the procedure in section “Changing the
Password for NSS DB” in the ESM Administrator’s Guide.
What is Suite B?
Suite B is a set of cryptographic algorithms put forth by the National Security Agency (NSA) as part of
the national cryptographic technology. While FIPS 140-2 supports sensitive but unclassified
information, FIPS with Suite B supports both unclassified information and most classified to top secret
information. In addition to AES, Suite B includes cryptographic algorithms for hashing, digital
signatures, and key exchange.
Note:
l
l
l
Not all ESM versions support the FIPS with Suite B mode. Refer to the ESM HP ArcSight ESM
Support Matrix Document available on the Protect 724 website for supported platforms for FIPS
with Suite B mode.
When the Manager is installed in FIPS with Suite B compliant mode, all components (ArcSight
Console, SmartConnectors, and Logger, if applicable) must be installed in FIPS with Suite B
compliant mode, and browser used to access ESM must be FIPS enabled.
Before installing ESM in FIPS with Suite B mode, keep in mind that pre-v4.0 Loggers will not be
able to communicate with a FIPS-enabled ArcSight Manager.
When configured to use Suite B mode, ESM supports Suite B Transitional profile. There are 2 level of
security defined in Suite B mode:
l
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
Suite B 128-bit security level, providing protection from unclassified up to secret information.
l
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
Suite B 192-bit security level, providing protection from unclassified up to top secret information.
HPE ESM
6.9.1c
Page 73 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
NSS Tools Used to Configure Components in FIPS
Mode
NSS is a cross-platform cryptographic C library and a collection of security tools. ESM comes bundled
with the following three basic NSS command line tools:
l
runcertutil - is a certificate and key management tool used to generate key pairs and import and
export certificates.
l
runmodutil - is the NSS module configuration tool. It is used to enable or disable the FIPS module
and change Keystore passwords.
l
runpk12util - is an import and export tool for PKCS #12 format key pairs (.pfx files).
See “Appendix A, Administrative Commands” in the Administrator’s Guide 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 help on any command, enter this command from a component’s bin directory:
On Windows:
arcsight.bat <command_name> -H
On Linux:
./arcsight <command_name> -H
TLS Configuration in a Nutshell
TLS configuration involves either server side authentication only or both server side and client side
authentication. Setting up client side authentication is optional. To configure ESM in FIPS mode, you
need to set up TLS configuration on the ArcSight Manager, and ArcSight Console. Use TLSv1.0 or TLS
v1.1 (TLSv1.2 is not supported due to a limitation of java/NSS in FIPS mode.)
Since TLS is based on SSL 3.0, we recommend that you have a good understanding of how SSL works.
Please read the section “Understanding SSL Authentication” in the ESM Administrator’s Guide for
details on how SSL works.
TLS and SSL require the server to have a public/private key pair and a cryptographic certificate linking
the server's identity to the public key. The certificate should be signed by an entity that the client trusts.
The clients, in turn, should be configured to 'trust' this entity. If the server and clients are controlled by
the same authority then certificates can be created locally (self-signed certificates). A more secure
approach would be to get the certificate signed by an organization that clients are pre-configured to
trust. This involves dealing with one of the many commercial Certification Authorities (CAs).
HPE ESM
6.9.1c
Page 74 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
Refer to the Administrator’s Guide for information on upgrading an existing default mode installation
into FIPS mode.
Server Side Authentication
The first step in an SSL handshake is when the server (ArcSight Manager) authenticates itself to the
ArcSight Console. This is called server side authentication. To set up TLS configuration on your
ArcSight Manager for server side authentication, you need:
l
l
A key pair in your ArcSight Manager’s NSS DB.
The ArcSight Manager’s certificate, which incorporates the public key from the key pair located in the
ArcSight Manager’s NSS DB. By default, this is a self-signed certificate.
Next, you should export the ArcSight Manager’s certificate from its NSS DB and lastly import this
certificate into the NSS DB of the clients that will be connecting to this ArcSight Manager.
Client Side Authentication
SSL 3.0 supports client side authentication, which you can optionally set up as an extra measure of
security. Client side authentication consists of the client authenticating itself to the server. In an SSL
handshake, client side authentication, if set up, takes place after the server (ArcSight Manager) has
authenticated itself to the ArcSight Console. At this point, the server requests the client to authenticate
itself.
For the ArcSight Console to authenticate itself to the ArcSight Manager, you should have the following
in the ArcSight Console’s NSS DB:
l
A key pair.
l
The ArcSight Console’s certificate, which incorporates the ArcSight Console’s public key.
If you plan to use PKCS #11 token such as the Common Access Card, you will be required to import the
token’s certificate into the ArcSight Manager’s NSS DB as the token is a client to the ArcSight Manager.
For detailed procedures on each of the steps mentioned above, refer to the section “Setting up ClientSide Authentication” in the Administrator’s Guide.
Exporting the Manager’s Certificate to Clients
This topic does not apply to ArcSight Console, which automatically imports the certificate. You are
required to have this exported certificate available when installing clients that connect to this, such as
Connectors. When installing the certificate, you import it into the clients’ NSS DB. For Connectors, the
NSS DB is <ARCSIGHT_HOME>/current/user/agent/nssdb.client. Importing the ArcSight
Manager’s certificate allows the clients to trust the ArcSight Manager.
HPE ESM
6.9.1c
Page 75 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
To export the Manager’s certificate, run the following command from the ArcSight Manager’s
/opt/arcsight/manager/bin directory:
./arcsight runcertutil -L -n mykey -r -d <ARCSIGHT_
HOME>/config/jetty/nssdb -o <absolute_path_to _Managercertificatename.cer>
Note: The -o specifies the absolute path to the location where you want the exported ArcSight
Manager’s certificate to be placed. If you do not specify the absolute path the file will be exported
to the /opt/arcsight/manager directory by default.
For example, to export the ArcSight Manager’s certificate as a file named ManagerCert.cer to
the/opt/arcsight/manager directory, run:
./arcsight runcertutil -L -n mykey -r -d <ARCSIGHT_
HOME>/config/jetty/nssdb -o /opt/arcsight/manager/ManagerCert.cer
This will export the ManagerCert.cer file, the ArcSight Manager’s certificate, in the
/opt/arcsight/manager directory.
Using PKCS #11 Token With a FIPS Mode Setup
To use a PKCS #11 Token, such as the ActivClient’s Common Access Card (CAC) or 90Meter, follow the
steps in "Setting Up to Use a PKCS#11 Provider " on page 61.
Installing ArcSight Console in FIPS Mode
Note: If you would like to set up client-side authentication on the ArcSight Console, refer to the
Administrator’s Guide for detailed steps to do so.
If you are using FIPS mode, you cannot use the ArcSight Console on a Mac.
Typically, ArcSight Console is deployed on several perimeter machines located outside the firewall which
protects the ArcSight Manager.
Refer to the ESM Product Lifecycle document available on the Protect 724 website
(https://www.protect724.hpe.com) for details on supported platforms for the ArcSight Console.
This section tells you how to install the ArcSight Console in FIPS mode only. For details on installing the
ArcSight Console in default mode, refer to the “Installing ArcSight Console” chapter, earlier in this
guide.
HPE ESM
6.9.1c
Page 76 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
In order for an ArcSight Console to communicate with a FIPS enabled ArcSight Manager, the ArcSight
Console must trust the ArcSight Manager. This trust is established by importing the ArcSight
Manager’s certificate into the ArcSight Console’s NSS DB (<ARCSIGHT_
HOME>/current/config/nssdb.client). After you configure the ArcSight Console for FIPS, it will
automatically import the ArcSight Manager’s certificate the first time you start it.
To install the ArcSight Console in FIPS mode:
1. Run the self-extracting archive file that is appropriate for your target platform.
2. Follow the prompts in the wizard screens. Refer to “Installing ArcSight Console” chapter for details
on each screen.
3. Select No, I do not want to transfer the settings in the following screen and click Next.
4. Next, you will see the following screen:
Select Run console in FIPS mode and click Next.
5. You will be reminded that once you select the FIPS mode, you will not be able to revert to the
default mode. Click Yes.
6. You will be prompted to select a cipher suite. Select the type of FIPS the ArcSight Manager uses
and click Next.
7. Next you will be prompted for the ArcSight Manager’s hostname and port. The ArcSight Manager
hostname must be the same (short name, fully qualified domain name, or IP address) as the
Common Name (CN) you used when you created the ArcSight Manager key pair.
8. Follow the prompts in the next few wizard screens (refer to the “Installing ArcSight Console”
chapter, earlier in this guide for details on any screen) until you get to the screen where you have to
select the authentication option.
Select Password Based or SSL Client Based Authentication, which also must be the option that
you had set on the ArcSight Manager when installing it.
9. If you are using SSL client-based authentication and if you plan to use a PKCS #11 token with the
ArcSight Console, select PKCS #11 Token option in the following screen. If you are using different
authentication, you do not see this screen and you can skip this step.
Enter the path or browse to the PKCS #11 library.
By default, the PKCS #11 library is located in the following directory:
On 64-bit Windows:
C:\Program Files (x86)\ActivIdentity\ActivClient\acpkcs211.dll
(this is the 32-bit version of the ActivClient library)
If you do not plan to use a PKCS #11 token with the ArcSight Console, select Client Key Store, you
will see a message reminding you to set up the client certificate after the installation completes.
After completing the Configuration Wizard, follow the procedure in the topic “Setting up ClientSide Authentication,” in the “Configuration Changes Related to FIPS” appendix of the ESM
Administrator’s Guide.
HPE ESM
6.9.1c
Page 77 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
10. Follow the prompts in the next few wizard screens to complete the ArcSight Console installation.
Refer to the “Installing ArcSight Console” chapter, earlier in this guide, for details on any screen.
When you start the ArcSight Console, you should see a message saying that the ArcSight Console is
being started in FIPS mode.
Types of Key Pairs Used in FIPS Mode
The type of key pair for FIPS 140-2 mode is the same type used in non-FIPS mode. When using the
runcertutil command, the key-type option would be -k rsa.
The type of key pair for FIPS with Suite B is different. The key depends on the level of classification you
need to accommodate. FIPS Suite B requires the use of elliptic curve cryptography so the key-type
option starts out -k ec. After that you have to specify the -q secp<bits>r1 option. The value of
<bits> is:
l
256 -- for up to secret classifications corresponding to 128-bit encryption
l
384 -- for up to top secret classifications corresponding to 192-bit encryption
1. Delete the existing Manager key pair.
If you are generating a key pair on the Manager, first delete the one that is there by default:
/opt/arcsight/manager/bin/arcsight runcertutil -D -d
/opt/arcsight/manager/config/jetty/nssdb/ -n mykey
2. Generate a new key pair.
To generate a new key pair, you might use a command like this:
./arcsight runcertutil -S -s “CN=<previous_CN>” -v <validity_in_months> -n
mykey -k ec -q secp384r1 -x -t “C,C,C” -m 1234 -d
/opt/arcsight/manager/config/jetty/nssdb
You can use secp521r1, but some browsers, such as Internet Explorer 11 (on Windows 8.1 and
Windows Server 2012) and Chrome (on any operating system), cannot use the 521-bit option. The
examples in this document use 521, but if you are using IE 11 on those OS versions or Chrome, they
do not work with FIPS Suite B. Use secp384r1 (or secp256r1).
If you use the wrong elliptic curve cryptography for a browser that cannot support it, or you make
a simple typographical error, there is no error or warning message and the Manager will not
function correctly. To correct that problem delete Manager key pair and create it again.
3. Restart the Manager. Always restart the Manager after generating a key pair.
4. Delete the old Manager certificate from each client (connectors, ArcSight Console's, and browsers).
5. Export the new Manager certificate into each client. See "Exporting the Manager’s Certificate to
Clients" on page 75. Leave the Connectors stopped. It may be preferable to deal with each
connector one at a time, rather than turning them all off at once.
6. Restart the Console and the browser after importing the new Manager certificate.
HPE ESM
6.9.1c
Page 78 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
7. In the ArcSight Console, delete each connector and then re-register it with the Manager.
8. Restart each connector.
Connecting a Default Mode ArcSight Console to a
FIPS 140-2 ArcSight Manager
To have an ArcSight Console installed in the default mode to connect to an ArcSight Manager running
in the FIPS 140-2 mode:
l
Either add server.fips.enabled=true in your console.properties file located in the
ArcSight Console’s <ARCSIGHT_HOME>/current/config directory.
Or add -Dhttps.protocols=TLSv1 to the ARCSIGHT_JVM_OPTIONS variable in the ArcSight
Console’s <ARCSIGHT_HOME>/current/bin/scripts/console.sh file.
l
Import the ArcSight Manager’s certificate into <ARCSIGHT_
HOME>/current/jre/lib/security/cacerts on the ArcSight Console. See section, “Import a
Certificate,” in the ESM Administrator’s Guide, for details on how to do this.
Note: You cannot connect a default mode ArcSight Console to an ArcSight Manager using FIPS
Suite B.
Connecting a FIPS ArcSight Console to FIPS Enabled
ArcSight Managers
This procedure should be automatic for multiple ArcSight Managers. Just make sure that each ArcSight
Manager certificate has a unique Common Name (CN) so that it’s CN does not conflict with the CN of
any existing certificate in the ArcSight Console’s nssdb.client.
If you need to import an ArcSight Manager’s certificate into the ArcSight Console’s nssdb.client
manually, refer to the ESM Administrator’s Guide for details on the procedure.
Configure Your Browser for FIPS
To connect a browser to a FIPS web server, the browser must be configured to support FIPS. Review
the documentation for your browser and follow the instructions to make it FIPS compliant before using
it for ArcSight Console online help or to connect to the ArcSight Command Center.
Make sure that all SSL protocols are turned off. For example, on Microsoft Internet Explorer (IE):
HPE ESM
6.9.1c
Page 79 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
1. Select Tools > Internet Options.
2. Select the Advanced tab.
3. Scroll down to the Security section.
4. Uncheck Use SSL 2.0 and Use SSL 3.0.
5. Check the TLS options. By default ESM uses TLS 1.0; TLSv1.2 is not supported due to a limitation
of java/NSS in FIPS mode.
Other browsers (and other versions of IE) may have different menu items or options for doing this, so
refer to your browser documentation.
When using a browser with Suite B, it matters how you generate your key pair. For information about
the encryption to use with browsers, see "Types of Key Pairs Used in FIPS Mode" on page 78.
Note: You cannot use IE or CHROME for 90Meter and CAC with FIPS Suite B (128 or 192) unless
you set up your key pairs correctly.
Installing SmartConnectors in FIPS Mode
When the ArcSight Manager is installed in FIPS mode, the SmartConnectors must also be installed in
FIPS mode. When you run the SmartConnector installation, (see the SmartConnector documentation)
select Enable FIPS Mode. Then continue until you see the screen that offers you the choice to
Continue or Exit. Select Exit and click Next. On the next screen, click Done. You have to import the
ArcSight Manager's certificate to allow the connector to trust the ArcSight Manager before adding a
new connector.
To import the 's certificate, run the following command from the connector's <ARCSIGHT_
HOME>/current/bin directory:
arcsight runcertutil -A -n <provide_an_alias_for_the_cert> -t “CT,C,C” -d
<ARCSIGHT_HOME>\current\user\agent\nssdb.client -i <absolute_path_to_
certificate_file>
Enter changeit for the password when prompted. That was the default password. If you changed it to
something else, enter that password.
Run <ARCSIGHT_HOME>\current\bin\runagentsetup -i console to resume your connector
setup. You can skip -i console to run this setup in GUI mode, but this documentation explains the
procedure for running in console (command line) mode.
1. Select Add a Connector and press Enter.
2. Select the connector to configure and press Enter to continue.
3. For each of the parameters you are shown next, you can either change the value or accept the
default value. Continue until you get to the Type of Destination parameters.
4. Select ArcSight Manager (encrypted) as the type of destination and press Enter.
HPE ESM
6.9.1c
Page 80 of 94
ESM Installation Guide
Appendix D: Installing ESM in FIPS Mode
5. Under Destination Parameters, or each of the parameters you are shown next, you can either
change the value or accept the default value. When you get to them, enter the Manager Hostname
and login credentials.
6. For the FIPS Cipher Suites parameter, choose from:
l FIPS Default
l
FIPS with Suite B128 bits
FIPS with Suite B192 bits
Press Enter to continue.
7. Enter the connector details such as the name and location, which can be any values you want.
l
8. Decide whether to install the connector as a service or leave it as a standalone application and press
Enter to Continue.
9. Exit the connector configuration wizard.
For more information on installing SmartConnectors in FIPS mode see Installing FIPS-Compliant
SmartConnectors. It is used in conjunction with the individual device SmartConnector configuration
guides for your device.
How Do I Know if My Installation is FIPS Enabled?
To figure out whether your existing installation has been installed in FIPS mode or default mode, check
the fips.enabled property in the component’s property file located as follows:
l
/opt/arcsight/manager/config/server.properties for the ArcSight Manager
l
<ARCSIGHT_HOME>/current/config/console.properties for the ArcSight Console
If FIPS mode is enabled, the property should be set to fips.enabled=true. If the component is
running in default mode, the property will be set to false.
HPE ESM
6.9.1c
Page 81 of 94
Appendix E: Locales and Encodings
ESM supports various languages: English, Japanese, traditional Chinese, simplified Chinese, French,
Russian, and Korean. Setting the Locale for any of these languages ensures that you get the
appropriate environment in terms of language settings, number format, date/time format, timezone
settings, and Daylight Saving Time setting for that country or language. This document describes the
updates to be taken into consideration when configuring ESM for a supported language.
Terminology
Some of the common terms used in this document are described below.
Character Set
A character set is a collection of characters that have been grouped together for a particular purpose.
An example of a character set is the English alphabet.
Code Point
Each character value within a code set is referred to as a code point.
Code Set
Each character in a character set is assigned a unique value. Collectively, these values are known as a
code set.
Encoding
Encoding specifies how each character's code point is stored in memory or disk files.
Internationalization
Internationalization is the process of designing an application so that it can be adapted to various
languages and regions without further engineering changes.
HPE ESM 6.9.1c
Page 82 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
Locale
Locale refers to the region where you are running ArcSight ESM. A locale can include language, number
format, date-time format, and other settings.
Localization
Localization is the process of adding language specific files to an internationalized application so that
the application supports that language.
Unicode
Unicode is a universal character set that assigns a unique code point to characters from all major
languages of the world.
UTF-8
The version of Unicode supported by ESM.
Before You Install a Localized Version of ESM
Note: The ArcSight Manager and Console should be configured with the same locale.
By default, all communication between ArcSight components is done using UTF-8 character encoding.
Even though ESM supports only UTF-8 internally, if your Connector receives events in UTF-16, for
example, the events are still stored correctly since these events get converted to UTF-8 by the
Connector before they are passed on to the Manager.
ArcSight Console and Manager
For best results, install the ArcSight Console on an operating system that is set to the same locale as the
Manager. During startup, the ArcSight Console and the Manager automatically detect and use the
locale from the operating system.
HPE ESM
6.9.1c
Page 83 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
ArcSight SmartConnectors
If a device is configured to use a language-specific encoding (not Unicode), the Connector receiving
events from this device should be configured to use the same encoding as the device.
Setting the Encoding for Selected SmartConnectors
For some connectors you can set the encoding to a character set corresponding to your Locale. Check
the SmartConnector Configuration Guide for that connector for instructions on configuring encodings.
Such connectors support all character sets supported by Java.
Change the encoding to match the log files' encoding only if the log files use an encoding other
than the default.
Connectors that do not specifically support an encoding specification use the default encoding of the
operating system on which they reside.
Localizing Date Formats
If your connector receives logs that contain timestamps or date formats in a non-English language or
locale (for example, "mai 24, 2015 12:56:07.615" where "mai" is German for May), configure the
agent.parser.locale.name property in the agent.properties file. This file is located in the
<ARCSIGHT_HOME>/current/user/agent directory.
Set the agent.parser.locale.name property to the value that corresponds to the Connector's
locale. By default, this property is set to en_US. Refer to the table in "List of Possible Values" below for
possible values for this property.
List of Possible Values
agent.parser.locale.name Values
The table below lists the possible values for this property.
HPE ESM
Values
Language
ar
Arabic
ar_AE
Arabic
6.9.1c
Country
Variant
United Arab
Page 84 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
Values
Language
Country
Variant
Emirates
HPE ESM
ar_BH
Arabic
Bahrain
ar_DZ
Arabic
Algeria
ar_EG
Arabic
Egypt
ar_IQ
Arabic
Iraq
ar_JO
Arabic
Jordan
ar_KW
Arabic
Kuwait
ar_LB
Arabic
Lebanon
ar_LY
Arabic
Libya
ar_MA
Arabic
Morocco
ar_OM
Arabic
Oman
ar_QA
Arabic
Qatar
ar_SA
Arabic
Saudi Arabia
ar_SD
Arabic
Sudan
ar_SY
Arabic
Syria
ar_TN
Arabic
Tunisia
ar_YE
Arabic
Yemen
be
Belarusian
be_BY
Belarusian
bg
Bulgarian
bg_BG
Bulgarian
ca
Catalan
6.9.1c
Belarus
Bulgaria
Page 85 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
HPE ESM
Values
Language
Country
ca_ES
Catalan
Spain
cs
Czech
cs_CZ
Czech
da
Danish
da_DK
Danish
de
German
de_AT
German
Austria
de_CH
German
Switzerland
de_DE
German
Germany
de_LU
German
Luxembourg
el
Greek
el_GR
Greek
en
English
en_AU
English
Australia
en_CA
English
Canada
en_GB
English
United Kingdom
en_IE
English
Ireland
en_IN
English
India
en_NZ
English
New Zealand
en_US
English
United States
en_ZA
English
South Africa
es
Spanish
6.9.1c
Variant
Czech Republic
Denmark
Greece
Page 86 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
HPE ESM
Values
Language
Country
es_AR
Spanish
Argentina
es_BO
Spanish
Bolivia
es_CL
Spanish
Chile
es_CO
Spanish
Columbia
es_CR
Spanish
Costa Rica
es_DO
Spanish
Dominican
Republic
es_EC
Spanish
Ecuador
es_ES
Spanish
Spain
es_GT
Spanish
Guatemala
es_HN
Spanish
Honduras
es_MX
Spanish
Mexico
es_NI
Spanish
Nicaragua
es_PA
Spanish
Panama
es_PE
Spanish
Peru
es_PR
Spanish
Puerto Rico
es_PY
Spanish
Paraguay
es_SV
Spanish
El Salvador
es_UY
Spanish
Uruguay
es_VE
Spanish
Venezuela
et
Estonian
et_EE
Estonian
fi
Finnish
6.9.1c
Variant
Estonia
Page 87 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
HPE ESM
Values
Language
Country
fi_FI
Finnish
Finland
fr
French
fr_BE
French
Belgium
fr_CA
French
Canada
fr_CH
French
Switzerland
fr_FR
French
France
fr_LU
French
Luxembourg
hi_IN
Hindi
India
hr
Croatian
hr_HR
Croatian
hu
Hungarian
hu_HU
Hungarian
is
Icelandic
is_IS
Icelandic
it
Italian
it_CH
Italian
Switzerland
it_IT
Italian
Italy
iw
Hebrew
iw_IL
Hebrew
ja
Japanese
ja_JP
Japanese
ko
Korean
6.9.1c
Variant
Croatia
Hungary
Iceland
Israel
Japan
Page 88 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
HPE ESM
Values
Language
Country
ko_KR
Korean
Korea
lt
Lithuanian
lt_LT
Lithuanian
lv
Latvian
lv_LV
Latvian
mk
Macedonian
mk_MK
Macedonian
nl
Dutch
nl_BE
Dutch
Belgium
nl_NL
Dutch
Netherlands
no
Norwegian
no_NO
Norwegian
Norway
no_NO_NY
Norwegian
Norway
pl
Polish
pl_PL
Polish
pt
Portuguese
pt_BR
Portuguese
Brazil
pt_PT
Portuguese
Portugal
ro
Romanian
ro_RO
Romanian
ru
Russian
ru_RU
Russian
6.9.1c
Variant
Lithuania
Latvia
Macedonia
Nynorsk
Poland
Romania
Russia
Page 89 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
HPE ESM
Values
Language
sk
Slovak
sk_SK
Slovak
sl
Slovanian
sl_SI
Slovanian
sq
Albanian
sq_AL
Albanian
sv
Swedish
sv_SE
Swedish
th
Thai
th_TH
Thai
Thailand
th_TH_TH
Thai
Thailand
tr
Turkish
tr_TR
Turkish
uk
Ukranian
uk_UA
Ukranian
vi
Vietnamese
vi_VN
Vietnamese
zh
Chinese
zh_CN
Chinese
China
zh_HK
Chinese
Hong Kong
zh_TW
Chinese
Taiwan
6.9.1c
Country
Variant
Slovakia
Slovania
Albania
Sweden
TH
Turkey
Ukraine
Vietnam
Page 90 of 94
ESM Installation Guide
Appendix E: Locales and Encodings
Key-Value Parsers for Localized Devices
Some localized devices not only send localized values but also localized keys in event messages. In such
a case, additional processing may be needed to translate the keys to English for the event messages to
be properly parsed. For example, assume that the content of a key-value parser is:
event.destinationUserName=User
...and the received event message is:
User=
...where
is Korean for KIM.
In that case, the parser as it is works fine since double byte is supported already.
If the received event message is:
...where
is Korean for User, then additional mapping is needed to translate
to User.
If you encounter a need for a localized device, please contact Customer Support using the HP SSO
website.
HPE ESM
6.9.1c
Page 91 of 94
ESM Installation Guide
Appendix F: Restore Appliance Factory Settings
Appendix F: Restore Appliance Factory
Settings
You can restore the appliance to its original factory settings using the built-in System Restore utility.
CAUTION:Factory reset irrevocably deletes all event and configuration data.
Use the following procedure to restore the appliance to its original, factory settings:
1. Attach a keyboard, monitor, and mouse directly to the appliance and open an operating system
console session.
2. Reboot the appliance.
3. After a few minutes, when the Linux boot menu appears, use the down arrow key to select System
Restore <build_num> from the menu that appears, then press Enter.
System Restore automatically detects and displays the archive image.
The image is named following this pattern:
YYYY-MM-DD_<model>_<build_num>.ari
where YYYY-MM-DD is the date, <model> is the appliance model, and <build_num> is the build
number of the image being restored. If you encounter any issues with the image, contact Customer
Support.
4. Press F10 (VERIFY) to check the archive for damage before performing the restore.
5. Press F1 (AUTOSELECT) to automatically map the source image.
6. Press F2 (RESTORE) to begin the restore process.
CAUTION: Do not interrupt or power-down the appliance during the restore process.
Interrupting the restore process may force the system into a state from which it cannot be
recovered.
7. When the restore process is completed, press F12 to reboot the appliance.
HPE ESM
6.9.1c
Page 92 of 94
ESM Installation Guide
Appendix F: Restore Appliance Factory Settings
HPE ESM 6.9.1c
Page 93 of 94
Send Documentation Feedback
If you have comments about this document, you can contact the documentation team by email. If an
email client is configured on this system, click the link above and an email window opens with the
following information in the subject line:
Feedback on ESM Installation Guide (ESM 6.9.1c)
Just add your feedback to the email and click send.
If no email client is available, copy the information above to a new message in a web mail client, and send
your feedback to arc-doc@hpe.com.
We appreciate your feedback!
HPE ESM 6.9.1c
Page 94 of 94
Download PDF
Similar pages