Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 690653" data-attributes="member: 32260">It seems that the Attack Surface Reduction introduced in Windows 10 Fall Creators Update works also in Windows Home version. It can be configured when using PowerShell.The bad news is that the rule &#039;Block Office applications from creating child processes&#039; does not work with Microsoft Office 2007 and Open Office. It works well with Microsoft Office 2016.So it is possible, that the below ASR features:<ul>
<li data-xf-list-type="ul">Block Office applications from creating child processes</li>
<li data-xf-list-type="ul">Block Office applications from creating executable content</li>
<li data-xf-list-type="ul">Block Office applications from injecting into other processes</li>
<li data-xf-list-type="ul">Block Win32 imports from Macro code in Office</li>
</ul>will work only with the office software still supported by Microsoft (MS Office 2010, 2013, 2016).Unfortunately, I cannot test it for MS Office 2010 and MS Office 2013. I someone can then please let me know.</blockquote>

[QUOTE="Andy Ful, post: 690653, member: 32260"] It seems that the Attack Surface Reduction introduced in Windows 10 Fall Creators Update works also in Windows Home version. It can be configured when using PowerShell. The bad news is that the rule 'Block Office applications from creating child processes' does not work with Microsoft Office 2007 and Open Office. It works well with Microsoft Office 2016. So it is possible, that the below ASR features: [LIST] [*]Block Office applications from creating child processes [*]Block Office applications from creating executable content [*]Block Office applications from injecting into other processes [*]Block Win32 imports from Macro code in Office [/LIST] will work only with the office software still supported by Microsoft (MS Office 2010, 2013, 2016). Unfortunately, I cannot test it for MS Office 2010 and MS Office 2013. I someone can then please let me know. [/QUOTE]

Verification