Hacker News new | past | comments | ask | show | jobs | submit login

Does CS actually offer any real protection? I always thought it was just feel-good software, that Windows had caught up to separating permissions since after XP or so. Either one is lying/scamming, but which one?



> Does CS actually offer any real protection? I always thought it was just feel-good software, that Windows had caught up to separating permissions since after XP or so. Either one is lying/scamming, but which one?

Our ZScaler rep (basically, they technically work for us) come out with massive impressive looking numbers of the thousands of threats they detect and eliminate every month

Oddly before we had zscaler we didn't seem to have any actual problems. Now we have it and while we have lots of zscaler caused problems around performance and location, we still don't have any actual problems.

Feels very much like a tiger repelling rock. But I'm sure the corporate hospitality is fun.


AFAIK, most of the people I know that deploy CrowdStrike (including us) just do it to check a box for audits and certifications. They don't care much about protections and will happily add exceptions on places where it gives problems (and that's a lot of places)


What a dream business.


It's not about checking the boxes themselves, but the shifting of liability that enables. Those security companies are paid well not for actually providing security, but for providing a way to say, "we're not at fault, we adhered to the best security practices, there's nothing we could've done to prevent the problem".


So in essence just a flavor of insurance?

Shouldn't that hit Crowdstrike's stock price much more than it has then? (so far I see ~11% down which is definitely a lot but it looks like they will survive).


Not quite. Insurance is a product that provides compensation in the event of loss. Deploying CrowdStrike with an eye toward enterprise risk management falls under one of either changing behaviors or modifying outcomes (or perhaps both).


They are paying with reputation and liability, no?

If the idea is "we'll hire Crowdstrike for CYA" when things like this happen, the blame is on CS and they pay with their reputation.


Pay for what exactly though? Cybersecurity incidents result in material loss, and someone somewhere needs to provide dollars for the accrued costs. Reputation can't do that, particularly when legal liability (or, hell, culpability) is involved.

EDR deployment is an outcome-modifying measure, usually required as underwritten in a cybersecurity insurance policy for it to be in force. It isn't itself insurance.


Not at all like insurance, because they don’t have to pay out at all when things go wrong.


In a way it's the new "nobody ever got fired for buying IBM".


You're so right. Pay us ludicrous sums to make your auditors feel good. Crazy.


So much of regulation is just a round-about to creating business for regulatory compliance.


Good for profits, but it bet there are some employees who feel a distinct lack of joy about their work.


Just adding my two cents: I work as a pentester and arguably all of my colleagues agree that engagements where Crowdstrike is deployed are the worst because it's impossible to bypass.


It definitely isn't impossible to bypass. It gets bypassed all the time, even publicly. There's like 80 different CrowdStrike bypass tricks that have been published at some point. It's hard to bypass and it takes skill, and yes it's the best EDR, but it's not the best solution - the best solution is an architecture where bypassing the EDR doesn't mean you get to own the network.

An attacker that's using a 0 day to get into a privileged section in a properly set up network is not going to be stopped by CrowdStrike.


Or you're a pentester playing 4D chess with your comment.

Or a CS salesperson playing 3D chess with your comment.

If so, well played!


By “impossible to bypass” are you meaning that it provides good security? Or that it makes pen testing harder because you need to be able to temporarily bypass it in order to do your test?


The first. AV evasion is a whole discipline in itself and it can be anything from trivial to borderline impossible. Crowdstrike definitely plays in the champions league.


[flagged]


I don't appreciate your aggressive tone. Which AV is better in your opinion? Are there a lot?


You should be asking how to get through, not what competitor is better. You totally sound like a marketing rep now.


That's not what the discussion was about. If you don't think crowdstrike qualifies as one of the best, justify your opinion.


Best not to respond to trolls.


How can one gets through? I'm sure the knowledge costs gold though.


valuable 2 cents

is there any writeups from the pentesting side of things that we can read to learn more?


I’ll say this: I did a small lab in college for a hardware security class and I got a scary email from IT because CrowdStrike noticed there was some program using speculative execution/cache invalidation to leak data on my account - they recognized my small scale example leaking a couple of bytes. Pretty impressive to be honest.


Did you have CrowdStrike installed on your personal machine, or did they detect it over the network somehow?


We ran our code on our own accounts on the school’s system.


Those able to write and use FUD malware do not create public documentation. Crowdstrike is not impossible to bypass, but for a junior security journeyman known as a pentester, working for corporate interests with no budget and absurdly limited scopes under contract for n-hours a week for 3 weeks will never be able to do anything as simple as an EDR evasion, however if you wish to actually learn the basics the common practitioner of this art please go study the offsec evasion class. Then go read a lot of code and syscall documentation and learn assembly.


I don't understand why you were downvoted. I'm interested in what you said. When you mentioned offsec evasion class, is this what you mean? It seems pretty advanced.

https://www.offsec.com/courses/pen-300/

What kind of code should I read? Actually, let me ask this, what kind of code should I write first before diving into this kind of evasion technique? I feel I need to write some small Windows system software like duplicating Process Explorer, to get familiar with Win32 programming and Windows system programming, but I could be wrong?

I think I do have a study path, but it's full of gap. I work as a data engineer -- the kind that I wouldn't even bother to call myself engineer /s


I know quite a few offensive security pros that are way better than I will ever be at breaking into systems and evading detections that can only barely program anything beyond simple python scripts.

It’s a great goal to eventually learn everything, but knowing the correct tools and techniques and how and when to use them most effectively are very different skillsets from discovering new vulnerabilities or writing new exploit code and you can start at any of them.

Compare for instance a physiologist, a gymnastics coach, and an Olympic gymnast. They all “know how the human body works” but in very different ways and who you’d go to for expertise depends on the context.

Similarly just start with whatever part you are most interested in. If you want to know the techniques and tools you can web search and find lots of details.

If you want to know how best to use them you should set up vulnerable machines (or find a relevant CTF) and practice. If you want to understand how they were discovered and how people find new ones you should read writeups from places like Project Zero that do that kind of research. If you’re interested in writing your own then yes you probably need to learn some system programming. If you enjoy the field you can expand your knowledge base.


EDR vendors are generally lying unless they tell you anything but "install us if you want to pass certification".


My contacts abroad are saying "that software US government mandated us to install on our clients and servers to do business with US companies is crashing our machines".

When did Crowdstrike get this gold standard super seal of approval? What could they be referring to?


[flagged]


> if it's not 100% secure

It's 100% broken though...

I guarantee you that the damage caused by Crowdstrike today will significantly outweigh any security benefits/savings that using their software might have had over the years.


The benefits include

1) Nice trips to golf courses before contract renewal

2) Nice meals at fancy restaurants before contract renewal

3) Someone for the CTO to blame when something goes wrong


Nah, more like your security/usability/reliability tradeoff needs to be better.


As a redteamer I guarantee you that a Windows endpoint without EDR is caviar for us...


Are there publicly known exploits which allow RCE or data extraction on a default windows installation?


* SMB encryption or signing not enforced

* NTLM/NTLMv1 enabled

* mDNS/llmnr/nbt-ns enabled

* dhcpv6 not controlled

* Privileged account doing plain LDAP (not LDAPS) binds or unencrypted FTP connections

* WPAD not controlled

* lights out interfaces not segregated from business network. Bonus points if its a supermicro which discloses the password hash to unauthenticated users as a design features.

* operational technology not segregated from information technology

* Not a windows bug, but popular on windows: 3rd party services with unquoted exe and uninstall strings, or service executable in a user-writable directory.

I remediate pentests as well as realworld intrusion events and we ALWAYS find one of these as the culprit. An oopsie happening on the public website leading to an intrusion is actually an extreme rarity. It's pretty much always email > standard user > administrator.

I understand not liking EDR or AV but the alternative seems to be just not detecting when this happens. The difference between EDR clients and non-EDR clients is that the non-EDR clients got compromised 2 years ago and only found it today.


Thanks for the list. I got this job as the network administrator at a community bank 2 years ago and 9/9 of these were on/enabled/not secured. I've got it down to only 3/9 (dhcpv6, unquoted exe, operational tech not segregated from info tech). I'm asking for free advise, so feel free to ignore me, but of these three unremediated vectors, which do you see as the culprit most often?


dhcpv6 poisoning is really easy to do with metasploit and creates a MITM scenario. It's also easy to fix (dhcpv6guard at the switch, a domain firewall rule, or a 'prefer ipv4' reg key).

unquoted paths are used to make persistence and are just an indicator of some other compromise. There are some very low impact scripts on github that can take care of it

Network segregation, the big thing I see in financial institutions is the cameras. Each one has its own shitty webserver, chances are the vendor is accessing the NVR with teamviewer and just leaving the computer logged in and unlocked, and none of the involved devices will see any kind of update unless they break. Although I've never had a pentester do anything with this I consider the segment to be haunted.


None of those things require a kernel module with remote code execution to configure properly.


I believe the question was 'in which ways is windows vulnerable by default', and I answered that.

If customers wanted to configure them properly, they could, but they don't. EDR will let them keep all the garbage they seem to love so dearly. It doesn't just check a box, it takes care of many other boxes too.


At work we have two sets of computers. One gets beamed down by our multi-national overlords, loaded with all kinds of compliance software. The other is managed by local IT and only uses windows defender, has some strict group policies applied, BMCs on a separate vlans etc. Both pass audits, for whatever that's worth.


This is the key question for me: is there a way to get [most of] the security benefits of EDR without giving away the keys to the kingdom.


No. If an EDR relies on userland mechanisms to monitor, these userland mechanisms can easily be removed by the malicious process too.


> It's pretty much always email > standard user > administrator

What does this mean?


believe it or not, most users dont run around downloading random screensavers or whatever. Instead they are receiving phish emails, often from trusted contacts who have recently been compromised using the same style of message that they are used to receiving, that give the attacker a foothold on the computer. From there, you can use a commonly available insecure legacy protocol or other privilege escalation technique to gain administrative rights on the device.


standard user: why can't I open this pdf? It says Permission Denied

dumb admin: let me try .... boom game over man


It's the attack path.


>> always email > standard user > administrator

maybe its the boomers that can't give up Outlook? Otherwise they could've migrated everybody to google workspaces or some other web alternative.


You don't need exploits to remotely access and run commands on other systems, steal admin passwords, and destroy data. All the tools to do that are built into Windows. A large part of why security teams like EDR is that it gives them the data to detect abuse of built-in tools and automatically intervene.


Not on a fully patched system. 0-days are relatively rare and fixed pretty quickly by Microsoft.


Remember WannaCry? The vuln it used was patched by MS two months prior the attack. Yet it took the world by storm.


Not sure what you want from me, I simply answered the question. Yes I remember WannaCry.


How is it caviar then?


Not the same poster, but one phase of a typical attack inside a corporate network is lateral movement. You find creds on one system and want to use them to log on to a second system. Often, these creds have administrative privileges on the second system. No vulnerabilities are necessary to perform lateral movement.

Just as an example: you use a mechanism similar to psexec to execute commands on the remote system using the SMB service. If the remote system has a capable EDR, it will shut that down and report the system from which the connection came from to the SOC, perhaps automatically isolate it. If it doesn't, an attacker moves laterally through your entire network with ease in no time until they have domain admin privs.


A key part of breach a network is having a beacon running on their networks, and communicating out, one way or another.

Running beacons with good EDRs is difficult, and has become the most challenging aspect of most red team engagements because of that.

No EDR, everything becomes suddenly super easy.


Anyone who claims CS is nothing but a compliance checkbox has never worked as an actual analyst, of course it's effective...no, dur, its worth 50bn for no reason...god some people are stupid AND loud


Every company I’ve ever worked at has wound up having to install antivirus software to pass audits. The software only ever caused problems and never caught anything. But hey, we passed the audit so we’re good right?


The real scam is the audit.

Many moons ago, I failed a "security audit" because `/sbin/iptables --append INPUT --in-interface lo --jump ACCEPT`

"This leaves the interface completely unfiltered"

Since then, I've not trusted any security expert until I've personally witnessed their competence.


Long time ago I was working for a web hoster, and had to help customers operating web shops to pass audits required for credit card processing.

Doing so regularly involved allowing additonal ciphers for SSL we deemed insecure, and undoing other configurations for hardening the system. Arguing about it is pointless - either you make your system more insecure, or you don't pass the audit. Typically we ended up configuring it in a way that we can easily toggle those two states, and reverted it back to a secure configuration once the customer got their certificate, and flipped it back to insecure when it was time to reapply for the certification.


This tracks for me. PA-DSS was a pain with ssl and early tls... our auditor was telling us to disable just about everything (and he was right) and the gateways took forever to move to anything that wasn't outdated.

Then our dealerships would just disable the configuration anyway.

It's been better in recent years.


The dreaded exposed loopback interface... I'm an (internal) auditor, and I see huge variations in competence. Not sure what to do about it, since most technical people don't want to be in an auditor role.


The companies I had the displeasure of dealing with were basically run by mindless people with a shell script.


I agree completely. It makes me wonder if other engineering disciplines have this same competency issue.


We did this at one place I used to work at. We had lots of Linux systems. We installed clamAV but kept the service disabled. The audit checkbox said “installed” and it fulfilled the checkbox…


Yes, it offers very real protection. Crowdstrike in particular is the best in the market, speaking from experience and having worked with their competitor's products as well and responded to real world compromises.


How did they fail to test such a critical bug then ?

Clearly shows lack of testing.

If intially good, probably culture & products have rotten.

Not fit to be in security domain, if like this.


I think this is more of a failure on the software development side than the domain specific functionality side.


Hubris. Clearly they have no form of internal testing for updates because this should have been caught immediately.


"best in the market"

I think the evidence shows that no, they aren't.


Go buy the second-best in the market then. Red Team would love you to do that.


Yes, from experience, I can say that CS does offer real protection.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: