Microsoft Defender for IoT
Identity protectionSet Up SNMP MIB Monitoring on an OT Sensor
In brief
The guide now instructs administrators to access the Defender for IoT CLI over SSH as the cyberx user before setup. It also expands encryption names and updates related guidance.
What Defender admins need to know
Ensure SSH CLI access as cyberx through a terminal emulator before configuring SNMP MIB monitoring.
Summaries are generated from the documentation change itself.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
Set up SNMP MIB health monitoring on an OT sensor
|---------|---------|
|**Username** and **Password** | Enter the SNMP v3 credentials used to access the SNMP server. Both usernames and passwords must be configured on both the OT sensor and the SNMP server.<br><br>Usernames can include up to 32 alphanumeric characters, and no spaces. <br><br>Passwords are case-sensitive, and can include 8-12 alphanumeric characters. |
|**Auth Type** |Select the authentication type used to access the SNMP server: **MD5** or **SHA** |
|**Encryption** | Select the encryption used when communicating with the SNMP server: <br>- **DES*DES (Data Encryption Standard)** (56-bit key size): RFC3414 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3). <br>- **AES*AES (Advanced Encryption Standard)** (AES 128(128 bits supported): RFC3826 The Advanced Encryption Standard (AES)AES Cipher Algorithm in the SNMP User-based Security Model. |
|**Secret Key** | Enter a secret key used when communicating with the SNMP server. The secret key must have exactly eight alphanumeric characters. |
- Select Save to save your changes.
Defender for IoT in the Azure portal provides a downloadable SNMP MIB file. Load this SNMP MIB file into your SNMP monitoring system to predefine Defender for IoT sensors.
To download the SNMP MIB file from Defender for IoT on the Azure portal, select Sites and sensors > More actions > Download SNMP MIB file.
Query SNMP configuration on the sensor
Before you begin, make sure you can access the Defender for IoT CLI over SSH as the cyberx user, using a terminal emulator.
To validate and query the SNMP MIB monitoring configuration in the OT sensor:
- In the OT sensor, go to System settings > Sensor management
- To access the Defender for IoT CLI, sign in to your OT or Enterprise IoT sensor as the cyberx user, using a terminal emulator and SSH.
- Run the appropriate query for the SNMP version you configured, and update the variables accordingly:
- For version 2 type:
snmpwalk -v 2c -c<community-string> <sensor-ip> isa - For version 3 type:
snmpwalk -v 3 -aMD5|SHA -xDES|AES -A<password> -X<secret-key> -u<username> -|autoPriv <sensor-ip> isa
OT sensor OIDs for manual SNMP configurations
| License status | 1.3.6.1.4.1.53313.7 |STRING | Activation period of this appliance: Active / Expiration Date / Expired |
Related content
For more information about managing OT sensors from the web interface, see Maintain OT network sensors from the GUI.
@@ -1,10 +1,10 @@ ----title: Set up SNMP MIB monitoring on an OT sensor+title: Set Up SNMP MIB Monitoring on an OT Sensor description: Learn how to set up your OT sensor for health monitoring via SNMP. -ms.date: 06/12/2026+ms.date: 07/03/2026 ms.topic: how-to ai-usage: ai-assisted-ms.custom: msecd-doc-authoring-1014+ms.custom: msecd-doc-authoring-1016 --- # Set up SNMP MIB health monitoring on an OT sensor@@ -54,7 +54,7 @@ To download a predefined SNMP MIB file from the Azure portal, you need access to |---------|---------| |**Username** and **Password** | Enter the SNMP v3 credentials used to access the SNMP server. Both usernames and passwords must be configured on both the OT sensor and the SNMP server.<br><br>Usernames can include up to 32 alphanumeric characters, and no spaces. <br><br>Passwords are case-sensitive, and can include 8-12 alphanumeric characters. | |**Auth Type** |Select the authentication type used to access the SNMP server: **MD5** or **SHA** |- |**Encryption** | Select the encryption used when communicating with the SNMP server: <br>- **DES** (56-bit key size): RFC3414 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3). <br>- **AES** (AES 128 bits supported): RFC3826 The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model. |+ |**Encryption** | Select the encryption used when communicating with the SNMP server: <br>- **DES (Data Encryption Standard)** (56-bit key size): RFC3414 User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3). <br>- **AES (Advanced Encryption Standard)** (128 bits supported): RFC3826 The AES Cipher Algorithm in the SNMP User-based Security Model. | |**Secret Key** | Enter a secret key used when communicating with the SNMP server. The secret key must have exactly eight alphanumeric characters. | 1. Select **Save** to save your changes.@@ -63,20 +63,22 @@ To download a predefined SNMP MIB file from the Azure portal, you need access to Defender for IoT in the Azure portal provides a downloadable SNMP MIB file. Load this SNMP MIB file into your SNMP monitoring system to predefine Defender for IoT sensors. -**To download the SNMP MIB file** from [Defender for IoT](https://portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **More actions** > **Download SNMP MIB file**.+To download the SNMP MIB file from [Defender for IoT](https://portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **More actions** > **Download SNMP MIB file**. ## Query SNMP configuration on the sensor > [!NOTE] > - You can query the SNMP configuration on the sensor in version **25.2.1 or later.** +Before you begin, make sure you can [access the Defender for IoT CLI](references-work-with-defender-for-iot-cli-commands.md#defender-for-iot-cli-access) over SSH as the *cyberx* user, using a terminal emulator.+ To validate and query the SNMP MIB monitoring configuration in the OT sensor: 1. In the OT sensor, go to **System settings > Sensor management** 1. To [access the Defender for IoT CLI](references-work-with-defender-for-iot-cli-commands.md#defender-for-iot-cli-access), sign in to your OT or Enterprise IoT sensor as the *cyberx* user, using a terminal emulator and SSH. 1. Run the appropriate query for the SNMP version you configured, and update the variables accordingly:-- For version 2 type: `snmpwalk -v 2c -c<community-string> <sensor-ip> isa`-- For version 3 type: `snmpwalk -v 3 -aMD5|SHA -xDES|AES -A<password> -X<secret-key> -u<username> -|autoPriv <sensor-ip> isa`+ - For version 2 type: `snmpwalk -v 2c -c<community-string> <sensor-ip> isa`+ - For version 3 type: `snmpwalk -v 3 -aMD5|SHA -xDES|AES -A<password> -X<secret-key> -u<username> -|autoPriv <sensor-ip> isa` ## OT sensor OIDs for manual SNMP configurations @@ -110,10 +112,10 @@ If you're configuring Defender for IoT sensors on your SNMP monitoring system ma | **License status** | 1.3.6.1.4.1.53313.7 |STRING | Activation period of this appliance: Active / Expiration Date / Expired | > [!NOTE]+> > - Nonexisting keys respond with null, HTTP 200.-> - Hardware-related MIBs (CPU usage, CPU temperature, memory usage, disk usage) should be tested on all architectures and physical sensors. CPU temperature on virtual machines is expected to be non applicable.-+> - You should test Hardware-related MIBs (CPU usage, CPU temperature, memory usage, disk usage) on all architectures and physical sensors. CPU temperature on virtual machines is expected to be non applicable. -## Next steps+## Related content For more information about managing OT sensors from the web interface, see [Maintain OT network sensors from the GUI](how-to-manage-individual-sensors.md).