Skip to content

Commit c5127a7

Browse files
committed
logrhythm draft
1 parent 6d9561d commit c5127a7

File tree

3 files changed

+57
-0
lines changed

3 files changed

+57
-0
lines changed

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,8 @@
114114
href: tutorial-forescout.md
115115
- name: Integrate Fortinet
116116
href: tutorial-fortinet.md
117+
- name: LogRhythm
118+
href: integrations/logrhythm.md
117119
- name: Integrate Palo Alto
118120
href: tutorial-palo-alto.md
119121
- name: Integrate Qradar

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

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,7 @@ The following table lists available integrations for Microsoft Defender for IoT,
2020
|**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) |
2121
|**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) |
2222
|**Fortinet** | Send Defender for IoT data to Fortinet services for: <br><br>- Enhanced network visibility in FortiSIEM<br>- Extra abilities in FortiGate to stop anomalous behavior | [Integrate Fortinet with Microsoft Defender for IoT](tutorial-fortinet.md) |
23+
| **LogRhythm** | Forward Defender for IoT alerts to LogRhythm. | [Integrate LogRhythm with Microsoft Defender for IoT](integrations/logrhythm.md) |
2324
|**Palo Alto** |Use Defender for IoT data to block critical threats with Palo Alto firewalls, either with automatic blocking or with blocking recommendations. | [Integrate Palo-Alto with Microsoft Defender for IoT](tutorial-palo-alto.md) |
2425
|**QRadar** |Forward Defender for IoT alerts to IBM QRadar. | [Integrate Qradar with Microsoft Defender for IoT](tutorial-qradar.md) |
2526
|**ServiceNow** | View Defender for IoT device detections, attributes, and connections in ServiceNow. | [Integrate ServiceNow with Microsoft Defender for IoT](tutorial-servicenow.md) |
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
title: Integrate LogRhythm with Microsoft Defender for IoT
3+
description: Learn how to send Microsoft Defender for IoT alerts to ALogRhythmrcSight.
4+
ms.topic: how-to
5+
ms.date: 08/02/2022
6+
---
7+
8+
# Integrate LogRhythm with Microsoft Defender for IoT
9+
10+
This article describes how to send Microsoft Defender for IoT alerts to LogRhythm. Integrating Defender for IoT with LogRhythm 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, version TBD or higher. Make sure that you can sign in as a TBD user.
17+
18+
- Access to an LogRhythm server as a TBD user.
19+
20+
## Create a Defender for IoT forwarding rule
21+
22+
This procedure describes how to create a forwarding rule from your OT sensor to send Defender for IoT alerts from that sensor to LogRhythm.
23+
24+
1. Sign in to your OT sensor console and select **Forwarding** on the left.
25+
26+
1. Enter a meaningful name for your rule, and then define your rule details, including:
27+
28+
- The minimal alert level. For example, if you select Minor, you are notified about all minor, major and critical incidents.
29+
- The protocols you want to include in the rule.
30+
- The traffic you want to include in the rule.
31+
32+
For more information, see [Forward alert information](../how-to-forward-alert-information-to-partners.md).
33+
34+
1. In the **Actions** area, define the following values:
35+
36+
- **Server**: Select a SYSLOG server option, such as **SYSLOG Server (LEEF format)
37+
- **Host**: The IP or hostname of your LogRhythm collector
38+
- **Port**: Enter **514**
39+
- **Timezone**: Enter your timezone
40+
41+
1. Select **Save** to save your forwarding rule.
42+
43+
## Configure LogRhythm to collect logs
44+
45+
After configuring a forwarding rule from your OT sensor console, configure LogRhythm to collect your Defender for IoT logs.
46+
47+
For more information, see the [LogRhythm documentation](https://docs.logrhythm.com/docs/devices/syslog-log-sources).
48+
49+
## Next steps
50+
51+
For more information, see:
52+
53+
- [Integrations with partner services](../integrate-overview.md)
54+
- [Forward alert information](../how-to-forward-alert-information-to-partners.md)

0 commit comments

Comments
 (0)