Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
itvision.altervista.org
Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
1–10 of 55 posts
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#2Like monitoring for an unknown application doing esoteric things?
I presume there's some sort of security software in this space for servers
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#3The problem is, Linux antivirus does not really exist.
Granted, there is some software that will scan your files for known signatures - but those signatures are for Win/Mac malware, which solves a completely different problem.
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#4Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#5Are there any anti virus for Linux that does that heuristic type scanning that you see on windows? Like monitoring for an unknown application doing esoteric things? I presume there's some sort of security software in this space for servers
Would be interesting to see a benchmark/study evaluating it as a desktop antivirus - but arguably any server-side malware (which I assume is the majority for Linux today) also apply for a large part of Linux workstations.
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#6> Many proprietary applications can only be successfully installed under sudo or the root account which is a nice and easy way to compromise a computer.
This isn't even worded very well for the common threat vector in this cases which is `curl | sudo bash`.
The truth is that the threat actors targeting Linux almost always do so by "living off the land". A lot of those files are benign or customized to the system leaving the common hash identification method of identifing known malicious binaries as a non-starter. Checking compiled libraries and binaries for sub-classes of behavior also doesn't get very far due to the wide variance of versions across different distributions and customizations done by different administrators.
There are a lot of ways to detect or preventing those changes to the system that are actively deployed (none of which are an anti-virus).
There is a chance that true behavior based analysis can provide hints towards compromise and all the BPF tooling around that makes it a potentially promising lead, but no anti-virus I'm aware of is doing that while other auditing tools are.
There are also a lot of risks with an anti-virus itself. To be useful it needs to be deep in the kernel, above root permissions watching everything. Usually these are proprietary and all the major anti-virus names have had security issues in the past. Un-audited proprietary code running inside the Linux kernel is always a sketchy proposition.
Which leads us back to the common conclusion that no, Linux does not need an anti-virus. They don't solve any of the security problems mentioned and will consume a large amount of system resources to accomplish nothing.
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#7I don't think McAfee will mitigate this scenario.
In my experience antivirus programs are so painful and slow that I would accept almost any inconvenience to avoid using them, for example, doing development on air-gapped VMs or even separate physical machines for web browsing, email, and development.
For example, every 'npm install foo' command creates thousands of files, in one specific case introducing a virus scan on each one turned a 10s install into a 5 minute one.
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#8> As you can see, having a decent antivirus in Linux is not that a crazy idea.
Well, actually, it is far from obvious. Antivirus software even on Windows is commonly the thing that makes the system more vulnerable, not less. This page however uses the word "antivirus" as "a magical piece of software that protects the computer against viruses". How does it do that?
The idea that to fix a security issue you should install an additional program which "increases" security is dubious.
The problems listed on the page are real and we should tackle them. However, I don't think that an "antivirus" is the right solution. Instead security should be treated in a systematic way, not something that you add to a system, after it's done. I think we should invest in, among others, sandboxing techniques, move away from Xorg, write system software in memory-safe languages.
Security is not an app to be installed. It's an architectural problem.
It's also ironic that most of the points listed on the page apply equally well to antivirus software. Namely, are distro maintainers qualified to verify antivirus code? What if an antivirus gets compromised? An open source antivirus could also get code submissions with cleverly hidden backdoors. And what if it's proprietary? (Most of them are.) They also commonly run with elevated privileges (the point about sudo).
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#9This blog post needs to show how an anti-virus would protect against any of the threats it's talked about. The one that an anti-virus might catch is this: > Many proprietary applications can only be successfully installed under sudo or the root account which is a nice and easy way to compromise a computer. This isn't even worded very well for the common threat vector in this cases which is `curl | sudo bash`. The tru…
Many Windows AV solutions feature behavioral analysis or sandbox. Even analyzing API calls in many cases is enough to identify something you are not really content with. For instance a simplistic image viewer which opens internet connections and fetches data from the net ... that sounds weird, right? Or calls exec() on some weird strings.
Re: Linux Myths Series: Linux Doesn't Need an Antivirus (2020)
#10This blog post needs to show how an anti-virus would protect against any of the threats it's talked about. The one that an anti-virus might catch is this: > Many proprietary applications can only be successfully installed under sudo or the root account which is a nice and easy way to compromise a computer. This isn't even worded very well for the common threat vector in this cases which is `curl | sudo bash`. The tru…
However, what comes to mind as a relatively easy win with real gains for a large part of Linux desktops would be a global scanner for hostile npm/pip/etc packages. To catch typosquatters, takeovers etc of dependencies.
A lot can be inherited or borrowed from existing implementations.