It reminds me of a story.
It takes place in 1992 or so, DARPA was funding a small computer security company to securely connect The White House (really the Executive Office Building) to the Internet. They came to this security company and asked "Do you know anything about 'Internet firewalls?'" People at the company did. After lots of talking and planning someone with a clue said, "We need to do a network survey." "Why?"
"We need to see what else is connected to your network." Now remember, this was 1993, before everyone including your Aunt Tilly was on the Internet. Long story short, the company did the network survey and found that the White House network was already on the Internet. They were connected via NASA Goddard, which, at the time, was well-known in the local IP community for poor network security. They would have had a firewall in their front door with an unlocked back door.
Back to the jetliner. People tend to make these mistakes. Why, or why in the world are—sorry, were—the networks interconnected? I don't know but experience tells me it was probably to save some copper (or fiber). No matter how smart you are (and the Boeing engineers are smart), always, always, always bring someone else in to look at your plans. And make sure some of those people know something about security and risks.
| I heard from someone "in the know," who shall remain nameless. |
"How to hack into a 787" was erroneous from the very beginning. It was a scare story launched by someone with no actual knowledge of the systems in question.
Well, certainly good news, but my point remains. These are the times when you don't just bring in application experts, or networking experts, but also security experts.