File tree Expand file tree Collapse file tree 1 file changed +3
-5
lines changed
articles/defender-for-iot/organizations/integrations Expand file tree Collapse file tree 1 file changed +3
-5
lines changed Original file line number Diff line number Diff line change @@ -13,14 +13,14 @@ This article describes how to send Microsoft Defender for IoT alerts to LogRhyth
13
13
14
14
Before you begin, make sure that you have the following prerequisites:
15
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.
16
+ - Access to a Defender for IoT OT sensor as an Admin user.
19
17
20
18
## Create a Defender for IoT forwarding rule
21
19
22
20
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
21
22
+ For more information, see [ Forward alert information] ( ../how-to-forward-alert-information-to-partners.md ) .
23
+
24
24
1 . Sign in to your OT sensor console and select ** Forwarding** on the left.
25
25
26
26
1 . Enter a meaningful name for your rule, and then define your rule details, including:
@@ -29,8 +29,6 @@ This procedure describes how to create a forwarding rule from your OT sensor to
29
29
- The protocols you want to include in the rule.
30
30
- The traffic you want to include in the rule.
31
31
32
- For more information, see [ Forward alert information] ( ../how-to-forward-alert-information-to-partners.md ) .
33
-
34
32
1 . In the ** Actions** area, define the following values:
35
33
36
34
- ** Server** : Select a SYSLOG server option, such as ** SYSLOG Server (LEEF format)
You can’t perform that action at this time.
0 commit comments