Skip to content

Commit b288df7

Browse files
authored
Merge pull request #206674 from batamig/arcsight
2 parents 1f40370 + 563c6a2 commit b288df7

File tree

3 files changed

+60
-0
lines changed

3 files changed

+60
-0
lines changed

articles/defender-for-iot/organizations/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -106,6 +106,8 @@
106106
items:
107107
- name: Overview
108108
href: integrate-overview.md
109+
- name: ArcSight
110+
href: integrations/arcsight.md
109111
- name: Integrate ClearPass
110112
href: tutorial-clearpass.md
111113
- name: Integrate CyberArk

articles/defender-for-iot/organizations/integrate-overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,7 @@ The following table lists available integrations for Microsoft Defender for IoT,
1616

1717
|Partner service |Description | Learn more |
1818
|---------|---------|---------|
19+
| **ArcSight** | Forward Defender for IoT alerts to ArcSight. | [Integrate ArcSight with Microsoft Defender for IoT](integrations/arcsight.md) |
1920
|**Aruba ClearPass** | Share Defender for IoT data with ClearPass Security Exchange and update the ClearPass Policy Manager Endpoint Database with Defender for IoT data. | [Integrate ClearPass with Microsoft Defender for IoT](tutorial-clearpass.md) |
2021
|**CyberArk** | Send CyberArk PSM syslog data on remote sessions and verification failures to Defender for IoT for data correlation. | [Integrate CyberArk with Microsoft Defender for IoT](tutorial-cyberark.md) |
2122
|**Forescout** | Automate actions in Forescout based on activity detected by Defender for IoT, and correlate Defender for IoT data with other *Forescout eyeExtended* modules that oversee monitoring, incident management, and device control. | [Integrate Forescout with Microsoft Defender for IoT](tutorial-forescout.md) |
Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
---
2+
title: Integrate ArcSight with Microsoft Defender for IoT
3+
description: Learn how to send Microsoft Defender for IoT alerts to ArcSight.
4+
ms.topic: how-to
5+
ms.date: 08/02/2022
6+
---
7+
8+
# Integrate ArcSight with Microsoft Defender for IoT
9+
10+
This article describes how to send Microsoft Defender for IoT alerts to ArcSight. Integrating Defender for IoT with ArcSight provides visibility into the security and resiliency of OT networks and a unified approach to IT and OT security.
11+
12+
## Prerequisites
13+
14+
Before you begin, make sure that you have the following prerequisites:
15+
16+
- Access to a Defender for IoT OT sensor as an Admin user.
17+
18+
## Configure the ArcSight receiver type
19+
20+
To configure your ArcSight server settings so that it can receive Defender for IoT alert information:
21+
22+
1. Sign in to your ArcSight server.
23+
1. Configure your receiver type as a **CEF UDP Receiver**.
24+
25+
For more information, see the [ArcSight SmartConnectors Documentation](https://www.microfocus.com/documentation/arcsight/arcsight-smartconnectors/#gsc.tab=0).
26+
27+
## Create a Defender for IoT forwarding rule
28+
29+
This procedure describes how to create a forwarding rule from your OT sensor to send Defender for IoT alerts from that sensor to ArcSight.
30+
31+
For more information, see [Forward alert information](../how-to-forward-alert-information-to-partners.md).
32+
33+
1. Sign in to your OT sensor console and select **Forwarding** on the left.
34+
35+
1. Enter a meaningful name for your rule, and then define your rule details, including:
36+
37+
- The minimal alert level. For example, if you select Minor, you are notified about all minor, major and critical incidents.
38+
- The protocols you want to include in the rule.
39+
- The traffic you want to include in the rule.
40+
41+
1. In the **Actions** area, define the following values:
42+
43+
- **Server**: Select **ArcSight**
44+
- **Host**: The ArcSight server address
45+
- **Port**: The ArcSight server port
46+
- **Timezone**: The timezone of the ArcSight server
47+
48+
1. Select **Save** to save your forwarding rule.
49+
50+
## Next steps
51+
52+
For more information, see:
53+
54+
- [Integrations with partner services](../integrate-overview.md)
55+
- [Forward alert information](../how-to-forward-alert-information-to-partners.md)
56+
- [Manage individual sensors](../how-to-manage-individual-sensors.md)
57+

0 commit comments

Comments
 (0)