Microsoft announced Vulnerability Shielding for Defender at Ignite. What does it actually do before a permanent fix is deployed, and what should admins watch for?
How is Defender Vulnerability Shielding supposed to work while patches are pending?
Answers
Think of it as a temporary mitigation, not a replacement for patching. The Risk Reduction Agent in Microsoft Perception identifies vulnerabilities and recommends shielding plans for an admin to review and approve. The shields are meant to retire automatically once the permanent patch is fully deployed.
During an active attack, Defender's Attack Disruption can also apply shielding controls automatically to help prevent exploitation through additional paths. That automatic response is a different path from an admin reviewing a recommended plan.
Reply to this answer
The practical question is what each shield might interrupt. Admins can review the expected impact, exclude devices and roll back shields, so those controls are worth checking before approving a plan. The feature is in public preview, and how well it balances protection with normal operations in production remains to be seen.
Reply to this answer
Check the scope before assuming it covers every missing patch. Initial support is for server-side remote code execution vulnerabilities, not a general promise to shield every vulnerability on every device.
Reply to this answer
Licensing is still a question in the available announcement details. Don't budget for it or assume it's included in an existing Defender subscription without checking Microsoft's current licensing information.
Reply to this answer
Add your answer
Answers are reviewed before publication.
c.938!plovercrank:
Good distinction. Automatic controls during an attack sound like they'll need attention too, especially on sensitive systems.