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
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/alerts.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ For more information, see [Securing IoT devices in the enterprise](concept-enter
45
45
46
46
## Managing OT alerts in a hybrid environment
47
47
48
-
Users working in hybrid environments may be managing OT alerts in Defender for IoT on the Azure portal, the OT sensor, and an on-premises management console.
48
+
Users working in hybrid environments may be managing OT alerts in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, the OT sensor, and an on-premises management console.
49
49
50
50
Alert statuses are fully synchronized between the Azure portal and the OT sensor, and between the sensor and the on-premises management console. This means that regardless of where you manage the alert in Defender for IoT, the alert is updated in other locations as well.
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/concept-enterprise.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ While the number of IoT devices continues to grow, they often lack the security
18
18
19
19
## IoT security across Microsoft 365 Defender and Azure
20
20
21
-
Defender for IoT provides IoT security functionality across both the Microsoft 365 Defender and Azure portals using the following methods:
21
+
Defender for IoT provides IoT security functionality across both the Microsoft 365 Defender and [Azure portals](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) using the following methods:
22
22
23
23
|Method |Description and requirements | Configure in ... |
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/configure-sensor-settings-portal.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Define a new setting whenever you want to define a specific configuration for on
37
37
38
38
**To define a new setting**:
39
39
40
-
1. In Defender for IoT on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**.
40
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**.
41
41
42
42
1. On the **Sensor settings (Preview)** page, select **+ Add**, and then use the wizard to define the following values for your setting. Select **Next** when you're done with each tab in the wizard to move to the next step.
43
43
@@ -62,7 +62,7 @@ Your new setting is now listed on the **Sensor settings (Preview)** page under i
62
62
63
63
**To view the current settings already defined for your subscription**:
64
64
65
-
1. In Defender for IoT on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**
65
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **Sensor settings (Preview)**
66
66
67
67
The **Sensor settings (Preview)** page shows any settings already defined for your subscriptions, listed by setting type. Expand or collapse each type to view detailed configurations. For example:
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/faqs-eiot.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Enterprise IoT is designed to help customers secure un-managed devices throughou
29
29
30
30
For more information, see [Onboard with Microsoft Defender for IoT](eiot-defender-for-endpoint.md).
31
31
32
-
-**In the Azure portal**: Defender for IoT customers can view their discovered IoT devices in the **Device inventory** page in Defender for IoT in the Azure portal. Register an Enterprise IoT network sensor, currently in **Public preview** to gain visibility to additional devices that aren't covered by Defender for Endpoint.
32
+
-**In the Azure portal**: Defender for IoT customers can view their discovered IoT devices in the **Device inventory** page in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal. Register an Enterprise IoT network sensor, currently in **Public preview** to gain visibility to additional devices that aren't covered by Defender for Endpoint.
33
33
34
34
For more information, see [Enhance device discovery with an Enterprise IoT network sensor (Public preview)](eiot-sensor.md).
35
35
@@ -82,7 +82,7 @@ To make any changes to an existing plan, you'll need to cancel your existing pla
82
82
83
83
To remove only Enterprise IoT from your plan, cancel your plan from Microsoft Defender for Endpoint. For more information, see [Cancel your Defender for IoT plan](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration#cancel-your-defender-for-iot-plan).
84
84
85
-
To cancel the plan and remove all Defender for IoT services from the associated subscription, cancel the plan in Defender for IoT in the Azure portal. For more information, see [Cancel your Enterprise IoT plan](manage-subscriptions-enterprise.md#cancel-your-enterprise-iot-plan).
85
+
To cancel the plan and remove all Defender for IoT services from the associated subscription, cancel the plan in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal. For more information, see [Cancel your Enterprise IoT plan](manage-subscriptions-enterprise.md#cancel-your-enterprise-iot-plan).
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/getting-started.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ This procedure describes how to add a trial Defender for IoT plan for OT network
37
37
38
38
**To add your plan**:
39
39
40
-
1. In the Azure portal, go to **Defender for IoT** and select **Plans and pricing** > **Add plan**.
40
+
1. In the Azure portal, go to [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) and select **Plans and pricing** > **Add plan**.
41
41
42
42
1. In the **Plan settings** pane, define the following settings:
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-cloud-alerts.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ For more information, see [Azure user roles and permissions for Defender for IoT
32
32
33
33
## View alerts on the Azure portal
34
34
35
-
1. In Defender for IoT on the Azure portal, select the **Alerts** page on the left. By default, the following details are shown in the grid:
35
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select the **Alerts** page on the left. By default, the following details are shown in the grid:
36
36
37
37
| Column | Description
38
38
|--|--|
@@ -93,7 +93,7 @@ Supported grouping options include *Engine*, *Name*, *Sensor*, *Severity*, and *
93
93
94
94
## Manage alert severity and status
95
95
96
-
We recommend that you update alert severity as soon as you've triaged an alert so that you can prioritize the riskiest alerts as soon as possible. Make sure to update your alert status once you've taken remediation steps so that the progress is recorded.
96
+
We recommend that you update alert severity In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal as soon as you've triaged an alert so that you can prioritize the riskiest alerts as soon as possible. Make sure to update your alert status once you've taken remediation steps so that the progress is recorded.
97
97
98
98
You can update both severity and status for a single alert or for a selection of alerts in bulk.
99
99
@@ -136,7 +136,7 @@ Downloading the PCAP file can take several minutes, depending on the quality of
136
136
137
137
You may want to export a selection of alerts to a CSV file for offline sharing and reporting.
138
138
139
-
1. In Defender for IoT on the Azure portal, select the **Alerts** page on the left.
139
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select the **Alerts** page on the left.
140
140
141
141
1. Use the search box and filter options to show only the alerts you want to export.
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-device-inventory-for-organizations.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.topic: how-to
7
7
8
8
# Manage your device inventory from the Azure portal
9
9
10
-
Use the **Device inventory** page in the Azure portal to manage all network devices detected by cloud-connected sensors, including OT, IoT, and IT. Identify new devices detected, devices that might need troubleshooting, and more.
10
+
Use the **Device inventory** page in [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal to manage all network devices detected by cloud-connected sensors, including OT, IoT, and IT. Identify new devices detected, devices that might need troubleshooting, and more.
11
11
12
12
For more information, see [What is a Defender for IoT committed device?](architecture.md#what-is-a-defender-for-iot-committed-device).
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Select the link in each widget to drill down for more information in your sensor
35
35
36
36
### Validate connectivity status
37
37
38
-
Verify that your sensor is successfully connected to the Azure portal directly from the sensor's **Overview** page.
38
+
Verify that your sensor is successfully connected to the Azure portal directly from the sensor's **Overview** page.
39
39
40
40
If there are any connection issues, a disconnection message is shown in the **General Settings** area on the **Overview** page, and a **Service connection error** warning appears at the top of the page in the :::image type="icon" source="media/how-to-manage-individual-sensors/bell-icon.png" border="false"::: **System Messages** area. For example:
41
41
@@ -49,12 +49,11 @@ If there are any connection issues, a disconnection message is shown in the **Ge
49
49
50
50
:::image type="content" source="media/how-to-manage-individual-sensors/system-messages.png" alt-text="Screenshot of the system messages pane." lightbox="media/how-to-manage-individual-sensors/system-messages.png":::
51
51
52
-
53
52
## Download software for OT sensors
54
53
55
54
You may need to download software for your OT sensor if you're [installing Defender for IoT software](ot-deploy/install-software-ot-sensor.md) on your own appliances, or [updating software versions](update-ot-software.md).
56
55
57
-
In Defender for IoT in the Azure portal, use one of the following options:
56
+
In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal, use one of the following options:
58
57
59
58
- For a new installation, select **Getting started** > **Sensor**. Select a version in the **Purchase an appliance and install software** area, and then select **Download**.
60
59
@@ -368,7 +367,7 @@ You'll need an SMTP mail server configured to enable email alerts about disconne
368
367
369
368
**Prerequisites**:
370
369
371
-
Make sure you can reach the SMTP server from the [sensor's management port](./best-practices/understand-network-architecture.md).
370
+
Make sure you can reach the SMTP server from the [sensor's management port](./best-practices/understand-network-architecture.md).
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-manage-the-on-premises-management-console.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,18 +13,19 @@ This article covers on-premises management console options like backup and resto
13
13
14
14
You may need to download software for your on-premises management console if you're [installing Defender for IoT software](ot-deploy/install-software-on-premises-management-console.md) on your own appliances, or [updating software versions](update-ot-software.md).
15
15
16
-
In Defender for IoT in the Azure portal, use one of the following options:
16
+
In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) in the Azure portal, use one of the following options:
17
17
18
-
- For a new installation or standalone update, select **Getting started** > **On-premises management console**.
18
+
- For a new installation or standalone update, select **Getting started** > **On-premises management console**.
19
19
20
-
- For a new installation, select a version in the **Purchase an appliance and install software** area, and then select **Download**.
20
+
- For a new installation, select a version in the **Purchase an appliance and install software** area, and then select **Download**.
21
21
- For an update, select your update scenario in the **On-premises management console** area and then select **Download**.
22
22
23
23
- If you're updating your on-premises management console together with connected OT sensors, use the options in the **Sites and sensors** page > **Sensor update (Preview)** menu.
For more information, see [Update Defender for IoT OT monitoring software](update-ot-software.md#update-an-on-premises-management-console).
28
+
28
29
## Upload an activation file
29
30
30
31
When you first sign in, an activation file for the on-premises management console is downloaded. This file contains the aggregate committed devices that are defined during the onboarding process. The list includes sensors associated with multiple subscriptions.
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/how-to-work-with-threat-intelligence-packages.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,15 +27,14 @@ To perform the procedures in this article, make sure that you have:
27
27
28
28
- Relevant permissions on the Azure portal and any OT network sensors or on-premises management console you want to update.
29
29
30
-
-**To download threat intelligence packages from the Azure portal**, you need access to the Azure portal as a [Security Reader](../../role-based-access-control/built-in-roles.md#security-reader), [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
30
+
-**To download threat intelligence packages from the Azure portal**, you need access to the Azure portal as a [Security Reader](../../role-based-access-control/built-in-roles.md#security-reader), [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
31
31
32
-
-**To push threat intelligence updates to cloud-connected OT sensors from the Azure portal**, you need access to Azure portal as a [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
32
+
-**To push threat intelligence updates to cloud-connected OT sensors from the Azure portal**, you need access to Azure portal as a [Security Admin](../../role-based-access-control/built-in-roles.md#security-admin), [Contributor](../../role-based-access-control/built-in-roles.md#contributor), or [Owner](../../role-based-access-control/built-in-roles.md#owner) role.
33
33
34
-
-**To manually upload threat intelligence packages to OT sensors or on-premises management consoles**, you need access to the OT sensor or on-premises management console as an **Admin** user.
34
+
-**To manually upload threat intelligence packages to OT sensors or on-premises management consoles**, you need access to the OT sensor or on-premises management console as an **Admin** user.
35
35
36
36
For more information, see [Azure user roles and permissions for Defender for IoT](roles-azure.md) and [On-premises users and roles for OT monitoring with Defender for IoT](roles-on-premises.md).
37
37
38
-
39
38
## View the most recent threat intelligence package
40
39
41
40
To view the most recent package delivered, in the Azure portal, select **Sites and sensors** > **Threat intelligence update (Preview)** > **Local update**.
@@ -54,13 +53,13 @@ Update threat intelligence packages on your OT sensors using any of the followin
54
53
55
54
### Automatically push updates to cloud-connected sensors
56
55
57
-
Threat intelligence packages can be automatically updated to *cloud connected* sensors as they're released by Defender for IoT.
56
+
Threat intelligence packages can be automatically updated to *cloud connected* sensors as they're released by Defender for IoT.
58
57
59
58
Ensure automatic package update by onboarding your cloud connected sensor with the **Automatic Threat Intelligence Updates** option enabled. For more information, see [Onboard a sensor](tutorial-onboarding.md#onboard-and-activate-the-virtual-sensor).
60
59
61
60
**To change the update mode after you've onboarded your OT sensor**:
62
61
63
-
1. In Defender for IoT on the Azure portal, select **Sites and sensors**, and then locate the sensor you want to change.
62
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors**, and then locate the sensor you want to change.
64
63
1. Select the options (**...**) menu for the selected OT sensor > **Edit**.
65
64
1. Toggle on or toggle off the **Automatic Threat Intelligence Updates** option as needed.
66
65
@@ -70,14 +69,14 @@ Your *cloud connected* sensors can be automatically updated with threat intellig
70
69
71
70
**To manually push updates to a single OT sensor**:
72
71
73
-
1. In Defender for IoT on the Azure portal, select **Sites and sensors**, and locate the OT sensor you want to update.
74
-
1. Select the options (**...**) menu for the selected sensor and then select **Push Threat Intelligence update**.
72
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors**, and locate the OT sensor you want to update.
73
+
1. Select the options (**...**) menu for the selected sensor and then select **Push Threat Intelligence update**.
75
74
76
75
The **Threat Intelligence update status** field displays the update progress.
77
76
78
77
**To manually push updates to multiple OT sensors**:
79
78
80
-
1. In Defender for IoT on the Azure portal, select **Sites and sensors**. Locate and select the OT sensors you want to update.
79
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors**. Locate and select the OT sensors you want to update.
The **Threat Intelligence update status** field displays the update progress for each selected sensor.
@@ -94,7 +93,7 @@ If you're also working with an on-premises management console, we recommend that
94
93
95
94
**To download threat intelligence packages**:
96
95
97
-
1. In Defender for IoT on the Azure portal, select **Sites and sensors** > **Threat intelligence update (Preview)** > **Local update**.
96
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Sites and sensors** > **Threat intelligence update (Preview)** > **Local update**.
98
97
99
98
1. In the **Sensor TI update** pane, select **Download** to download the latest threat intelligence file. For example:
100
99
@@ -134,7 +133,7 @@ On each OT sensor, the threat intelligence update status and version information
134
133
135
134
For cloud-connected OT sensors, threat intelligence data is also shown in the **Sites and sensors** page. To view threat intelligence statues from the Azure portal:
136
135
137
-
1. In Defender for IoT on the Azure portal, select **Site and sensors**.
136
+
1. In [Defender for IoT](https://ms.portal.azure.com/#view/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/~/Getting_started) on the Azure portal, select **Site and sensors**.
138
137
139
138
1. Locate the OT sensors where you want to check the threat intelligence statues.
140
139
@@ -149,7 +148,6 @@ For cloud-connected OT sensors, threat intelligence data is also shown in the **
149
148
> [!TIP]
150
149
> If a cloud-connected OT sensor shows that a threat intelligence update has failed, we recommend that your check your sensor connection details. On the **Sites and sensors** page, check the **Sensor status** and **Last connected UTC** columns.
0 commit comments