Skip to content

Commit ac5e54a

Browse files
authored
Merge pull request #951 from MicrosoftDocs/chrisda
Smart quote and weird non-ASCII text replacement
2 parents 3f74507 + d0c729d commit ac5e54a

11 files changed

+129
-123
lines changed

defender-for-iot/device-discovery.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Learn how to [discover and manage your IoT/OT devices](manage-devices-inventory.
2424
## Device inventory: initial view
2525

2626
If you don't yet have a Defender for IoT license, the **Device inventory** page detects your OT devices and lists them with regular device data, but without security data. For example, the device name, IP, and category are visible, while the risk level isn't visible. The device inventory also displays a note at the top of the page that indicates the number of unprotected OT devices.
27-
27+
2828
In this case, [onboard Defender for IoT](get-started.md) to get security value for your OT devices.
2929

3030
If you're seeing the message that indicates the number of unprotected OT devices, and you've already set up Defender for IoT, [set up a site](set-up-sites.md) and associate the relevant devices with it.
@@ -41,29 +41,29 @@ Learn more about the [device inventory in Microsoft Defender for Endpoint](/defe
4141

4242
The key device discovery capabilities are:
4343

44-
|Capability |Description |
45-
|---------|---------|
46-
|OT device management |[Manage OT devices](manage-devices-inventory.md):<br>- Build an up-to-date inventory that includes all your managed and unmanaged devices.<br>- Classify critical devices to ensure that the most important assets in your organization are protected.<br>- Add organization-specific information to emphasize your organization preferences. |
47-
|Device protection with risk-based approach |Identify risks such as missing patches, vulnerabilities and prioritize fixes based on risk scoring and automated threat modeling. |
48-
|Device alignment with physical sites |Allows contextual security monitoring. Use the **Site** filter to manage each site separately. Learn more about [filters](/defender-endpoint/machines-view-overview#use-filters-to-customize-the-device-inventory-views). |
49-
|Device groups |Allows different teams in your organization to monitor and manage relevant assets only. Learn more about [creating a device group](/defender-endpoint/machine-groups#create-a-device-group). |
50-
|Device criticality |Reflects how critical a device is for your organization and allows you to identify a device as a business critical asset. Learn more about [device criticality](/defender-endpoint/machines-view-overview#device-inventory-overview). |
44+
|Capability|Description|
45+
|---|---|
46+
|OT device management|[Manage OT devices](manage-devices-inventory.md):<br>- Build an up-to-date inventory that includes all your managed and unmanaged devices.<br>- Classify critical devices to ensure that the most important assets in your organization are protected.<br>- Add organization-specific information to emphasize your organization preferences.|
47+
|Device protection with risk-based approach|Identify risks such as missing patches, vulnerabilities and prioritize fixes based on risk scoring and automated threat modeling.|
48+
|Device alignment with physical sites|Allows contextual security monitoring. Use the **Site** filter to manage each site separately. Learn more about [filters](/defender-endpoint/machines-view-overview#use-filters-to-customize-the-device-inventory-views).|
49+
|Device groups|Allows different teams in your organization to monitor and manage relevant assets only. Learn more about [creating a device group](/defender-endpoint/machine-groups#create-a-device-group).|
50+
|Device criticality|Reflects how critical a device is for your organization and allows you to identify a device as a business critical asset. Learn more about [device criticality](/defender-endpoint/machines-view-overview#device-inventory-overview).|
5151

5252
## Supported devices
5353

5454
Defender for IoT's device inventory supports the following device classes:
5555

56-
|Devices |Example |
57-
|---------|---------|
58-
|**Manufacturing**| Industrial and operational devices, such as pneumatic devices, packaging systems, industrial packaging systems, industrial robots |
59-
|**Building** | Access panels, surveillance devices, HVAC systems, elevators, smart lighting systems |
60-
|**Health care** | Glucose meters, monitors |
61-
|**Transportation / Utilities** | Turnstiles, people counters, motion sensors, fire and safety systems, intercoms |
62-
|**Energy and resources** | DCS controllers, PLCs, historian devices, HMIs |
63-
|**Endpoint devices** | Workstations, servers, or mobile devices |
64-
| **Enterprise** | Smart devices, printers, communication devices, or audio/video devices |
65-
| **Retail** | Barcode scanners, humidity sensor, punch clocks |
56+
|Devices|Example|
57+
|---|---|
58+
|**Manufacturing**|Industrial and operational devices, such as pneumatic devices, packaging systems, industrial packaging systems, industrial robots|
59+
|**Building**|Access panels, surveillance devices, HVAC systems, elevators, smart lighting systems|
60+
|**Health care**|Glucose meters, monitors|
61+
|**Transportation / Utilities**|Turnstiles, people counters, motion sensors, fire and safety systems, intercoms|
62+
|**Energy and resources**|DCS controllers, PLCs, historian devices, HMIs|
63+
|**Endpoint devices**|Workstations, servers, or mobile devices|
64+
|**Enterprise**|Smart devices, printers, communication devices, or audio/video devices|
65+
|**Retail**|Barcode scanners, humidity sensor, punch clocks|
6666

6767
## Next steps
6868

69-
[Discover and manage devices](manage-devices-inventory.md)
69+
[Discover and manage devices](manage-devices-inventory.md)

defender-for-iot/microsoft-defender-iot.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -22,18 +22,18 @@ In this article, you learn how Microsoft Defender customers can extend their pro
2222

2323
You can work with these different flavors of Defender for IoT:
2424

25-
|Flavor |Details |Next steps |
26-
|---------|---------|---------|
27-
|Defender for IoT in the Defender portal (Preview) |Microsoft Defender customers can use this flavor for a unified IT/OT experience, extending Defender XDR protection to OT environments. [Learn about the main use cases](#what-are-the-main-defender-for-iot-use-cases). |[Get started](get-started.md) with Defender for IoT in the Defender portal. |
28-
|Defender for IoT in the classic, Azure portal |All customers can use this flavor to identify OT devices, vulnerabilities, and threats in the Azure portal. |See the [Defender for IoT on Azure overview](/azure/defender-for-iot/organizations/overview). |
29-
|Protection for enterprise IoT devices |Microsoft Defender customers can enable protection for enterprise IoT devices, like printers, smart TVs, and conferencing systems and purpose-built, proprietary devices. |[Get started](/azure/defender-for-iot/organizations/eiot-sensor) with enterprise IoT monitoring. |
25+
|Flavor|Details|Next steps|
26+
|---|---|---|
27+
|Defender for IoT in the Defender portal (Preview)|Microsoft Defender customers can use this flavor for a unified IT/OT experience, extending Defender XDR protection to OT environments. [Learn about the main use cases](#what-are-the-main-defender-for-iot-use-cases).|[Get started](get-started.md) with Defender for IoT in the Defender portal.|
28+
|Defender for IoT in the classic, Azure portal|All customers can use this flavor to identify OT devices, vulnerabilities, and threats in the Azure portal.|See the [Defender for IoT on Azure overview](/azure/defender-for-iot/organizations/overview).|
29+
|Protection for enterprise IoT devices|Microsoft Defender customers can enable protection for enterprise IoT devices, like printers, smart TVs, and conferencing systems and purpose-built, proprietary devices.|[Get started](/azure/defender-for-iot/organizations/eiot-sensor) with enterprise IoT monitoring.|
3030

3131
## Who uses Defender for IoT?
3232

3333
Defender for IoT is intended for:
3434

3535
- **CISOs** or security leaders that want to gain an overview of their organization's OT network and security.
36-
- **OT security admins, industrial engineers, risk managers, and SOC analysts** that want to gain a high-level view of a site's risks, incidents, and vulnerabilities, get recommendations for remediation actions, manage and discover protected OT devices, and more.
36+
- **OT security admins, industrial engineers, risk managers, and SOC analysts** that want to gain a high-level view of a site's risks, incidents, and vulnerabilities, get recommendations for remediation actions, manage and discover protected OT devices, and more.
3737

3838
## What are the main OT security challenges?
3939

@@ -51,13 +51,13 @@ Defender for IoT in the Defender portal uses the following combination of techno
5151

5252
## What are the main Defender for IoT use cases?
5353

54-
|Use case |Capabilities |
55-
|---------|---------|
56-
|**[Discover OT devices](manage-devices-inventory.md)** |Gather OT network data from Microsoft Defender for Endpoint; identify and manage OT devices. |
57-
|**[Get an overview of your productions sites (site security)](site-security-overview.md)** |Get an overview of your production sites to gain insights into OT risks, make better-informed security investment decisions, and streamline communication between stakeholders. |
58-
|**[Prioritize and remediate vulnerabilities](prioritize-vulnerabilities.md)** |Proactively manage OT network risks based on vulnerability details and recommended remediation advice. |
59-
|**[Analyze incidents](investigate-threats.md) and respond to threats** |Review incidents and alerts with real-time details about events logged in your OT network and take recommended remediation actions. |
60-
|**Extend Microsoft Defender XDR** |Microsoft Defender XDR and Defender for IoT form a unified pre- and post-breach enterprise defense suite. This suite natively integrates across endpoint, IoT/OT, identity, email, and applications to detect, prevent, investigate, and automatically respond to sophisticated attacks. |
54+
|Use case|Capabilities|
55+
|---|---|
56+
|**[Discover OT devices](manage-devices-inventory.md)**|Gather OT network data from Microsoft Defender for Endpoint; identify and manage OT devices.|
57+
|**[Get an overview of your productions sites (site security)](site-security-overview.md)**|Get an overview of your production sites to gain insights into OT risks, make better-informed security investment decisions, and streamline communication between stakeholders.|
58+
|**[Prioritize and remediate vulnerabilities](prioritize-vulnerabilities.md)**|Proactively manage OT network risks based on vulnerability details and recommended remediation advice.|
59+
|**[Analyze incidents](investigate-threats.md) and respond to threats**|Review incidents and alerts with real-time details about events logged in your OT network and take recommended remediation actions.|
60+
|**Extend Microsoft Defender XDR**|Microsoft Defender XDR and Defender for IoT form a unified pre- and post-breach enterprise defense suite. This suite natively integrates across endpoint, IoT/OT, identity, email, and applications to detect, prevent, investigate, and automatically respond to sophisticated attacks.|
6161

6262
## Next steps
6363

defender-for-iot/prerequisites.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -58,18 +58,18 @@ If you're using the Defender portal for the first time, you need to set up all o
5858

5959
The unified RBAC roles and permissions to give users access to [site security](site-security-overview.md) features are:
6060

61-
|Write permissions |Read permissions |
61+
|Write permissions|Read permissions|
6262
|----|----|
63-
| **MDE Roles**: Core security settings scoped to all device groups. <br>**Entra ID roles**: Global Administrator, Security Administrator, Security Operator scoped to all device groups.| Write roles (including roles that aren't scoped to all device groups). <br> **MDE Roles**: Security data basics (under Security Operations).<br>**Entra ID roles**: Global Reader, Security Reader.|
63+
|**MDE Roles**: Core security settings scoped to all device groups. <br>**Entra ID roles**: Global Administrator, Security Administrator, Security Operator scoped to all device groups.|Write roles (including roles that aren't scoped to all device groups). <br> **MDE Roles**: Security data basics (under Security Operations).<br>**Entra ID roles**: Global Reader, Security Reader.|
6464

6565
This table shows the full roles and permissions needed for all MDE features used with Defender for IoT:
6666

67-
| Feature | Write permissions | Read permissions |
67+
|Feature|Write permissions|Read permissions|
6868
|---|----|---|
69-
|Alerts and incidents| **MDE Roles**: Alerts (manage) <br> **Entra ID roles**: Global Administrator, Security Administrator, Security Operator| Write roles<br> **MDE Roles**: Security data basics<br>**Entra ID roles**: Global Reader, Security Reader |
70-
|Vulnerabilities | **MDE Roles**: Response (manage)\Security operations \ Security data <br>**Entra ID roles**: Global Administrator, Security Administrator, Security Operator | Write roles<br> **MDE Roles**: Vulnerability management (read) <br> **Entra ID roles**: Global Reader, Security Reader |
71-
|Inventory| **MDE Roles**: Onboard offboard device: Detection tuning (manage) <br> Manage device tags: Alerts (manage)<br>**Entra ID roles**: Global Administrator, Security Administrator, Security Operator | Write roles <br>**MDE Roles**: Security data basics/Security operations \ Security data <br> **Entra ID roles**: Global Reader, Security Reader |
72-
|Device group| **MDE Roles**: Authorization (Read and manage) <br>**Entra ID roles**: Global Administrator, Security Administrator|**MDE Roles**: Authorization (write roles, Read-only) |
69+
|Alerts and incidents|**MDE Roles**: Alerts (manage) <br> **Entra ID roles**: Global Administrator, Security Administrator, Security Operator|Write roles<br> **MDE Roles**: Security data basics<br>**Entra ID roles**: Global Reader, Security Reader|
70+
|Vulnerabilities|**MDE Roles**: Response (manage)\ Security operations \ Security data <br>**Entra ID roles**: Global Administrator, Security Administrator, Security Operator|Write roles<br> **MDE Roles**: Vulnerability management (read) <br> **Entra ID roles**: Global Reader, Security Reader|
71+
|Inventory|**MDE Roles**: Onboard offboard device: Detection tuning (manage) <br> Manage device tags: Alerts (manage) <br>**Entra ID roles**: Global Administrator, Security Administrator, Security Operator|Write roles <br>**MDE Roles**: Security data basics/Security operations \ Security data <br> **Entra ID roles**: Global Reader, Security Reader|
72+
|Device group|**MDE Roles**: Authorization (Read and manage) <br>**Entra ID roles**: Global Administrator, Security Administrator|**MDE Roles**: Authorization (write roles, Read-only)|
7373

7474
To assign roles and permissions for other Microsoft Defender for Endpoint features, such as alerts, incidents and inventory, see [assign roles and permissions for Defender for Endpoint](/defender-endpoint/prepare-deployment).
7575

defender-office-365/attack-simulation-training-insights.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -439,8 +439,8 @@ How user activity signals are captured is described in the following table.
439439
|Read Message|The user read the simulation message.|Message read signals might experience issues in the following scenarios: <ul><li>The user reported the message as phishing in Outlook without leaving the reading pane, and **Mark items as read when viewed in the Reading Pane** wasn't configured (default).</li><li>The user reported the unread message as phishing in Outlook, the message was deleted, and **Mark messages as read when deleted** wasn't configured (default).</li></ul>|
440440
|Out of Office|Determines whether the user is out of office.|Currently calculated by the Automatic replies setting from Outlook.|
441441
|Compromised User|Indicates if a user been compromised. The compromise signals can vary based on the attack type.|<ul><li>**Credential Harvest**: The user enters their credentials in the login page (credentials aren't stored by Microsoft).</li><li>**Malware Attachment**: The user opens the file and enables editing in protected view.</li><li>**Link in attachment**: The user opens the attachment, and clicks on the link.</li><li>**Link to Malware**: The user clicks on the link and enters their credentials.</li><li>**Drive by URL**: The user clicks on the link (entering credentials isn't required).</li><li>**OAuth**: The user clicks on the link and accepts to share permissions.</li></ul>|
442-
|Clicked Message Link|Indicates if a user clicked on the message .|The URL in the simulation is unique for each user, which allows individual user activity tracking. Third-party filtering services or email forwarding can lead to false positives. For more information, see [I see clicks or compromise events from users who insist they didn't click the link in the simulation message](attack-simulation-training-faq.md#i-see-clicks-or-compromise-events-from-users-who-insist-they-didnt-click-the-link-in-the-simulation-message).|
443-
|Forwarded Message|Indicates if a user forwarded on the message .||
442+
|Clicked Message Link|Indicates if a user clicked on the message.|The URL in the simulation is unique for each user, which allows individual user activity tracking. Third-party filtering services or email forwarding can lead to false positives. For more information, see [I see clicks or compromise events from users who insist they didn't click the link in the simulation message](attack-simulation-training-faq.md#i-see-clicks-or-compromise-events-from-users-who-insist-they-didnt-click-the-link-in-the-simulation-message).|
443+
|Forwarded Message|Indicates if a user forwarded on the message.||
444444
|Replied to Message|Indicates if an end users has replied on the message.||
445445
|Deleted message|Indicates if an end users has deleted the message.|The signal comes from the Outlook activity of the user. If the user reports the message as phishing, the message might be moved to the Deleted Items folder, which is identified as a deletion.|
446446
|Permissions granted|Indicates if a user shared permissions in an Oauth-based attack.||

0 commit comments

Comments
 (0)