Skip to content

Commit be5f512

Browse files
committed
updates
1 parent b459b21 commit be5f512

File tree

3 files changed

+3
-45
lines changed

3 files changed

+3
-45
lines changed

defender-endpoint/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -386,8 +386,6 @@
386386
items:
387387
- name: Safe deployment practices
388388
href: mde-sdp-strategy.md
389-
- name: Manage behavior safely in your organization
390-
href: manage-maintain-mde-guide.md
391389
- name: Defender for Endpoint Security Operations Guide
392390
href: mde-sec-ops-guide.md
393391
- name: Troubleshoot

defender-endpoint/manage-maintain-mde-guide.md

Lines changed: 0 additions & 40 deletions
This file was deleted.

defender-endpoint/mde-sdp-strategy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Defender for Endpoint applies SDP to two distinct update mechanisms:
2727
- Software and driver updates that are updated monthly (can potentially update kernel-mode components).
2828
- Security intelligence and detection logic updates that can be updated multiple times a day (updates only apply to user-mode components).
2929

30-
## Monthly SDP software and drivers updates
30+
## Monthly SDP software and driver updates
3131

3232
Defender for Endpoint releases monthly software and driver updates that add new functionality, improve existing features, and resolve bugs.
3333

@@ -49,7 +49,7 @@ Once internal testing is successfully completed, Microsoft then releases the upd
4949

5050
In addition to Microsoft’s safe deployment practices, organizations can also manage monthly updates with their own safe deployment practices through various controls:
5151

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.
5353
- Apply patch management software and practices for security component updates that can also arrive in the form of monthly Latest Cumulative Updates (LCUs).
5454
- 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.
5555

@@ -68,7 +68,7 @@ Similar to the process for software and driver updates, Microsoft ships security
6868

6969
### Customer SDP for daily updates
7070

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:
7272

7373
- Stage updates through [corporate networks](microsoft-defender-antivirus-ring-deployment-group-policy-network-share.md#setting-up-the-pilot-environment) or software management solutions.
7474
- 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

Comments
 (0)