Skip to content

Commit 47df5da

Browse files
committed
updates
1 parent 3327953 commit 47df5da

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

defender-for-iot/mde-deployment-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,15 +25,15 @@ MDE agents offer various discovery and security capabilities, such as passive mo
2525

2626
- Server 2019 and computers with Build Version 17763
2727

28-
- Lower operating system versions: Machines with lower operating system versions (e.g., Server 2016) can be onboarded to MDE <!-- does this mean: can be onboarded to an MDE agent OR can still have an MDE agent onboarded to it-->but can't run SENSENDR.
28+
- Lower operating system versions: Machines with lower operating system versions (e.g., Server 2016) can be onboarded to MDE an MDE agent but can't run SENSENDR.
2929

3030
## Passive Monitoring
3131

3232
Passive monitoring involves silently analyzing network traffic using known endpoints and traffic patterns, for example, MDE passively monitors network traffic to discover OT devices.
3333

3434
- Requirement: An MDE agent must be running on the LAN or subnet to be monitored.
3535

36-
- Network traffic type required: the MDE agent needs to receive unicast traffic between<!-- from ... to the --> the discovered OT devices and the device with the agent.<!-- Theo - what does this mean? -->
36+
- Network traffic type required: the MDE agent needs to pass unicast traffic between the discovered OT devices and the agent/ sensor.<!--?-->
3737

3838
:::image type="content" source="media/mde-agent-deployment-guide/mde-agent-deployment-guide-1.png" alt-text="A diagram showing the passive monitoring of a subnet." lightbox="media/mde-agent-deployment-guide/mde-agent-deployment-guide-1.png":::
3939

0 commit comments

Comments
 (0)