Reply to thread

Message

<blockquote data-quote="Andy Ful" data-source="post: 968080" data-attributes="member: 32260">The idea of protecting Svchost is natural&nbsp; (but hard to apply) to the Enterprise environment. Such an environment has so big attack surface that one has to assume serious chances of breach. That is why the protection is focused on postinfection remediation, anti-exploit mitigations, protecting credentials, preventing lateral movement, etc.Such thinking is not adequate in the home environment because:<ol>
<li data-xf-list-type="ol">The attack surface is much smaller.</li>
<li data-xf-list-type="ol">The features loved by attackers are rarely needed by home users.</li>
<li data-xf-list-type="ol">The infection rate is much smaller compared to Enterprises.</li>
<li data-xf-list-type="ol">The system and software are often well patched.</li>
<li data-xf-list-type="ol">The attacks originating from the home network are very rare.</li>
</ol>That is why home users can focus on initial attack vectors and do not bother much about what will happen after infection.</blockquote>

[QUOTE="Andy Ful, post: 968080, member: 32260"] The idea of protecting Svchost is natural (but hard to apply) to the Enterprise environment. Such an environment has so big attack surface that one has to assume serious chances of breach. That is why the protection is focused on postinfection remediation, anti-exploit mitigations, protecting credentials, preventing lateral movement, etc. Such thinking is not adequate in the home environment because: [LIST=1] [*]The attack surface is much smaller. [*]The features loved by attackers are rarely needed by home users. [*]The infection rate is much smaller compared to Enterprises. [*]The system and software are often well patched. [*]The attacks originating from the home network are very rare. [/LIST] [B]That is why home users can focus on initial attack vectors and do not bother much about what will happen after infection.[/B] [/QUOTE]

Verification