Most users are infected by ignoring some alerts of security software and still hoping that they will be uninfected.
However, I also miss the possibility of exclusions.
However, I also miss the possibility of exclusions.
Yes it reduces usability; then I have two options, either to use programs allowed by SAC, or to disable SAC and apply MAC with exclusions.But it reduces usability, doesn't it? And it can still be bypassed.
Great news.SAC usability improvement.
SAC can now be toggled ON/OFF from inside the Windows Security app (tested in the Insider Build 26220.7070).
![]()
Windows 11 Insider Build 26220.7070: Faster Recovery, Widgets Redesign, SAC Toggle
Microsoft has shipped Windows 11 Insider Preview Build 26220.7070 (packaged as KB5070300) to the Dev and Beta channels, an incremental but meaningful update that tightens recovery workflows, refines the Widgets user interface, and removes a handful of practical friction points for testers and IT...windowsforum.com
Don't hold your breath, my friend.Waiting for adding "exclusions"; SAC can be disabled to allow installing an app, but after re-enabling, launching such app may be blocked, if not added to exclusions.
With forthcoming "Smart App Control - ON/OFF", when SAC blocks a known-good software update then:Don't hold your breath, my friend.![]()
There is only one type of truly effective default deny. It is the one that the user can never disable - not even in an administrator privileged account.
1. "Users want to use stuff". That might be legal, but it don't make it right - at least not for uneducated, ignorant, wholly dis-inclined and insecure masses.This kind of restriction will certainly create fookery for the hoomans that require abilities in order to maximize effectiveness of said tasks.
There's a global threshold at which the hooman stupid will kill us all.Your not wrong though, it's the only way to fix stupid.
Test this theory after SAC ON/OFF feature is shipped with Windows 11 by:But I think with SAC it might be a little better because of the continuous updating of the cloud white list.
Hypothetical tests allow for any outcome, which does not mean the results you claim are true neither will such a hypothetical test proof you are right.Test this theory after SAC ON/OFF feature is shipped with Windows 11 by:
1. Giving a laptop with SAC enabled to a group of 6 to 18 year olds.
2. Giving a laptop with SAC enabled to a group of adults aged 19 thru 101 (randomly chosen).
Watch the hoomans bypass SAC by simply turning it off whenever they see fit to do s9o because they all want to do unsafe, unhygienic stuff - in other words "Users want to use stuff."
There's nothing hypothetical about that. If I had a dollar for every time someone has asked me how to disable a security to install something that's being blocked I'd be a rich man. That knowledge stems from experience and is common sense as he is not wrong, users do want to use stuff. Especially that age bracket, they know better than everyone at that age.Hypothetical tests allow for any outcome, which does not mean the results you claim are true neither will such a hypothetical test proof you are right.
I can hardly lmagine Microsoft would make such a drastic move (from blacklist to whitelist) when it was not supported by the big data Microsoft gathers with telemetry.
The whole point of the "hypothetical test" is that it replicates real-world hooman behaviors and patterns of behaviors in the wild.Hypothetical tests allow for any outcome, which does not mean the results you claim are true neither will such a hypothetical test proof you are right.
Microsoft is not moving from blacklist to whitelist with regards to SAC.I can hardly imagine Microsoft would make such a drastic move (from blacklist to whitelist) when it was not supported by the big data Microsoft gathers with telemetry.
