The California fires seem to be caused by load oscillating attacks on smart meters to create faults (sparks) in the electrical grid. In 2024, Itron smart meter partnered with Microsoft Azure OpenAI.
First off, amazing article. Thank you for your attention to detail!
As an engineer (Loose definition lol), this makes me wonder about other technologies and companies that are vulnerable to production/service-line hacks that can be used to carry out terrorism. If I had all the money in the world right now, I'd probably spend it on burying those industries in ethical, patriotic engineers trained to spot and prevent ops and exploitable technology like this.
A lot of people don't realize how insecure most Technical Solutions are, or how they get that way. Most people, even Engineers, don't understand that you can design solutions to be fundamentally secure from certain kinds of attacks by avoiding certain design patterns, or that through manipulation of certain department leadership of the customer company, you can justify slipping control mechanisms into the Ghost Requirements for a technology that will effectively give you an undocumented backdoor.
For those reading who don't know, Ghost Requirements are psuedo-requirements that are assumed or a given due to the underlying technology(ies) being used, or how it's implemented.
For an oversimplified example, Architects like to use vertically federated, TCP-based Message Queues to upscale data flow from many endpoints to some central service in an easy to understand/visualize way. But they also require you to cache/store messages at several points in your infrastructure.
Depending on the size and nature of the data you're transporting, it might be easier and more secure to implement some encrypted UDP/DTLS scheme that maximizes direct throughput to your central service for scalability without caching your data anywhere outside the receiving Server's Kernel's own internal network packet queues, which are naturally access protected.
/Someone/ needs access to Message Queue Servers, but UDP/DTLS just passes through every router to the target without stopping, and should be encrypted (Unless you've not patched Heartbleed ;)).
So in this example, if your customer isn't bright, and you're criming and need access to customer data before it gets back to your App Server, you can just make sure you work Message Queues into your proposed Solution and it will be assumed that your "Support Teams" need access to the Queue Servers. Poorly handle or define your access points on these servers, and watch data get siphoned off.
Bonus points if you can convince them that an anti-virus program will reduce performance of the queue nodes.
The need for enforced standards for Architectural Security in the tech industry CANNOT be stressed enough. There is virtually no enforced regulation on this stuff in the US.
BOC claims if he was in America the penetration problem would be fixed in no time. I say bullshit, he has no funding, his patreon traffic is paltry as is yours because Jones, Webb, Rogan etc are handed the massive budget, so he gets pissed at you for no reason. Thanks for your work, the low traffic means it's spot on.
If we get caught they will just replace us with persons of the same cloth. So it does not matter what you do, America is a golden calf and we will suck it dry, chop it up and sell it off piece by piece until there is nothing left but the worlds biggest welfare state which we will create and control. Why? Because it is the will of god and America is big enough to take the hit so we can do it again and again. This is what we do to countries that we hate. We destroy them very slowly and make them suffer for refusing to be our slaves. Quote from Mileikowsky at Finks Bar 1990
First off, amazing article. Thank you for your attention to detail!
As an engineer (Loose definition lol), this makes me wonder about other technologies and companies that are vulnerable to production/service-line hacks that can be used to carry out terrorism. If I had all the money in the world right now, I'd probably spend it on burying those industries in ethical, patriotic engineers trained to spot and prevent ops and exploitable technology like this.
A lot of people don't realize how insecure most Technical Solutions are, or how they get that way. Most people, even Engineers, don't understand that you can design solutions to be fundamentally secure from certain kinds of attacks by avoiding certain design patterns, or that through manipulation of certain department leadership of the customer company, you can justify slipping control mechanisms into the Ghost Requirements for a technology that will effectively give you an undocumented backdoor.
For those reading who don't know, Ghost Requirements are psuedo-requirements that are assumed or a given due to the underlying technology(ies) being used, or how it's implemented.
For an oversimplified example, Architects like to use vertically federated, TCP-based Message Queues to upscale data flow from many endpoints to some central service in an easy to understand/visualize way. But they also require you to cache/store messages at several points in your infrastructure.
Depending on the size and nature of the data you're transporting, it might be easier and more secure to implement some encrypted UDP/DTLS scheme that maximizes direct throughput to your central service for scalability without caching your data anywhere outside the receiving Server's Kernel's own internal network packet queues, which are naturally access protected.
/Someone/ needs access to Message Queue Servers, but UDP/DTLS just passes through every router to the target without stopping, and should be encrypted (Unless you've not patched Heartbleed ;)).
So in this example, if your customer isn't bright, and you're criming and need access to customer data before it gets back to your App Server, you can just make sure you work Message Queues into your proposed Solution and it will be assumed that your "Support Teams" need access to the Queue Servers. Poorly handle or define your access points on these servers, and watch data get siphoned off.
Bonus points if you can convince them that an anti-virus program will reduce performance of the queue nodes.
The need for enforced standards for Architectural Security in the tech industry CANNOT be stressed enough. There is virtually no enforced regulation on this stuff in the US.
O'Connell railed against your work on patreon and called you a jewess. What the hell happened?
BoC is just salty. He got kicked off of YouTube for encouraging stochastic terrorism by urging people to sh**t Alex Jones in the face.
BOC claims if he was in America the penetration problem would be fixed in no time. I say bullshit, he has no funding, his patreon traffic is paltry as is yours because Jones, Webb, Rogan etc are handed the massive budget, so he gets pissed at you for no reason. Thanks for your work, the low traffic means it's spot on.
If we get caught they will just replace us with persons of the same cloth. So it does not matter what you do, America is a golden calf and we will suck it dry, chop it up and sell it off piece by piece until there is nothing left but the worlds biggest welfare state which we will create and control. Why? Because it is the will of god and America is big enough to take the hit so we can do it again and again. This is what we do to countries that we hate. We destroy them very slowly and make them suffer for refusing to be our slaves. Quote from Mileikowsky at Finks Bar 1990