You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
summary: Microsoft Defender for IoT provides comprehensive threat detection for IoT/OT environments, with multiple deployment options including fully on-premises, cloud-connected, or hybrid.
5
-
brand: azure ## Used for color theming of icons and hero area
3
+
title: Microsoft Defender for IoT
4
+
summary: Microsoft Defender for IoT provides comprehensive threat detection for IoT/OT environments, with multiple deployment options that include cloud, on-premises, or hybrid.
6
5
7
6
metadata:
8
7
title: Microsoft Defender for IoT documentation
9
-
description: Learn how Microsoft Defender for IoT, an Azurebased cloud security service provides comprehensive IoT device threat protection.
8
+
description: Learn how Microsoft Defender for IoT, an Azure-based, cloud security service provides comprehensive IoT device threat protection.
title: OT monitoring appliance reference overview - Microsoft Defender for IoT
3
+
description: Provides an overview of all appliances available for use with Microsoft Defender for IoT OT sensors and on-premises management consoles.
4
+
ms.date: 07/10/2022
5
+
ms.topic: conceptual
6
+
---
7
+
8
+
# OT monitoring appliance reference
9
+
10
+
This article provides an overview of the OT monitoring appliances supported with Microsoft Defender for IoT.
11
+
12
+
Each article provides details about the appliance and any extra software installation procedures required. For more information, see [Install OT system software](../how-to-install-software.md) and [Update Defender for IoT OT monitoring software](../update-ot-software.md).
13
+
14
+
## Corporate environments
15
+
16
+
The following OT monitoring appliances are available for corporate deployments:
17
+
18
+
-[HPE ProLiant DL360](hpe-proliant-dl360.md)
19
+
20
+
## Large enterprises
21
+
22
+
The following OT monitoring appliances are available for large enterprise deployments:
23
+
24
+
-[HPE ProLiant DL20/DL20 Plus (4SFF)](hpe-proliant-dl20-plus-enterprise.md)
25
+
26
+
## Production line
27
+
28
+
The following OT monitoring appliances are available for production line deployments:
29
+
30
+
-[HPE ProLiant DL20/DL20 Plus (NHP 2LFF) for SMB deployments](hpe-proliant-dl20-plus-smb.md)
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-install-software.md
+30-23Lines changed: 30 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,13 @@
1
1
---
2
-
title: Install OT system software - Microsoft Defender for IoT
3
-
description: Learn how to install a sensor and the on-premises management console for Microsoft Defender for IoT.
4
-
ms.date: 01/06/2022
2
+
title: Install OT network monitoring software - Microsoft Defender for IoT
3
+
description: Learn how to install agentless monitoring software for an OT sensor and an on-premises management console for Microsoft Defender for IoT. Use this article if you're reinstalling software on a preconfigured appliance, or if you've chosen to install software on your own appliances.
4
+
ms.date: 07/11/2022
5
5
ms.topic: how-to
6
6
---
7
7
8
-
# Install OT system software
9
-
10
-
This article describes how to install software for OT sensors and on-premises management consoles. You might need the procedures in this article if you're reinstalling software on a preconfigured appliance, or if you've chosen to install software on your own appliances.
8
+
# Install OT agentless monitoring software
11
9
10
+
This article describes how to install agentless monitoring software for OT sensors and on-premises management consoles. You might need the procedures in this article if you're reinstalling software on a preconfigured appliance, or if you've chosen to install software on your own appliances.
12
11
13
12
## Pre-installation configuration
14
13
@@ -26,7 +25,7 @@ For more information, see:
26
25
27
26
Make sure that you've downloaded the relevant software file for the sensor or on-premises management console.
28
27
29
-
You can obtain the latest versions of our OT sensor and on-premises management console software from the Azure portal, on the Defender for IoT > **Getting started** page. Select the **Sensor**, **On-premises management console**, or **Updates** tab and locate the software you need.
28
+
You can obtain the latest versions of our OT sensor and on-premises management console software from the Azure portal. On the Defender for IoT > **Getting started** page, select the **Sensor**, **On-premises management console**, or **Updates** tab and locate the software you need.
30
29
31
30
Mount the ISO file using one of the following options:
32
31
@@ -59,33 +58,33 @@ This procedure describes how to install OT sensor software on a physical or virt
59
58
60
59
1. The sensor will reboot, and the **Package configuration** screen will appear. Press the up or down arrows to navigate, and the SPACE bar to select an option. Press ENTER to advance to the next screen.
61
60
62
-
1. Select the monitor interface and press the **ENTER** key.
61
+
1. Select the monitor interface. For example:
63
62
64
63
:::image type="content" source="media/tutorial-install-components/monitor-interface.png" alt-text="Screenshot of the select monitor interface screen.":::
65
64
66
-
1. If one of the monitoring ports is for ERSPAN, select it, and press the **ENTER** key.
65
+
1. If one of the monitoring ports is for ERSPAN, select it. For example:
67
66
68
67
:::image type="content" source="media/tutorial-install-components/erspan-monitor.png" alt-text="Screenshot of the select erspan monitor screen.":::
69
68
70
-
1. Select the interface to be used as the management interface, and press the **ENTER** key.
69
+
1. Select the interface to be used as the management interface. For example:
71
70
72
71
:::image type="content" source="media/tutorial-install-components/management-interface.png" alt-text="Screenshot of the management interface select screen.":::
73
72
74
-
1. Enter the sensor's IP address, and press the **ENTER** key.
73
+
1. Enter the sensor's IP address. For example:
75
74
76
75
:::image type="content" source="media/tutorial-install-components/sensor-ip-address.png" alt-text="Screenshot of the sensor IP address screen.":::
77
76
78
-
1. Enter the path of the mounted logs folder. We recommend using the default path, and press the **ENTER** key.
77
+
1. Enter the path of the mounted logs folder. We recommend using the default path. For example:
79
78
80
79
:::image type="content" source="media/tutorial-install-components/mounted-backups-path.png" alt-text="Screenshot of the mounted backup path screen.":::
81
80
82
-
1. Enter the Subnet Mask IP address, and press the **ENTER** key.
81
+
1. Enter the Subnet Mask IP address. For example:
83
82
84
-
1. Enter the default gateway IP address, and press the **ENTER** key.
83
+
1. Enter the default gateway IP address.
85
84
86
-
1. Enter the DNS Server IP address, and press the **ENTER** key.
85
+
1. Enter the DNS Server IP address.
87
86
88
-
1. Enter the sensor hostname and press the **ENTER** key.
87
+
1. Enter the sensor hostname. For example:
89
88
90
89
:::image type="content" source="media/tutorial-install-components/sensor-hostname.png" alt-text="Screenshot of the screen where you enter a hostname for your sensor.":::
91
90
@@ -150,9 +149,9 @@ For information on how to find the physical port on your appliance, see [Find yo
150
149
151
150
### Add a secondary NIC (optional)
152
151
153
-
You can enhance security to your on-premises management console by adding a secondary NIC dedicated for attached sensors within an IP address range. By adding a secondary NIC, the first will be dedicated for end-users, and the secondary will support the configuration of a gateway for routed networks.
152
+
You can enhance security to your on-premises management console by adding a secondary NIC dedicated for attached sensors within an IP address range. When you use a secondary NIC, the first is dedicated for end-users, and the secondary supports the configuration of a gateway for routed networks.
154
153
155
-
:::image type="content" source="media/tutorial-install-components/secondary-nic.png" alt-text="The overall architecture of the secondary NIC.":::
154
+
:::image type="content" source="media/tutorial-install-components/secondary-nic.png" alt-text="Diagram that shows the overall architecture of the secondary NIC." border="false":::
156
155
157
156
Both NICs will support the user interface (UI). If you choose not to deploy a secondary NIC, all of the features will be available through the primary NIC.
158
157
@@ -199,7 +198,7 @@ This command will cause the light on the port to flash for the specified time pe
199
198
200
199
After you've finished installing OT monitoring software on your appliance, test your system to make sure that processes are running correctly. The same validation process applies to all appliance types.
201
200
202
-
System health validations are supported via the sensor or on-premises management console UI or CLI, and is available for both the **Support** and **CyberX** users.
201
+
System health validations are supported via the sensor or on-premises management console UI or CLI, and are available for both the **Support** and **CyberX** users.
203
202
204
203
After installing OT monitoring software, make sure to run the following tests:
205
204
@@ -211,13 +210,21 @@ After installing OT monitoring software, make sure to run the following tests:
211
210
212
211
For more information, see [Check system health](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md#check-system-health) in our sensor and on-premises management console troubleshooting article.
213
212
214
-
## Access sensors from the on-premises management console
213
+
## Configure tunneling access for sensors through the on-premises management console
214
+
215
+
Enhance system security by preventing direct user access to the sensor.
216
+
217
+
Instead of direct access, use proxy tunneling to let users access the sensor from the on-premises management console with a single firewall rule. This technique narrows the possibility of unauthorized access to the network environment beyond the sensor. The user's experience when signing in to the sensor remains the same.
218
+
219
+
When tunneling access is configured, users use the following URL syntax to access their sensor consoles: `https://<on-premises management console address>/<sensor address>/<page URL>`
220
+
221
+
For example, the following image shows a sample architecture where users access the sensor consoles via the on-premises management console.
215
222
216
-
You can enhance system security by preventing direct user access to the sensor. Instead, use proxy tunneling to let users access the sensor from the on-premises management console with a single firewall rule. This technique narrows the possibility of unauthorized access to the network environment beyond the sensor. The user's experience when signing in to the sensor remains the same.
223
+
:::image type="content" source="media/tutorial-install-components/sensor-system-graph.png" alt-text="Screenshot that shows access to the sensor." border="false":::
217
224
218
-
:::image type="content" source="media/tutorial-install-components/sensor-system-graph.png" alt-text="Screenshot that shows access to the sensor.":::
225
+
The interface between the IT firewall, on-premises management console, and the OT firewall is done using a reverse proxy with URL rewrites. The interface between the OT firewall and the sensors is done using reverse SSH tunnels.
219
226
220
-
**To enable tunneling**:
227
+
**To enable tunneling access for sensors**:
221
228
222
229
1. Sign in to the on-premises management console's CLI with the **CyberX** or the **Support** user credentials.
0 commit comments