Skip to content

Commit f4a29a7

Browse files
yoninalmsftyoninalmsft
committed
FAQ EIoT
1 parent 0985af3 commit f4a29a7

File tree

5 files changed

+158
-32
lines changed

5 files changed

+158
-32
lines changed

‎.openpublishing.redirection.defender-for-iot.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/defender-for-iot/organizations/resources-frequently-asked-questions.md",
5+
"redirect_url": "/azure/defender-for-iot/organizations/faqs-general",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/defender-for-iot/organizations/appliance-catalog/appliance-catalog-overview.md",
510
"redirect_url": "/azure/defender-for-iot/organizations/appliance-catalog/index",

‎articles/defender-for-iot/organizations/TOC.yml

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -253,9 +253,14 @@
253253
href: references-work-with-defender-for-iot-apis.md
254254
- name: Defender for IoT CLI commands
255255
href: references-work-with-defender-for-iot-cli-commands.md
256-
- name: Frequently asked questions - service
257-
displayName: FAQ, regulation, internet, connection, hardware, appliances, ports, logs
258-
href: resources-frequently-asked-questions.md
256+
- name: Frequently asked questions
257+
items:
258+
- name: General FAQ
259+
href: faqs-general.md
260+
- name: OT networks FAQ
261+
href: faqs-ot.md
262+
- name: Enterprise IoT networks FAQ
263+
href: faqs-eiot.md
259264
- name: Defender for IoT glossary
260265
href: references-defender-for-iot-glossary.md
261266
- name: Resources

‎articles/defender-for-iot/organizations/faqs-eiot.md

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
---
2+
title: FAQs for Enterprise IoT networks - Microsoft Defender for IoT
3+
description: Find answers to the most frequently asked questions about Microsoft Defender for IoT Enterprise IoT networks.
4+
ms.topic: conceptual
5+
ms.date: 07/07/2022
6+
---
7+
8+
# Enterprise IoT networks frequently asked questions
9+
10+
This article provides a list of frequently asked questions and answers about Enterprise IoT networks in Defender for IoT.
11+
12+
## How can I start using Enterprise IoT?
13+
14+
To get started, you'll need to:
15+
16+
1. Add a Defender for IoT plan with Enterprise IoT to your Azure subscription.
17+
1. Set up a Defender for IoT network sensor.
18+
19+
You can add a plan from either Defender for IoT in the Azure portal or Microsoft Defender for Endpoint. If you’re a Defender for Endpoint customer, when adding your Defender for IoT plan, take care to exclude any devices already managed by Defender for Endpoint from your count of committed devices.
20+
21+
For more information, see:
22+
- [Quickstart: Get started with Defender for IoT](getting-started.md)
23+
- [Tutorial: Get started with Enterprise IoT](tutorial-getting-started-eiot-sensor.md)
24+
- [Defender for IoT integration](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration)
25+
26+
## How can I use the Enterprise IoT network sensor?
27+
28+
The Enterprise IoT network sensor is currently in Public Preview and can be used by all customers without additional charge. Add a Defender for IoT plan with Enterprise IoT, and then set up your Enterprise IoT network sensor.
29+
30+
For more information, see [Tutorial: Get started with Enterprise IoT](tutorial-getting-started-eiot-sensor.md).
31+
32+
## What permissions do I need to add a Defender for IoT plan? Can I use any Azure subscription?
33+
34+
Azure users with the **Security admin**, **Subscription owner** or **Subscription contributor** roles can add, edit, and cancel Defender for IoT plans. For more information, see [Permissions](getting-started.md#permissions).
35+
36+
Defender for Endpoint users with the **Global admin** role can add or cancel plans.
37+
38+
## Which devices are billable?
39+
40+
Devices are listed in the Defender for IoT device inventory based on a unique IP and MAC address coupling. Charges are based on the number of committed devices you provide when adding a Defender for IoT plan.
41+
42+
If you're a Defender for Endpoint customer, devices (seats) that are managed by Defender for Endpoint aren't included in the number of devices counted as committed devices.
43+
44+
For more information, see [Defender for IoT committed devices](how-to-manage-subscriptions.md#defender-for-iot-committed-devices).
45+
46+
## How should I estimate the number of committed devices?
47+
48+
We suggest using existing resources in your environment, for example Meraki, CMDB and other sources to get that estimation, as well as the device inventories in Defender for Endpoint and Defender for IoT. Once you have onboarded Defender for IoT, discovered devices will begin to populate in the device inventory and then you can update the number of your committed devices accordingly. A device would be a set combination of IP address and a MAC address. For more information, see [Defender for IoT committed devices](how-to-manage-subscriptions.md#defender-for-iot-committed-devices).
49+
50+
## Can I exclude unmanaged devices from the device inventory list?
51+
52+
Yes, in Defender for Endpoint, use *onboarding status* to filter for unmanaged devices. Use either the *Onboarding status* column in the Defender for Endpoint **Device inventory** page or filter API queries by the *onboarding status* field.
53+
54+
## Can I edit information in Defender for IoT about a discovered device?
55+
56+
You can edit several properties for devices, and even delete devices from the Defender for IoT **Device inventory** page. For more information, see [Edit device details](how-to-manage-device-inventory-for-organizations.md#edit-device-details).
57+
58+
## How does the integration between Microsoft Defender for Endpoint and Microsoft Defender for IoT work?
59+
60+
Integration between the two products takes place seamlessly, once you have:
61+
- Added a Defender for IoT plan with Enterprise IoT to an Azure subscription, either from Defender for IoT or Defender for Endpoint
62+
- Set up an Enterprise IoT or OT sensor from Defender for IoT in the Azure portal
63+
64+
Once these requirements are met, discovered devices can be viewed in both Defender for IoT and Defender for Endpoint. For more information, see [Defender for IoT integration](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration).
65+
66+
## Can I change the subscription I’m using for Defender for IoT?
67+
68+
To change the subscription you're using for your Defender for IoT plan, you'll need to cancel your plan on the existing subscription, and then add a new plan to a new subscription. Your existing data won't be migrated to the new subscription. For more information, see [Move existing sensors to a different subscription](how-to-manage-subscriptions.md#move-existing-sensors-to-a-different-subscription).
69+
70+
## How can I cancel Enterprise IoT?
71+
72+
If you have both Enterprise IoT and OT networks on your Defender for IoT plan, you can remove Enterprise IoT and leave OT in place by editing your plan. For more information, see [Edit a plan](how-to-manage-subscriptions.md#edit-a-plan).
73+
74+
You can cancel the entire plan from your subscription, removing all Defender for IoT services from that subscription. For more information, see [Cancel a Defender for IoT plan from a subscription](how-to-manage-subscriptions.md#cancel-a-defender-for-iot-plan-from-a-subscription).
75+
76+
You can also cancel your plan from the Defender for Endpoint portal. For more information, see [Defender for IoT integration](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration).
77+
78+
## What happens when the 30-day trial ends?
79+
80+
If you haven't changed your plan from a trial to a monthly commitment by the time your trial ends, your plan is automatically canceled, and you’ll lose access to Defender for IoT security features.
81+
82+
You can edit your plan at any time during your trial and update to a monthly commitment. For more information, see [Edit a plan](how-to-manage-subscriptions.md#edit-a-plan).
83+
84+
## How is pricing for Defender for IoT affected now that support for Enterprise IoT networks is in General Availability?
85+
86+
For more information, see the [Microsoft Defender for IoT pricing](https://azure.microsoft.com/pricing/details/iot-defender/) page.
87+
88+
> [!NOTE]
89+
> The Enterprise IoT network sensor is currently in Public Preview.
90+
91+
## How can I resolve billing issues associated with my Defender for IoT plan?
92+
93+
For any billing or technical issues, create a support request in the Azure portal.
94+
95+
## Next steps
96+
97+
For more information on getting started with Enterprise IoT, see:
98+
99+
- [Tutorial: Get started with Enterprise IoT monitoring](tutorial-getting-started-eiot-sensor.md)
100+
- [Manage Defender for IoT plans](how-to-manage-subscriptions.md)
101+
- [Defender for IoT integration](/microsoft-365/security/defender-endpoint/enable-microsoft-defender-for-iot-integration)

‎articles/defender-for-iot/organizations/faqs-general.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: General FAQs - Microsoft Defender for IoT
3+
description: Find answers to the most frequently asked questions about Microsoft Defender for IoT features and service.
4+
ms.topic: conceptual
5+
ms.date: 07/07/2022
6+
---
7+
8+
# Microsoft Defender for IoT frequently asked questions
9+
10+
This article provides a list of frequently asked questions and answers about Defender for IoT.
11+
12+
## What is Azure's unique value proposition for IoT security?
13+
14+
Defender for IoT enables enterprises to extend their existing cyber security view to their entire IoT solution. Azure provides an end to end view of your business solution, enabling you to take business-related actions and decisions based on your enterprise security posture and collected data. Combined security using Azure IoT, Azure IoT Edge, and Microsoft Defender for Cloud enable you to create the solution you want with the security you need.
15+
16+
## How does Defender for IoT compare to the competition?
17+
18+
Microsoft Defender for IoT delivers comprehensive security across all your IoT/OT devices. For **end-user organizations**, Microsoft Defender for IoT offers agentless, network-layer security that is rapidly deployed, works with diverse proprietary OT equipment and legacy Windows systems, and interoperates with Microsoft Sentinel and other SOC tools. It can be deployed on-premises or in Azure-connected environments. For **IoT device builders**, Microsoft Defender for IoT offers lightweight agents to embed device-layer security into new IoT/OT initiatives.
19+
20+
## Do I have to be an Azure customer?
21+
22+
No, for the agentless version of Microsoft Defender for IoT, you do not need to be an Azure customer. However, if you want to send alerts to Microsoft Sentinel; provision network sensors and monitor their health from the cloud; and benefit from automatic software and threat intelligence updates, you will need to connect the sensor to Azure and Defender for IoT. For more information, see [Sensor connection methods](architecture-connections.md).
23+
24+
For the agent-based version of Microsoft Defender for IoT, you must be an Azure customer.
25+
26+
## What happens when the internet connection stops working?
27+
28+
The sensors and agents continue to run and store data as long as the device is running. Data is stored in the security message cache according to size configuration. When the device regains connectivity, security messages resume sending.
29+
30+
## Next steps
31+
32+
To learn more about how to get started with Defender for IoT, see the following articles:
33+
34+
- Read the Defender for IoT [overview](overview.md)
35+
- [Get started with Defender for IoT](getting-started.md)
36+
- [OT Networks frequently asked questions](faqs-ot.md)
37+
- [Enterprise IoT networks frequently asked questions](faqs-eiot.md)

‎articles/defender-for-iot/organizations/resources-frequently-asked-questions.md renamed to ‎articles/defender-for-iot/organizations/faqs-ot.md

Lines changed: 7 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,13 @@
11
---
2-
title: Defender for IoT frequently asked questions
3-
description: Find answers to the most frequently asked questions about Microsoft Defender for IoT features and service.
2+
title: FAQs for OT networks - Microsoft Defender for IoT
3+
description: Find answers to the most frequently asked questions about Microsoft Defender for IoT OT networks.
44
ms.topic: conceptual
5-
ms.date: 11/09/2021
5+
ms.date: 07/07/2022
66
---
77

8-
# Microsoft Defender for IoT frequently asked questions
8+
# OT Networks frequently asked questions
99

10-
This article provides a list of frequently asked questions and answers about Defender for IoT.
11-
12-
## What is Azure's unique value proposition for IoT security?
13-
14-
Defender for IoT enables enterprises to extend their existing cyber security view to their entire IoT solution. Azure provides an end to end view of your business solution, enabling you to take business-related actions and decisions based on your enterprise security posture and collected data. Combined security using Azure IoT, Azure IoT Edge, and Microsoft Defender for Cloud enable you to create the solution you want with the security you need.
10+
This article provides a list of frequently asked questions and answers about OT networks in Defender for IoT.
1511

1612
## Our organization uses proprietary non-standard industrial protocols. Are they supported?
1713

@@ -27,7 +23,6 @@ Microsoft Defender for IoT sensor runs on specific hardware specs as described i
2723

2824
Certified hardware has been tested in our labs for driver stability, packet drops and network sizing.
2925

30-
3126
## Regulation doesn't allow us to connect our system to the Internet. Can we still utilize Defender for IoT?
3227

3328
Yes you can! The Microsoft Defender for IoT platform on-premises solution is deployed as a physical or virtual sensor appliance that passively ingests network traffic (via SPAN, RSPAN, or TAP) to analyze, discover, and continuously monitor IT, OT, and IoT networks. For larger enterprises, multiple sensors can aggregate their data to an on-premises management console.
@@ -40,20 +35,6 @@ For example:
4035
- A single appliance (virtual of physical) can be in the Shop Floor DMZ layer, having all Shop Floor cell traffic routed to this layer.
4136
- Alternatively, locate small mini-sensors in each Shop Floor cell with either cloud or local management that will reside in the Shop Floor DMZ layer. Another appliance (virtual or physical) can monitor the traffic in the Shop Floor DMZ layer (for SCADA, Historian, or MES).
4237

43-
## How does Defender for IoT compare to the competition?
44-
45-
Microsoft Defender for IoT delivers comprehensive security across all your IoT/OT devices. For **end-user organizations**, Microsoft Defender for IoT offers agentless, network-layer security that is rapidly deployed, works with diverse proprietary OT equipment and legacy Windows systems, and interoperates with Microsoft Sentinel and other SOC tools. It can be deployed on-premises or in Azure-connected environments. For **IoT device builders**, Microsoft Defender for IoT offers lightweight agents to embed device-layer security into new IoT/OT initiatives.
46-
47-
## Do I have to be an Azure customer?
48-
49-
No, for the agentless version of Microsoft Defender for IoT, you do not need to be an Azure customer. However, if you want to send alerts to Microsoft Sentinel; provision network sensors and monitor their health from the cloud; and benefit from automatic software and threat intelligence updates, you will need to connect the sensor to Azure and Defender for IoT. For more information, see [Sensor connection methods](architecture-connections.md).
50-
51-
For the agent-based version of Microsoft Defender for IoT, you must be an Azure customer.
52-
53-
## What happens when the internet connection stops working?
54-
55-
The sensors and agents continue to run and store data as long as the device is running. Data is stored in the security message cache according to size configuration. When the device regains connectivity, security messages resume sending.
56-
5738
## How can I change a user's passwords
5839

5940
Learn how to [Change a user's password](how-to-create-and-manage-users.md#change-a-users-password) for either the sensor or the on-premises management console.
@@ -82,9 +63,6 @@ You can also use our [UI and CLI tools](how-to-troubleshoot-the-sensor-and-on-pr
8263

8364
For more information, see [Troubleshoot the sensor and on-premises management console](how-to-troubleshoot-the-sensor-and-on-premises-management-console.md).
8465

85-
## Next steps
86-
87-
To learn more about how to get started with Defender for IoT, see the following articles:
66+
## Next Steps
8867

89-
- Read the Defender for IoT [overview](overview.md)
90-
- [Get started with Defender for IoT](getting-started.md)
68+
- [Tutorial: Get started with Microsoft Defender for IoT for OT security](tutorial-onboarding.md)

0 commit comments

Comments
 (0)