Is there a use case for Crowd Strike Falcon on Linux?
Is there a use case for Crowd Strike Falcon on Linux?
How does Linux it self or some other software on Linux address what Crowd Strike is doing for Windows?
E: thanks for the answers :)
You're viewing a single thread.
How does Linux it self or some other software on Linux address what Crowd Strike is doing for Windows?
Well, it usually drops to a black screen and kernel panics, but lately there's been a bit of a push for parity with windows.
The Linux BSOD is quite funny. But reading from Crowd Strike's website the Falcon product is supposed to monitor for breaches(?), so I was curious about what analogs exist in Linux or how the OS it self takes on that role.
Crowdstrike exists for Linux too. In fact, it apparently crashed RHEL and Debian a few months back. That didn't get so much attention.
Falcon seems to be a cross between an antivirus and an intrusion detection system (IDS). There are many antiviruses on Linux, but only one FOSS AV is popular - ClamAV. As for IDS, snort is an example.
But in the true sense, Falcon is much more than just an AV and IDS. It's a way to detect breaches and report it back to CrowdStrike's threat detection and analysis teams. I don't think there exists a proper alternative even in the commercial sector.
I don’t think there exists a proper alternative even in the commercial sector.
There is a handful of vendors and they indeed monitor a ton more than just viruses. The solution we're running at the office monitors pretty much all kinds of logs (dns, dhcp, authentication, network traffic....) and it can lock down clients which are behaving wrongly enough. For example every time I change a hosts file (for a legitimate reason) on my own laptop I get a question from security team if that was intented. And it combines logs/data gathered from different systems to identify potential threats and problematic hosts and that's why our fleet feeds in data from all kinds of devices.
I haven't seen that many different solutions which do this, but the few I've worked with are a bit hit or miss with linux. The current solution has a funny feature where it breaks dpkg if the server doesn't have certain things installed (which are not depencies on the packet itself). And they eat up a pretty decent chunk of CPU-cycles and RAM while running. But apparently someone has done the math and decided that it's worth the additional capacity, it's outside my pay range so I just install whatever I'm told to.
That's a BSOD for DRM failures I think, not a generic BSOD like on Windows.
Systemd also added systemd-bsod, but it’s for boot failures.