Mic Misp Config Guide
Mic Misp Config Guide
Legal Notices
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Copyright Notice
Copyright 2016-2024 Open Text.
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be
set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or
omissions contained herein. The information contained herein is subject to change without notice.
Trademark Notices
“OpenText” and other Open Text trademarks and service marks are the property of Open Text or its affiliates. All other
trademarks or service marks are the property of their respective owners.
Documentation Updates
The title page of this document contains the following identifying information:
l Software Version number
l Document Release Date, which changes each time the document is updated
l Software Release Date, which indicates the release date of this version of the software
To check for recent updates or to verify that you are using the most recent edition of a document, go to:
https://www.microfocus.com/support-and-services/documentation
Support
Contact Information
Phone A list of phone numbers is available on the Technical Support
Page: https://softwaresupport.softwaregrp.com/support-contact-information
Page 3 of 15
MISP - Open Source Threat Intelligence and Sharing Platform Solution
Note: The MISP Connector will be deprecated for the ArcSight 23.1 release, the first release of
2023. Customers using MISP today are strongly advised to migrate to the Galaxy Threat
Acceleration Program (GTAP), which includes support for MISP and premium intelligence feeds.
For more information, see the Configuration Guide for CyberRes Galaxy Threat Acceleration
Program SmartConnector.
Model Import Connector for MISP (Open Source Threat Intelligence and Page 4 of 15
Product Overview
The Micro Focus Model Import Connector for MISP (Open Source Threat Intelligence and
Sharing Platform Solution) uses Threat Intelligence to detect Advance Persistent Threats,
Ransomware, Phishing, Botnets and Cryptojacking. as well as provide context to security
events. The Model Import Connector for MISP (Open Source Threat Intelligence and Sharing
Platform Solution) is a component which retrieves Threat Intelligence from the MISP Open
Source Threat Intelligence and Sharing Platform Solution) instance, processes this data, and
forwards it to ArcSight ESM.
Note: When installing the connector as a Linux daemon, run the following command as
root and ensure the -u parameter is a non-root user:
$ARCSIGHT_HOME/current/bin/arcsight agentsvc -i -u user -sn <service_name>
Note: Use a non-root account to install the Micro Focus Model Import Connector for MISP (Open
Source Threat Intelligence and Sharing Platform Solution).
To install the OpenText Model Import Connector for MISP (Open Source Threat
Intelligence and Sharing Platform Solution)
1. Download the Model Import Connector for MISP (Open Source Threat Intelligence and
Sharing Platform Solution) installation executable from entitlement.microfocus.com
2. Start the connector installer by running the executable.
Note: The OpenText Model Import Connector for MISP (Open Source Threat Intelligence
and Sharing Platform Solution) installation requires additional steps after the installation
wizard has finished. See step 14 of this procedure and subsequent steps for details.
Follow the installation wizard through the following folder selection tasks and installation
of the core connector software:
l Introduction
l Choose Install Folder
l Choose Shortcut Folder
l Pre-Installation Summary
l Installing
3. Select Add a Connector.
4. OpenText Model Import Connector for MISP (Open Source Threat Intelligence and
Sharing Platform Solution) is already selected. Click Next.
5. Enter the required parameters to configure the connector, then click Next.
If you are installing the MISP connector in FIPS mode:
a. Run the connector install up to the connector framework step and cancel the
installation.
The connector install may be resumed using the runagentsetup script.
b. Export the MISP Instance certificate from the browser as a DER encoded binary x.509
(.CER) file.
c. Import the MISP Instance exported certificate into the connector framework FIPS
keystore, using a command similar to the example below (run the command from the
connector current directory):
./jre/bin/keytool -importcert -file /opt/certificate.cer -keystore
$ARCSIGHT_HOME/current/user/agent/fips/bcfips_ks -storepass changeit -
storetype BCFKS -providername BCFIPS -providerclass
org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath
$ARCSIGHT_HOME/current/lib/agent/fips/bc-fips-1.0.2.jar -J-
Djava.security.egd=file:/dev/urandom -alias mispInstance
Proxy Host(https) Use this field and the following three fields only if you need the
connector to use a proxy to access the Internet.
Proceed with the proxy configuration: Enter the proxy host IP address.
Proxy User Name Enter the proxy user name. This value is populated when the proxy
requires an authentication.
Note: If you specify a proxy user name, you must also specify a proxy
password.
Proxy Password Enter the password of the proxy user. This value is populated when the
proxy requires an authentication and if you have specified a proxy user
name.
MISP URL Enter the Model Import Connector for MISP ( Open Source Threat
Intelligence and Sharing Platform Solution) instance url.
Enforce Warning List Remove any attributes from the result that would cause a hit on a
warning list entry.
Parameter Description
Manager Host Name Enter the name or IP address of the host on which the Manager is installed.
Manager Port Enter the network port from which the Manager is accepting requests.
The default port is 8443.
User Name Enter a valid ArcSight user name to log in to configure the SmartConnector.
This is the same user name you created during the Manager installation.
8. Enter a Name for the connector and provide other information identifying the connector's
use in your environment. Click Next.
9. Select whether to import a certificate.
10. Review the Add connector Summary and click Next. If the summary is incorrect, click
Previous to make changes.
The wizard now prompts you to choose whether you want to run the connector as a stand-
alone process or as a service. Choose either Install as a service or Leave as a standalone
application. Click Next.
11. To close the installation wizard, choose Exit and click Next. There are further installation
steps after you close the wizard. Be sure to continue with the subsequent installation
steps.
12. Increase the java heap memory for the connector by doing the following (ARCSIGHT_
HOME represents the name of the directory where the connector is installed):
a. If you running the connector as a Windows service or Linux daemon , set the heap size
in the following file:~../current/user/agent.wrapper.conf
Set the following parameters:
#Initial Java Heap Size (in MB)
wrapper.java.initmemory=1024
#Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=2048
b. If you are going to run the connector as Standalone mode:
i. For Linux - create the following shell script and be sure it is executable:
~/ARCSIGHT_HOME/current/user/agent/setmem.sh
Note: If a user that does not have administrator privileges is used, the import will fail.
Running Connectors
Connectors can be installed and run in standalone mode, on Windows platforms as a Windows
service, or on UNIX platforms as a UNIX daemon, depending upon the platform supported. On
Windows platforms, connectors also can be run using shortcuts and optional Start menu
entries.
If installed standalone, the connector must be started manually, and is not automatically active
when a host is restarted. If installed as a service or daemon, the connector runs automatically
when the host is restarted. For information about connectors running as services or daemons,
see the ArcSight SmartConnector User's Guide, Chapter 3, Installing SmartConnectors, in the
section “Running SmartConnectors”.
For connectors installed as standalone mode, to run the connector on a particular host, open a
command window, go to $ARCSIGHT_HOME\current\bin and run: ./arcsight agents
To view the connector log, read the file:
For Windows - $ARCSIGHT_HOME\current\logs\agent.log
For Linux - ~/ARCSIGHT_HOME/current/logs/agent.log
To stop the connector, enter Ctrl+C in the command window.
Note: By default, the connector collects events starting one month prior to the installation day.
This parameter can be changed by modifying the start.date field in the
../current/user/agent/agent.properties file. The format of the field is YYYY-MM-DD. The
connector can only collect up to 12 months from the installation date. If the start.date set, is a
period longer than 12 months, the default time of one month will be used. The MISP Instance
timezone is defined in the PHP.ini file on the MISP Instance host.
Note: Data import needs to be started only once from the ArcSight Console. Unless it is stopped
from the ArcSight Console, there is no need to restart the data import.
To start and stop import for the Model Import Connector for MISP (Open Source
Threat Intelligence and Sharing Platform Solution):
1. Select the Micro Focus Model Import Connector for MISP (Open Source Threat
Intelligence and Sharing Platform Solution) and right-click.
2. Select Send Command > Model Import Connector > Start or Stop.
Administrative Tasks - Open Source Threat Intelligence and Sharing Platform Page 11 of 15
MISP - Open Source Threat Intelligence and Sharing Platform Solution
To increase or decrease this time interval, you can add the buildmodeldelay property to the
file agent.properties (located at $ARCSIGHT_HOME\current\user\agent). The property
buildmodeldelay is expressed in milliseconds.
For example, the following property sets the time interval to 10 seconds:
agent.component[35].buildmodeldelay=10000
Connector Upgrade
Perform the following steps to upgrade the Micro Focus Model Import Connector for MISP
(Open Source Threat Intelligence and Sharing Platform Solution):
1. Stop the connector.
2. Run the connector installer.
3. Select the location of the connector that you want to upgrade.
4. Select the option to continue and upgrade the connector.
5. The upgraded connector is installed in the $ARCSIGHT_HOME\current folder.
6. The original installation folder is renamed by prefacing characters.
7. Run the runagentsetup.exe file.
8. Specify your ESM account credentials, when prompted.
The connector upgrade completes successfully.
Troubleshooting
This section includes the following troubleshooting information:
Publication Status
Released: NOT RELEASED
Troubleshooting Page 14 of 15
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 computer, click the link above and an email
window opens with the following information in the subject line:
Feedback on MISP - Open Source Threat Intelligence and Sharing Platform Solution (Model
Import Connector 8.4.0)
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 [email protected].
We appreciate your feedback!