No validation, in the driver or the updater software.
No validation or automated testing on publish.
No staged rollouts.
Just utterly irresponsible all around.
When I worked there six years ago, the company motto was "two feet on the gas pedal" because the CEO was a race car driver. I bailed after 10 months, giving up pre IPO shares. The management for my team was non existent, and I was on the build and release team. People were doing releases of manually. They've improved the automation some from what I here, but looks like the motto finally hit them.
I should also say their metrics were absolutely staggering. The log aggregator was doing something like 2 trillion requests a week. All backed by splunk. I never heard what they were paying, but it must have been fucking nuts.
Race car drivers definitely don't put both feet on the gas pedal though... Like, what?
I would've preferred Colin McRae's classic in the same spirit: "when in doubt, flat out"
The unfortunate thing is that, in the long run, that strategy will probably be super effective. Unless Europe (with the only internet regulations that actually have teeth) does something harsh enough, they will probably pay a few small fines over this at most. Cost of doing business and probably baked in already.
A coworker of mine has worked with CrowdStrike in the past; I haven't. He said that the releases he was familiar with from them in the past were all staged into groups and customers were encouraged to test internally before applying them; not sure if this is a different product or what, but it seems like a big step backwards of what he's saying is right.
I first dealt with them at least 10+ years ago and at the time they had no ability to do staged roll outs or targeted roll outs. We got updates when they said we did, no choice or control. We had to resort to updating our firewall to restrict the download endpoint and only open it in groups to do a phased update.
Interesting! Sounds like they may have changed things a few times, or maybe my co-worker's memory has some gaps.
Oh ffs
Channel files are different from sensor updates, which you have no control over for version control. Sensor releases you have control over.
Ah interesting, thanks!
The idea of "security software" is ridiculous overall. You buy a software to fix security problems in Windows and it violates the original product by inserting code into kernel code. You lose support by the original product vendor. And you think you're secure, even the whole stuff makes you forget that IT should be always fit in solving security/restorability problems even when everything else fails.
And on a Friday to make things worse
No staged rollouts.
I read somewhere that CS does allow for staged rollouts but some updates deliberately ignore them.
No validation, in the driver or the updater software.
No validation or automated testing on publish.
No staged rollouts.
Just utterly irresponsible all around.
When I worked there six years ago, the company motto was "two feet on the gas pedal" because the CEO was a race car driver. I bailed after 10 months, giving up pre IPO shares. The management for my team was non existent, and I was on the build and release team. People were doing releases of manually. They've improved the automation some from what I here, but looks like the motto finally hit them.
I should also say their metrics were absolutely staggering. The log aggregator was doing something like 2 trillion requests a week. All backed by splunk. I never heard what they were paying, but it must have been fucking nuts.
Race car drivers definitely don't put both feet on the gas pedal though... Like, what?
I would've preferred Colin McRae's classic in the same spirit: "when in doubt, flat out"
The unfortunate thing is that, in the long run, that strategy will probably be super effective. Unless Europe (with the only internet regulations that actually have teeth) does something harsh enough, they will probably pay a few small fines over this at most. Cost of doing business and probably baked in already.
A coworker of mine has worked with CrowdStrike in the past; I haven't. He said that the releases he was familiar with from them in the past were all staged into groups and customers were encouraged to test internally before applying them; not sure if this is a different product or what, but it seems like a big step backwards of what he's saying is right.
I first dealt with them at least 10+ years ago and at the time they had no ability to do staged roll outs or targeted roll outs. We got updates when they said we did, no choice or control. We had to resort to updating our firewall to restrict the download endpoint and only open it in groups to do a phased update.
Interesting! Sounds like they may have changed things a few times, or maybe my co-worker's memory has some gaps.
Oh ffs
Channel files are different from sensor updates, which you have no control over for version control. Sensor releases you have control over.
Ah interesting, thanks!
The idea of "security software" is ridiculous overall. You buy a software to fix security problems in Windows and it violates the original product by inserting code into kernel code. You lose support by the original product vendor. And you think you're secure, even the whole stuff makes you forget that IT should be always fit in solving security/restorability problems even when everything else fails.
And on a Friday to make things worse
I read somewhere that CS does allow for staged rollouts but some updates deliberately ignore them.
Preach it