Instead of trying to harden an OS, why not use a system designed to be secure from the start, one that supports multilevel security. The technology was created in response to data processing demands during the Viet Nam conflict, and perfected during the 70s and 80s.
The root cause is that the security model of Unix that everyone copied isn't compatible with the modern world. The OS never asks what resources you want to allow a given program to access, instead it ass-u-me-s that it should have full run of everything, and just trusts the program to do the right thing.
So antivirus programs were invented to serve as a "no-fly-list" type system.... only programs on the list are stopped. This worked well until methods for changing the signature of programs got up to speed. Imagine a terrorist being able to make up a name before trying to buy/board a flight... this is where we are now.
Until we get the OS to ask what resources a program should be allowed... things will keep getting worse.
Because 10% of a working system can't be measured. Even a 100% completed to spec system is worthless until it has actually been used for a while... when it will prove to need about 100% more work.
Most software projects fail, unlike construction, etc... engineering can't be applied.
What, the Wealthy Industrialists who funded a clearly insane person on the assumption they could control him?
The lowest frequency you could use to track a target should be on the order of one that results in the target being 1/2 wavelength. Given the F35 is 16 meters long, that works out to about 10 Mhz. I highly doubt there is an effective way to absorb/deflect a radar pulse at such a low frequency (and depth of penetration) in an aircraft.
I've known this since the 1980s... I highly doubt that I'm in any way unique. I expect there are a number of spread spectrum 30-50 Mhz radars out there, just for catching "stealth" targets.
I designed and built my first embedded microprocessor project (for remote metering) using an 8088 and a 8284 clock generator chip, with some EPROM and static RAM back in the early 1980s.... I've been working on computers ever since.
How did this get down-voted? Settlement is a thing
The big issue is that one group of refugees from an attempted Genocide is creating another group of refugees from their attempted Genocide.
All else is lies.
"Our Lady of Blessed Acceleration, don't fail me now!" and/or
"Our Lady of Blessed Power Application, don't fail me now!"
I just gave up, and read the following things
doc searls web log
and that's it. The internet was nice while it lasted.
If this were a couple of kids in the US... they would both be on their way to Gitmo, the anti-rejection drugs the kid probably needs to stay alive wouldn't be addressed... then the remaining kid would probably go on a hunger strike in Solitary.
Oh... and someone at the Bank would be put in charge of a new "cyber security" division, with a big bonus and a corner office.
I wish we could be more like Canada some times.
That doesn't address the issue of unintended side effects from existing bugs. I agree that a separate LAN can help mitigate things, but it doesn't eliminate the odd things that can happen in a world where code is trusted by default.
Imagine if your garage light switch would 1 out of every 1000,000 times, cause your roof to fall off your house.... this is the world of software that can do anything.
The problem IS that things are trusted by default... but not in the way the author thought. If you trust every program you run by default, you are doomed. An operating system should NEVER trust anything by default... Linux, Windows, OSX all violate this principle. So do embedded devices base on some variant of them.
Never trust by default, and you stop having to worry about side-effects, and start deciding what the limits are ahead of time.