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
Security
Guides - Privacy & Security Tips
Windows Home/Pro owner? Use Software Restriction Policies!
Message
<blockquote data-quote="Andy Ful" data-source="post: 1005918" data-attributes="member: 32260"><p>After some experiments, I managed to spoil the SAC protection. Windows Security Center shows that SAC is ON, but I can run anything I want. The files are checked by SAC and violate code integrity, but SAC does not block them. It thinks that policies are in auditing mode. I deleted all SAC policies and applied my custom policy very similar to the base policy of SAC, but with a different GUID.</p><p></p><p>[ATTACH=full]269633[/ATTACH]</p><p></p><p>[ATTACH=full]269634[/ATTACH]</p><p></p><p>To skirt around SAC, the Trusted Installer privileges are required. The binary policy file was not configured to audit mode and normally blocks executables.</p><p>A similar effect can be forced by removing SAC policies (no WDAC/SAC policies at all). In this case, Event Log does not log CodeIntegrity events.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 1005918, member: 32260"] After some experiments, I managed to spoil the SAC protection. Windows Security Center shows that SAC is ON, but I can run anything I want. The files are checked by SAC and violate code integrity, but SAC does not block them. It thinks that policies are in auditing mode. I deleted all SAC policies and applied my custom policy very similar to the base policy of SAC, but with a different GUID. [ATTACH type="full" alt="1664484474827.png"]269633[/ATTACH] [ATTACH type="full" alt="1664484520714.png"]269634[/ATTACH] To skirt around SAC, the Trusted Installer privileges are required. The binary policy file was not configured to audit mode and normally blocks executables. A similar effect can be forced by removing SAC policies (no WDAC/SAC policies at all). In this case, Event Log does not log CodeIntegrity events. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
