Skip to content

Commit a5e442a

Browse files
committed
amit's comments
1 parent 00e4d79 commit a5e442a

File tree

1 file changed

+3
-5
lines changed
  • articles/defender-for-iot/organizations/integrations

1 file changed

+3
-5
lines changed

articles/defender-for-iot/organizations/integrations/logrhythm.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -13,14 +13,14 @@ This article describes how to send Microsoft Defender for IoT alerts to LogRhyth
1313

1414
Before you begin, make sure that you have the following prerequisites:
1515

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.
1917

2018
## Create a Defender for IoT forwarding rule
2119

2220
This procedure describes how to create a forwarding rule from your OT sensor to send Defender for IoT alerts from that sensor to LogRhythm.
2321

22+
For more information, see [Forward alert information](../how-to-forward-alert-information-to-partners.md).
23+
2424
1. Sign in to your OT sensor console and select **Forwarding** on the left.
2525

2626
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
2929
- The protocols you want to include in the rule.
3030
- The traffic you want to include in the rule.
3131

32-
For more information, see [Forward alert information](../how-to-forward-alert-information-to-partners.md).
33-
3432
1. In the **Actions** area, define the following values:
3533

3634
- **Server**: Select a SYSLOG server option, such as **SYSLOG Server (LEEF format)

0 commit comments

Comments
 (0)