CRWD: Certainly no positive impact in the short term. They will HAVE to provide all sorts of benefits on pricing, discounts, etc. to soothe any impact in the short term. Their security game is SO strong, I have a feeling this won't have much in the way of legs in the long term. Class action lawsuit is a given, impact unknown. Will likely come from the business sector and stockholders like us. When it comes down to it, all companies are vulnerable to things like this ... unfortunate for them to be sure. Hopefully they provide better staging in the future before allowing these things to happen.
In the financial sector, Microsoft Updates in the middle of the night were the bane of us all. They were always opening, closing, augmenting ports, security, settings that would take down our branches/tellers. I was caught between the auditors/regulators saying we had to install critical patches as soon as they were released and dealing with downtime when these patches closed ports that we wanted open or changed settings that disrupted communications. We can only be so quick with staging. We found it much safer to lag the update, stage as fast as we could and then keep our ear to the ground from other financials who installed the patch/updates. As far as the auditors knew, the updates were performed as released. I did have policy language stating I could choose to wait a period of time if I felt the risk of loading outweighed the benefits due to risk. :)
In any event, go PANW. I have equal exposure to both and have been looking to add CRWD in other accounts. Maybe I'll pivot to PANW instead though I'll be honest in saying I don't know how much overlap there is between the two. I'll have to look into that.
Thanks for the posts.
TJ |
