4 ms·
I specifically have experience with Kaseya. I kicked and screamed to get us off of it, the IT people insisted it was top notch. So when I became CFO I fired th
by SV_BubbleTime 5y ago
I specifically have experience with Kaseya. I kicked and screamed to get us off of it, the IT people insisted it was top notch.
So when I became CFO I fired them (outside company), not just for this, but it didn’t help.
It’s bad software. 24/7 full low level access is exactly what it is. We had an add on that stored admin credentials in a JSON… so looking back on that, it seems this should have happened sooner.
- daniellarusso 5y agoThe craziest part to me was their pushing of the vPro integrations.
- SV_BubbleTime 5y agoI dumped Intel servers for Epyc and Kaseya entirely. So, I’m looking pretty good with those decisions.
- briefcomment 5y agoDid you think it was an unintentional technical liability, or did you think it was intentional?
- SV_BubbleTime 5y agoUnintentional I think. If it was intentional I think things would have looked better on the surface.
- adolph 5y agoAdditional information about the Kaseya angle: https://doublepulsar.com/kaseya-supply-chain-attack-delivers-mass-ransomware-event-to-us-companies-76e4ec6ec64b https://doublepulsar.com/kaseya-supply-chain-attack-delivers...