ArcSight Smart Connectors
ArcSight Smart Connectors
Student Guide
Use of this material to deliver training without prior written permission from Micro Focus is prohibited.
SmartConnectors
Objectives
- ArcSight Connectors normalize and forward collected events from many different types of
devices to the ArcSight Manager over TCP port 8443
- Performance impact of the ArcSight Connector depends on the type of ArcSight Connector
- ArcSight Connectors need not have the same release version as the ArcSight Manager
- Multiple Connectors can be installed on a single server or be installed and managed by the
ArcSight Management Center or Connector Appliance
- Upgrade can be managed remotely or from the local ESM Console using a Connector .aup
file
What is a connector?
▪ Interface to objects on network
▪ Generate event data
▪ Normalize data
▪ SmartConnectors
- Execute commands like telling a scanner to run a scan
- Lookup IP address, host names
What is normalization?
▪ Parse data to pull out values from events
▪ Populate fields in schema
SmartConnector functions
▪ Collect data from source device
▪ Filter out data not needed
▪ Parse individual events
▪ Normalize into common schema
▪ Aggregate events
▪ Categorize events
▪ Pass events to ESM Manager after processing
▪ Can issue commands to devices
Asset Import
SmartConnector
Firewall Events
Events
ArcSight
Smartconnector ESM Console
NEW YORK
Syslog ArcSight ESM
Manager & CORRE,
ArcSight San Francisco
Smartconnector
SmartConnector Functions
1. Collects
- Active - polling
- Passive - listener
2. Normalizes – parse and map raw events into Common Event Format (CEF)
- Zone Tagging – add for each IP (Zone Name)
- Categorization – add Category field values – based Device Event Class ID
- Translates Time Zones - GMT
- Map Device Severity to Agent Severity for Threat Priority Calculation
- Customer (optional) – add for each record
- Other Options – Filter, Aggregate, Turbo Mode, DSM
3. Forwards or Cache/Forwards – 70 / 30 Cache Flush
- Cache – when cannot send to a destination – one cache per destination
- Multiple Destinations – two or more in parallel
- Failover Destination – one only
SmartConnectors by Task
10
11
12
Connector receives
events from Events are sent to
third party device the Destination
13
Cache
Cache
Cache Concepts:
– All events in cache - already filtered and/or aggregated
– One Cache per transport destination
– Cache Flush - 70% live events and 30% cached events
– Cache Overflow –
– Maximum exceeded
15
– First In First Out (FIFO) - drops 20MB of events at a time
16
SmartConnector Platforms
17
Platform File
Linux ArcSight-w.x.y.nnnn.z-Connector-Linux.bin
ArcSight-w.x.y.nnnn.z-Connector-Linux64.bin
Microsoft Windows ArcSight-w.x.y.nnnn.z-Connector-Win.exe
ArcSight-w.x.y.nnnn.z-Connector-Win64.exe
Solaris ArcSight-w.x.y.nnnn.z-Connector-Solaris.bin
ArcSight-w.x.y.nnnn.z-Connector-SolarisIA.bin
AIX ArcSight-w.x.y.nnnn.z-Connector-AIX.bin
ArcSight Update Pack ArcSight-w.x.y.nnnn.z-Connectors.aup
ArcSight-w.x.y.nnnn.z-opensource.tgz
Configuration Guides SmartConnectorConfigGuides-w.x.y.nnnn.zip
Release Notes SmartConnectorReleaseNotes-w.x.y.nnnn.pdf
18
19
20
21
22
23
24
25
Module Summary
26
Learning Check
1. To invoke the ArcSight SmartConnector Configuration Wizard, run which command from the
Connector directory:
a. arcsight wizardsetup –w
b. arcsight setup –i
c. arcsight connector –w
d. arcsight connectorsetup –w
2. True or False. Upgrading Connectors can be accomplished through the ESM Console.
27
Learning Check
7. True or False. The AUP Master Destination flag should be set to “true” for only one
ESM destination at a time.
28
Learning Check
2. Status
c. ./arcsight connectors
3. Install as Windows Service
d. ./arcsight connectorup
4. Modify any parameters
30