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="Andy Ful" data-source="post: 828836" data-attributes="member: 32260"><p>I thought that the main issue of the setup based on WD Application Guard + "Trust apps with good reputation" feature, would be the lack of whitelisting in the UserSpace.</p><p>But, it seems that after a few-days of bypassing this protection via forced SmartScreen (see point 6. above), <strong>Windows Defender learns (locally) that application is safe</strong>, and it can be run normally without blocking by Application Guard. This is usually limited to a particular computer until the application will gain sufficient reputation to be accepted as safe in the cloud.</p><p></p><p>Edit.</p><p>Applying the above WD Application Guard policies on <strong>Windows Home ver. 1903</strong> is very simple. The predefined file <span style="color: rgb(0, 168, 133)"><strong>SIPolicy.p7b</strong></span> has to be copied with admin rights into the folder <span style="color: rgb(0, 168, 133)"><strong>C:\Windows\System32\CodeIntegrity,</strong></span> and the computer must be rebooted.</p><p>If the user wants to unload the policies, then the file SIPolicy.p7b can be simply renamed or removed and the computer rebooted. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite135" alt=":giggle:" title="Giggle :giggle:" loading="lazy" data-shortname=":giggle:" /> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite130" alt="(y)" title="Thumbs up (y)" loading="lazy" data-shortname="(y)" /></p></blockquote><p></p>
[QUOTE="Andy Ful, post: 828836, member: 32260"] I thought that the main issue of the setup based on WD Application Guard + "Trust apps with good reputation" feature, would be the lack of whitelisting in the UserSpace. But, it seems that after a few-days of bypassing this protection via forced SmartScreen (see point 6. above), [B]Windows Defender learns (locally) that application is safe[/B], and it can be run normally without blocking by Application Guard. This is usually limited to a particular computer until the application will gain sufficient reputation to be accepted as safe in the cloud. Edit. Applying the above WD Application Guard policies on [B]Windows Home ver. 1903[/B] is very simple. The predefined file [COLOR=rgb(0, 168, 133)][B]SIPolicy.p7b[/B][/COLOR] has to be copied with admin rights into the folder [COLOR=rgb(0, 168, 133)][B]C:\Windows\System32\CodeIntegrity,[/B][/COLOR] and the computer must be rebooted. If the user wants to unload the policies, then the file SIPolicy.p7b can be simply renamed or removed and the computer rebooted. :giggle: (y) [/QUOTE]
Insert quotes…
Verification
Post reply
Top