The nozzle failed at srb ignition
A pending burn through was apparent even at that point.
404 publicly visible posts • joined 20 May 2020
.....enabled by a combination of bad build and testing on the part of CS **and** (don't forget) deliberate design decision by msft to hide a set of API calls that set their own internal AV solution (Defender) at a significant performance advantage compared to third-party tools.
When msft was caught with their design pants down, the decision was made to open those APIs up to everyone and anyone when the rational/good design decision should have been to kill off the calls.
And that's how we got here.
The court case that needs to be settled is if msft and their managers/executives are liable for global user damages caused by poor design and implementation of their products.
and they are.
Pull up a utility routing map that shows high-voltage main lines, high-capacity natgas pipelines, and fiber cable routes.
Now draw a 10-25 km circle at likely intersections.
Those are where mega data centers have been built the past 30 years and will continue to be built.
Any waving of hands with "what about the supporting infrastructure" is spurious at best.................
Over the past three years, I've been involved in the migration of some 48,000 server instances, Windows, Linux, from VMWare (hosted at both leased/cloud facilities and hosted locally/on-prem) to cloud native instances NOT using any VMWare product.
And my experience is hardly unique. Colleagues at other firms have done more work in this are than have I.
It's accountability, first of all at the human level. Then at the corporate level.
As in other industries the past 30 years, safety/security concerns and practices/procedures aren't 'backed' by much more than a "lessons were learned, adjustments made, we promise to do better in future" while actual human lives are lost.
It's well past time when the C Suite is held, directly responsible in some very personal and impactful ways for the suitability and behaviors of their companies and products.
Having been inside of Optum, and watched as the old-boy/girl network promote high percentages of connected people without regard for their actual skills or abilities, I'm not blown away at all.
Optum is well-known as a repository where the only accountability is at the lowest level of staff. Once an individual is in a 'leadership' role, part of their job is to expand staff to ensure that a few sacrificial lambs are always available.
Too big to fail = too big to trust. The best approach to security segmentation is to break that monster up.
..........to troubleshoot and fix a recently delivered laser printer.
Not something you can buy from the corner shop. It was one of those 1980s/1990s beasts that printed at 200 ppm double sided and had 4 input trays, 6 output trays, and an optional roll paper feeder / slicer.
When I got there, found that the local trucking firm that the customer hired (not the one we recommended) had rolled their truck down the side of a mountain. I collected the hazmat imaging belt (we just called it nasty stuff back then), the hard drives with proprietary software. the 6 eeproms with bootup firmware, and sat in the local conservation camp lodge for a week until my bosses and client 'negotiated' how to recover from the mess.
Got some great photos from the pair of game drives we took.