News for hackers. Stuff that matters.
Re:Leaked documents expose Avast antivirus subsidiary sellin... by the8472 on Monday January 27, 2020 @12:24PM (#22161525)
One issue with all antivirus on windows, including defender, is the performance impact. It seems to be dreadfully single-threaded, or at least make single-threaded workloads even worse. Monitoring CPU use during updates easily shows this, there are periods where a single core is busy with the defender service and nothing else is happening.

Another issue that while microsoft's incentives may be better aligned it still fundamentally is an antivirus and thus an increase in attacksurface. There have been exploits against it[0] and it turned out that it did things with SYSTEM privileges and no sandboxing.

[0] https://bugs.chromium.org/p/project-zero/issues/list?can=1&q...

Re:Leaked documents expose Avast antivirus subsidiary sellin... by BlueTemplar on Monday January 27, 2020 @09:31PM (#22165913)
If only one core is busy, then it shouldn't have much of a performance impact?
Re:Leaked documents expose Avast antivirus subsidiary sellin... by the8472 on Tuesday January 28, 2020 @05:32AM (#22168080)
It's only one core pegged at 100%, practically nothing else, which means it's a sequential workload entirely blocked on defender.
Re:Leaked documents expose Avast antivirus subsidiary sellin... by BlueTemplar on Tuesday January 28, 2020 @04:01PM (#22173977)
Oh, you mean that Defender locks your thread?
Re:Leaked documents expose Avast antivirus subsidiary sellin... by the8472 on Wednesday January 29, 2020 @05:49AM (#22179206)
I don't recall seeing significant locking in the stack samples, just that the scanning happens synchronously during some IO (e.g. closing file handles) and >90% of the CPU cycles are spent on defender. Which effectively boils down to a task that should be IO-bound becoming bottlenecked by waiting on defender.