$CrowdStrike (CRWD.US)$ are they going to be responsible for...
$CrowdStrike(CRWD.US$ are they going to be responsible for the loss.
Disclaimer: Community is offered by Moomoo Technologies Inc. and is for educational purposes only.
Read more
Comment
Sign in to post a comment
Ken Griffin Charity : Nope
Wenjing Zhu : Scotiabank current outages in Canada. Not sure it related to CRWD. Anyone know about it?
Money Thrill : If you are a customer and definitely need good security, it is rational not to look for problems with CrowdStrike without any considerations, i suppose? I would be careful because every company has software problems sometimes![undefined [undefined]](https://static.moomoo.com/nnq/emoji/static/image/default/default-black.png?imageMogr2/thumbnail/36x36)
![undefined [undefined]](https://static.moomoo.com/nnq/emoji/static/image/default/default-black.png?imageMogr2/thumbnail/36x36)
LELT : Nope. Protected and limited to liabilities as per agreement
888huat888 : They will be responsible for sure either short or long term
JIAYEN505 : Loss. Cover by Insurance. Security Contract has been signed still continues. Not affecting revenues.
LELT 888huat888 : Loss Operation is on Customers and not CrowdStrike. Therefore those customers had not bought insurance, it's their loss. How many days more articles and some traders trying to confuse the market
888huat888 LELT : Man made mistake shouldn’t be cover by insurance. Even if so, I find that in long term or near future client will leave them and revenue will drop. Thus, the company market share will fall eventually over time
LELT 888huat888 : If the vendor is the best, if customers left and stick to a lesser one, your risk of hacked will be higher and the cost will equally be enormous.FYI, after the outage, Microsoft still standby CrowdStrike
28282828 : Even there is agreement you cant run away if you are found guilty of negligence or anything else. So there is possibility of liability. CRWD can easily pay. More concern is the loss of trust and lose customers as customers learn from this mistake
View more comments...