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: defender-endpoint/mde-sdp-strategy.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
@@ -27,7 +27,7 @@ Defender for Endpoint applies SDP to two distinct update mechanisms:
27
27
- Software and driver updates that are updated monthly (can potentially update kernel-mode components).
28
28
- Security intelligence and detection logic updates that can be updated multiple times a day (updates only apply to user-mode components).
29
29
30
-
## Monthly SDP software and drivers updates
30
+
## Monthly SDP software and driver updates
31
31
32
32
Defender for Endpoint releases monthly software and driver updates that add new functionality, improve existing features, and resolve bugs.
33
33
@@ -49,7 +49,7 @@ Once internal testing is successfully completed, Microsoft then releases the upd
49
49
50
50
In addition to Microsoft’s safe deployment practices, organizations can also manage monthly updates with their own safe deployment practices through various controls:
51
51
52
-
-[Create a custom gradual rollout process for Microsoft Defender updates](configure-updates.md) to control the delivery of agent updates to their devices. Customers can control the rings that are assigned to their device group and when each ring receive updates. For example, place lower-valued assets in earlier rings and higher-valued assets in later rings.
52
+
-[Create a custom gradual rollout process for Microsoft Defender updates](configure-updates.md) to control the delivery of agent updates to their devices. Customers can control the rings that are assigned to their device group and when each ring receives updates. For example, place lower-valued assets in earlier rings and higher-valued assets in later rings.
53
53
- Apply patch management software and practices for security component updates that can also arrive in the form of monthly Latest Cumulative Updates (LCUs).
54
54
- Use [rollback controls](microsoft-defender-antivirus-updates.md#how-to-roll-back-an-update) or automated rollback options to revert or reset components to a last known good state.
55
55
@@ -68,7 +68,7 @@ Similar to the process for software and driver updates, Microsoft ships security
68
68
69
69
### Customer SDP for daily updates
70
70
71
-
Customers can also manage security intelligence updates with their own safe deployment policies through various controls:
71
+
Customers can also manage security intelligence updates with their own safe deployment policies through various measures:
72
72
73
73
- Stage updates through [corporate networks](microsoft-defender-antivirus-ring-deployment-group-policy-network-share.md#setting-up-the-pilot-environment) or software management solutions.
74
74
- Apply updates at a lower frequency for critical systems. Daily releases can be applied at a lower frequency for certain device groups, including servers critical to running your infrastructure.
0 commit comments