Reply to thread

Message

<blockquote data-quote="Windows_Security" data-source="post: 728028" data-attributes="member: 50782">WHY USE OS_ARMOR?Malware writers only use a limited number of hacking techniques (when we exclude user errors like phishing and social engineering). They always try to gain access to Windows build in shells to acquire higher priveledges, drop code, survice re-boot and connect/redirect internet traffic to a controlled server.Some say it is impossible to fight exploits, because exploits are based on progam errors of which the vendors did not&nbsp; know their software had them. But with the improvemenst in Memory hardening, code control and (C++) compilers Windows 10 is a tough cookie to beat. Windows 10 with all Windows Defender features enabled is pretty hard to break in.Luckily (for malware writers) Microsoft thought of a way to nullify all these security improvements by providing (new or enhanced) command and script interpretators in Windows itself. When old dynamic code platforms were abondanned (Active-X, HTML application, NTVDM) new ones are quickly introduced (dotNet, Powershell, Windows Management Instrumentation) to give hackers access to your PC.Malware tend to use what is already there (from exploit-kits to windows build-in shells), so OS-Armor blocking access to command shells and script interpretors&nbsp; and filtering command lines on known exploit tricks reduces the chances of being victim of malware using an exploit to near zero. The beauty of OS_Armor is that it does not try to prevent exploits, but limits gaining access to Windows build-in shell after an exploit is applied.That is why I recommend using OS_Armor in default settings</blockquote>

[QUOTE="Windows_Security, post: 728028, member: 50782"] [B]WHY USE OS_ARMOR?[/B] Malware writers only use a limited number of hacking techniques (when we exclude user errors like phishing and social engineering). They always try to gain access to Windows build in shells to acquire higher priveledges, drop code, survice re-boot and connect/redirect internet traffic to a controlled server. Some say it is impossible to fight exploits, because exploits are based on progam errors of which the vendors did not know their software had them. But with the improvemenst in Memory hardening, code control and (C++) compilers Windows 10 is a tough cookie to beat. Windows 10 with all Windows Defender features enabled is pretty hard to break in. Luckily (for malware writers) Microsoft thought of a way to nullify all these security improvements by providing (new or enhanced) command and script interpretators in Windows itself. When old dynamic code platforms were abondanned (Active-X, HTML application, NTVDM) new ones are quickly introduced (dotNet, Powershell, Windows Management Instrumentation) to give hackers access to your PC. Malware tend to use what is already there (from exploit-kits to windows build-in shells), so OS-Armor blocking access to command shells and script interpretors and filtering command lines on known exploit tricks reduces the chances of being victim of malware using an exploit to near zero. The beauty of OS_Armor is that it does not try to prevent exploits, but limits gaining access to Windows build-in shell after an exploit is applied. That is why I recommend using OS_Armor in default settings [/QUOTE]

Verification