|
| 1 | +--- |
| 2 | +title: How to connect on-premises Defender for IoT resources to Microsoft Sentinel |
| 3 | +description: Learn how to stream data into Microsoft Sentinel from an on-premises and locally-managed Microsoft Defender for IoT OT network sensor or an on-premises management console. |
| 4 | +ms.topic: how-to #Required; leave this attribute/value as-is. |
| 5 | +ms.date: 12/26/2022 |
| 6 | +ms.custom: template-how-to-pattern #Required; leave this attribute/value as-is. |
| 7 | +--- |
| 8 | + |
| 9 | +# Connect on-premises OT network sensors to Microsoft Sentinel |
| 10 | + |
| 11 | +You can [stream Microsoft Defender for IoT data into Microsoft Sentinel](../iot-solution.md) via the Azure portal, for any data coming from cloud-connected OT network sensors. |
| 12 | + |
| 13 | +However, if you're working either in a hybrid environment, or completely on-premises, you might want to stream data in from your locally-managed sensors to Microsoft Sentinel. To do this, create forwarding rules on either your OT network sensor, or for multiple sensors from an on-premises management console. |
| 14 | + |
| 15 | +Stream data into Microsoft Sentinel whenever you want to use Microsoft Sentinel's advanced threat hunting, security analytics, and automation features when responding to security incidents and threats across your network. For more information, see [Microsoft Sentinel documentation](/azure/sentinel/). |
| 16 | + |
| 17 | +## Prerequisites |
| 18 | + |
| 19 | +Before you start, make sure that you have the following prerequisites as needed: |
| 20 | + |
| 21 | +- Access to the OT network sensor or on-premises management console as an **Admin** user. For more information, see [On-premises users and roles for OT monitoring with Defender for IoT](../roles-on-premises.md). |
| 22 | + |
| 23 | +- A proxy machine prepared to send data to Microsoft Sentinel. For more information, see [Get CEF-formatted logs from your device or appliance into Microsoft Sentinel](/azure/sentinel/connect-common-event-format). |
| 24 | + |
| 25 | +- If you want to encrypt the data you send to Microsoft Sentinel using TLS, make sure to generate a valid TLS certificate from the proxy server to use in your forwarding alert rule. |
| 26 | + |
| 27 | + |
| 28 | +## Set up forwarding alert rules |
| 29 | + |
| 30 | +1. Sign into your OT network sensor or on-premises management console and create a forwarding rule. For more information, see [Forward on-premises OT alert information](../how-to-forward-alert-information-to-partners.md). |
| 31 | + |
| 32 | +1. When creating your forwarding rule, make sure to select **Microsoft Sentinel** as the **Server** value. For example, on the OT sensor: |
| 33 | + |
| 34 | + :::image type="content" source="../media/integration-on-premises-sentinel/sensor-sentinel.png" alt-text="Screenshot of the Microsoft Sentinel option from the OT sensor." lightbox="../media/integration-on-premises-sentinel/sensor-sentinel.png"::: |
| 35 | + |
| 36 | +1. If you're using TLS encryption, make sure to select **Enable encryption** and upload your certificate and key files. |
| 37 | + |
| 38 | +Select **Save** when you're done. Make sure to test the rule to make sure that it works as expected. |
| 39 | + |
| 40 | +> [!IMPORTANT] |
| 41 | +> To forward alert details to multiple Microsoft Sentinel instances, make sure to create a separate forwarding rule for each instance. Don't use the **Add server** option in the same forwarding rule to send data to multiple Microsoft Sentinel instances. |
| 42 | +
|
| 43 | + |
| 44 | +## Next steps |
| 45 | + |
| 46 | +> [!div class="nextstepaction"] |
| 47 | +> [Stream data from cloud-connected sensors](../iot-solution.md) |
| 48 | +
|
| 49 | +> [!div class="nextstepaction"] |
| 50 | +> [Investigate in Microsoft Sentinel](/azure/sentinel/investigate-cases) |
0 commit comments