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
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
Microsoft Defender
Smart App Control - Windows 11 22H2 feature promises significant protection from malware
Message
<blockquote data-quote="Andrezj" data-source="post: 1022260" data-attributes="member: 97580"><p>sac is certainly a good idea</p><p></p><p>there are some issues with it:</p><ul> <li data-xf-list-type="ul">sac database and algorithms are obviously not quite ready for prime-time given that sac blocks even microsoft files</li> <li data-xf-list-type="ul">microsoft is not very forthcoming in explaining expected behaviors or configuration of system to have sac permanently enabled - for example, enable windows subsystem for linux and sac blocks it or sac turns itself off</li> <li data-xf-list-type="ul">the requirement of a clean install makes perfect sense, but most users will not accept this - microsoft appears unwilling to budge on this</li> <li data-xf-list-type="ul">there is no way to create "allow" exceptions, and again, most users will not accept this requirement - again microsoft is not going to budge on this</li> <li data-xf-list-type="ul">the microsoft database (e.g. the databases queried by microsoft defender\smartscreen) already includes reputation scores of all the most popular software already - and yet sac blocks many of such software - because the real strategy microsoft is trying to implement with sac is all files, including dlls and updaters (including created .tmp files in the install sequence) are signed with authenticode</li> <li data-xf-list-type="ul">windows defender\smartscreen can block signed files from authenticode signed files from publishers that are already in the microsoft databases - if those files do not meet criteria such as prevelance and age; it is a guess but sac is probably doing the same ( no details from microsoft)</li> <li data-xf-list-type="ul">given microsoft's handling of many initiatives - of starting something to only complete it partially and then either stop or just put into maintenance - does not inspire confidence because sac is one of those microsoft intitiatives that appears susceptible to the "microsoft method"</li> </ul></blockquote><p></p>
[QUOTE="Andrezj, post: 1022260, member: 97580"] sac is certainly a good idea there are some issues with it: [LIST] [*]sac database and algorithms are obviously not quite ready for prime-time given that sac blocks even microsoft files [*]microsoft is not very forthcoming in explaining expected behaviors or configuration of system to have sac permanently enabled - for example, enable windows subsystem for linux and sac blocks it or sac turns itself off [*]the requirement of a clean install makes perfect sense, but most users will not accept this - microsoft appears unwilling to budge on this [*]there is no way to create "allow" exceptions, and again, most users will not accept this requirement - again microsoft is not going to budge on this [*]the microsoft database (e.g. the databases queried by microsoft defender\smartscreen) already includes reputation scores of all the most popular software already - and yet sac blocks many of such software - because the real strategy microsoft is trying to implement with sac is all files, including dlls and updaters (including created .tmp files in the install sequence) are signed with authenticode [*]windows defender\smartscreen can block signed files from authenticode signed files from publishers that are already in the microsoft databases - if those files do not meet criteria such as prevelance and age; it is a guess but sac is probably doing the same ( no details from microsoft) [*]given microsoft's handling of many initiatives - of starting something to only complete it partially and then either stop or just put into maintenance - does not inspire confidence because sac is one of those microsoft intitiatives that appears susceptible to the "microsoft method" [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Top