Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="509322" data-source="post: 771017"><p>PoSh = versions 1 thru 5. 6 is in beta right now.</p><p>PoSh v2.0 has weak protections because Microsoft didn't develop it with security in mind in the first place.</p><p>PoSh v3 - 5, Microsoft has serviced because of numerous reports of security problems. Microsoft has done a bare minimum job at improving security. Of course the whole point is to make PoSh available, but make it safe. That is an oxymoron - unless Microsoft collects it all to know it all and then patches it all. The face of stupidity.</p><p>PoSh v2.0 stupidly remains installed on Windows by default for backwards compatibility\legacy reasons.</p><p>PoSh code\commandlets are not universal across all versions of PoSh. So a cmdlet on v5.0 cannot automatically be used in v2.0.</p><p>However, v2.0 can be used maliciously if it is installed and active on Windows.</p><p>PoSh Constrained Language Mode (v5.0) or _pspolicy as an environmental variable are good security. However, v2.0 and other methods can be used to disable Constrained Language Mode. Therefore, just uninstall v2.0.</p><p>Disabling PoSh and wscript makes missing ASR rules in Exploit Guard a moot point.</p><p>Microsoft Windows spaghetti security.</p></blockquote><p></p>
[QUOTE="509322, post: 771017"] PoSh = versions 1 thru 5. 6 is in beta right now. PoSh v2.0 has weak protections because Microsoft didn't develop it with security in mind in the first place. PoSh v3 - 5, Microsoft has serviced because of numerous reports of security problems. Microsoft has done a bare minimum job at improving security. Of course the whole point is to make PoSh available, but make it safe. That is an oxymoron - unless Microsoft collects it all to know it all and then patches it all. The face of stupidity. PoSh v2.0 stupidly remains installed on Windows by default for backwards compatibility\legacy reasons. PoSh code\commandlets are not universal across all versions of PoSh. So a cmdlet on v5.0 cannot automatically be used in v2.0. However, v2.0 can be used maliciously if it is installed and active on Windows. PoSh Constrained Language Mode (v5.0) or _pspolicy as an environmental variable are good security. However, v2.0 and other methods can be used to disable Constrained Language Mode. Therefore, just uninstall v2.0. Disabling PoSh and wscript makes missing ASR rules in Exploit Guard a moot point. Microsoft Windows spaghetti security. [/QUOTE]
Insert quotes…
Verification
Post reply
Top