Skip to content

Commit 190b523

Browse files
authored
Remove link to blog post from exploit protection reference
Removed a link to a blog post about hardening Windows 10 from the exploit protection reference.
1 parent ea5aef1 commit 190b523

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

defender-endpoint/exploit-protection-reference.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -252,7 +252,7 @@ Block untrusted fonts mitigates the risk of a flaw in font parsing leading to th
252252

253253
This mitigation is implemented within GDI, which validates the location of the file. If the file isn't in the system fonts directory, the font won't load for parsing and the call will fail.
254254

255-
This mitigation is in addition to the built-in mitigation provided in Windows 10 1607 and later, and Windows 11, which moves font parsing out of the kernel and into a user-mode app container. Any exploit based on font parsing, as a result, happens in a sandboxed and isolated context, which reduces the risk significantly. For details on this mitigation, see the blog [Hardening Windows 10 with zero-day exploit mitigations](https://www.microsoft.com/security/blog/2017/01/13/hardening-windows-10-with-zero-day-exploit-mitigations/).
255+
This mitigation is in addition to the built-in mitigation provided in Windows 10 1607 and later, and Windows 11, which moves font parsing out of the kernel and into a user-mode app container. Any exploit based on font parsing, as a result, happens in a sandboxed and isolated context, which reduces the risk significantly.
256256

257257
### Compatibility considerations
258258

0 commit comments

Comments
 (0)