Category Archives: History

Do Walls Work?

Strangely enough I’ve been getting this question lately from people who believe I might have an answer. Little do they realize how complicated the answer really is.

The short answer is (from a political economy view) that walls will be said to work when someone is trying to get them funded, and will be said to not work when the same people (or those who follow their folly) try to get all the other things funded (because walls easily fail, as everyone familiar with security can predict).

Before I go much further, let me briefly turn to the philosophical question of walls. One of the most famous Muslim scholars in the world, Muhammad Ali, probably best exemplified the answer to any questions about walls “working”. Here’s a eulogy to his wisdom, worth a watch in its entirety. For purposes here I’ve started towards the end at the relevant quote:

…life is best when you build bridges between people, not walls.

So if the celebrated genius of a fighter Ali tells us life is best with bridges, why build walls at all? And if security experts (defenders and attackers) so easily predict failures, why spend money on them? These are the kinds of questions every CSO should be well-prepared to answer. It’s basically the “why should I fund your project to disable connections, when the point of business is to enable them” meeting.

This goes to the heart of the Anti-Virus (AV) industry, and the current derivatives (Clownstrike, Cylance…you know who I’m talking about).

In the beginning days of viruses (early 1980s) there were theories about positive security models, which measured system integrity in a way today we talk about “whitelists”. If you want to run something on a computer you boil it down to the essence, the most efficient model and description, such that anything out of that ordinary baseline could be flagged as unusual or even adversarial.

Such a model of safety isn’t revolutionary by any stretch of the imagination. It was a simple case of people with some knowledge of the healthcare industry saying computer viruses could be detected by looking for what is abnormal, and emphasizing a thorough scientific understanding of what is normal.

Well, in healthcare there is motivation to spend on establishing such knowledge because “healthy” is valuable state of being. In computers, however, there was a giant loophole preventing this kind of science being developed. Companies like McAfee realized right away that if you just scare people with fear, uncertainty and doubt about imminent invasion by caravans of viruses you can get them to throw money into a wall (even though it doesn’t work).

I would make the usual snake-oil reference here, except I have to first point out that snake-oil has real health benefits.

…snake oil in its original form really was effective, especially when used to treat arthritis and bursitis.

The concept of a snake-oil salesman refers to some shady American guy stealing Chinese ideas and using cheap counterfeits to profit on harm to customers. Thus the McAfee model of building walls (today we talk about “blacklists” being ineffective, when really we could say fake snake-oil) for huge amounts of money started around 1987. At that time McAfee the man himself created a company to collect money for delivering little more than a sense of safety, while attackers easily bypassed it.

Unfortunately consumers bought into this novelty wall sold by McAfee, despite being mostly nonsense. The oportunity cost was massive and the security industry has taken decades to recover. Innovators trying to compete by achieving any kind of security “science” in operations were obviously far less profitable compared to the raft of snake-oil McAfee marketing executives.

Consider for example in 1992 McAfee told the world an invasion was coming and they needed him to build some more walls.

McAfee was blamed for creating a false threat to sell more of his anti-virus elixir – which he did. McAfee’s anti-virus software sales reportedly “skyrocketed” that year, with more than half of the companies in the Fortune 100 having purchased McAfee software. Of course, this only furthered the theory that McAfee had just made up the whole damn thing.

He retired after this, scooping up millions in profit by building walls that didn’t work for a threat that didn’t exist.

To be fair, threats do exist, and walls do have a role to play. Hey, after all we do use firewalls too right? And firewalls have proven themselves useful in a most basic way too, by having attackers shift to an application layer when all the other service ports are down.

In other words firewalls work in the way that building a wall could end up dramatically increasing threats coming through airports, seaports and even underground. Basically air, sea and land threats could increase and be detected less easily by building a wall. When I used to pentest utilities for example, we rated walls as significantly less effective at stopping us versus six-sided boxes (buildings, if you will).

True story: on a datacenter pentest I approached two layers of walls. The first was easily bypassed and then I used some engineering to get through the second one. It was only at that point I realized I was in the wrong location. Datacenters used to be careful to avoid having any outward logos or markings, even obfuscating their address. In this case it worked! After getting myself through two walls without much thought, I was looking right at an ICE logo and a bunch of guns.

Yes, I accidentally had tested the Immigration and Customs Enforcement (ICE) facility…and immediately began egress. Getting out quickly took some creativity, unlike getting in, and ended up being a better skills test. In the end it was fine, a laugh for everyone, including the datacenter (which I did test immediately after).

So in the strictest sense, walls have some work to do, and they may be capable of delivering. This is very different from saying walls work, however, when people are thinking in the broader sense of being safe from harm. A con-man like McAfee can vacuum up money to get rich while delivering almost no value, because “walls work” is a tiny grain of truth in his giant cake factory shipping nutrition-less lies about health (risk and safety).

1600s: Que ne mangent-ils de la croûte de pâté? (let them eat forcemeat crust!)

1700s: Qu’ils mangent de la brioche! (let them eat cake!)

1990s: Let me install AV!

2019: Let me build a wall!

Almost a decade ago I did a small speaking tour about cloud security on this topic, although I used the Maginot line as an example. This massive defensive wall was named after 1930s French Minister of War André Maginot, and constructed along the country’s border with Germany.

I pointed out that one could argue the Maginot line forced attackers to shift tactics and use other entry methods. In that sense those walls did some actual work, like a firewall or AV will do for you today.

However, expectations of the French were for the wall to prevent the very thing that happened (rapid invasion past their borders). In fact, the forces at the wall became so irrelevant, they still stood ready and willing to fight even after the French government capitulated to the Nazis. Let’s face it, had the French military leadership simply listened to all the active warnings about Nazis going around the line, France likely would have ended up saying the wall did a job to help focus their active response (they could have directed defenses to neutral country borders that had no walls).

The French leadership failed to notice something was not normal (enemy troops moving through the Ardennes Forest and violating neutral countries). And that is why Maginot’s expensive wall continues to be almost universally remembered as a huge failure. (Some do still argue, as I did too, that Maginot’s plans worked within an extremely narrow assessment).

A “Manstein Plan” directed Nazi tanks through the Ardennes Forest to exploit Maginot Line weakness in uncompleted areas (despite 1938 General André-Gaston Prételat exercises predicting this exact issue by driving his tanks through that Forest). That Manstein Plan maybe should really just have been called the Prételat Report? Source: Martin Marix Evans, Invasion! Operation Sea Lion 1940 (Routledge; 1st edition 9 Sep. 2004) page 37

I don’t think any French to this day would say their wall worked however, given how it was billed to them at the time of funding (for an extremely high cost, which weakened more modern/important security needs like detection and radio/aero/rapid response).

For the French, the greatest failing of the Maginot Line arguably lay not in its conception, but in the opportunity costs that its construction imposed. The 87 miles of fortifications that were completed by 1935 cost some 7 billion francs ($8 billion in 2015 terms), over twice the initial estimate when the effort began in 1930. Depending on the source, the entire French defense budget in 1935 was between 7.5 (John Mearsheimer) and 12.8 billion (Williamson Murray) francs. As a result of this stupendous outlay, French military development in all other areas, from tanks to aircraft, suffered.

In other words, the current US regime is looking at data suggesting airports are the vulnerable path for entry and yet is proposing money be spent on something completely unrelated to airports. France in this scenario would be looking at data suggesting forests and neutral countries are the vulnerable paths for entry and blowing its budget on a wall elsewhere.

Terrorists trying to infiltrate the U.S. across our southern border was more of a theoretical vulnerability than an actual one…the figure she seems to be citing is based on 2017 data, not 2018, and refers to stops made by Department of Homeland Security across the globe, mainly at airports.

Does a wall on the border help with the real vulnerability in airports? No. The wall expense actually hurts, making the US materially less safe. One might conclude that shutting the government down, reducing active defenses at airports, to force a redirection of security funds to a useless wall is a very cynical plot that any hostile adversary would dream about.

To put a finer point on it, the expensive shutdown and the demand for an expensive wall both reflect the self-harming anti-American mindset of the current regime, and present grave dangers to US national security.

The long answer is thus that walls work at a very primitive level, which tends not to be worth the cost except in very particular cases where the predicted results are known and wanted. In the present context of the US border, there is no imminent threat and there is little to no chance of success without massive investment in detecting other methods of entry predicted (again, for a non-imminent threat).

There’s a reason AV is mostly free today. And it’s the same reason building a wall on the US border has been pitched as extremely expensive response to a fantasy threat, meaning it has little to no real value. Someone is trying to redistribute wealth and quit before people realize the walls are a distraction, where wasting time and money turns out to have been the objective (to hurt America).

History is pretty useful here, as we can easily prove things like walls have for thousands of years failed to prevent people climbing up (and down) them.

It is believed that the idea of a ladder was used over 10,000 years ago. We know this because pictures of them were discovered in a cave in Spain.

The ladder is also mentioned in the Bible. Jacob had a dream and in the dream he saw a ladder reaching from Heaven to earth.

Fun fact, ladders are much older than wheels. That’s right, ladders are more than twice as old as the wheel! And we obviously can say walls came before ladders. Thus always remember, when someone asks you which is older the wheel or the wall, go with the ladder (pun intended).

It remains to be seen, however, whether this sort of wall debate and debacle making the US less safe is going to force the US regime leader to step-down.

Incidentally, the Maginot example was not my only one on that speaking tour. Since I was invited to speak in England as well as the US, I thought it only fitting in 2010 that I use castle walls as an example of technology shifts, like a cannon, sawzall or a hypervisor escape vulnerability…the kind of inexpensive and fast-moving thing that makes wall builders shudder:

IBM Watson Sued by LA County for Secretly Tracking Users

Let’s get one thing out of the way. IBM’s Watson was instrumental to the Nazi Holocaust as he and his direct assistants worked with Adolf Hitler to help ensure genocide ran on IBM equipment.

When IBM’s director of worldwide media relations, John Bukovinsky, was asked about the disclosures in 2001 and 2002 of the company’s involvement in facilitating the extermination of millions of Jews, Gypsies and others, he replied, “That was six years ago [sic].” When a reporter pointed out that the Holocaust itself was some 60 years ago, Bukovinsky quipped, “So what. What is the point?”

The idea that IBM would want to market their big data system after the man notorious for meeting with Nazi leaders to deliver counting machines for genocide…it’s a pretty big sign that the evils of Watson are something to keep an eye out for even in the present day.

As Edwin Black wrote in “IBM and the Holocaust: The Strategic Alliance between Nazi Germany and America’s Most Powerful Corporation“:

Thomas Watson was more than just a businessman selling boxes to the Third Reich. For his Promethean gift of punch card technology that enabled the Reich to achieve undreamed of efficiencies both in its rearmament program and its war against the Jews, for his refusal to join the chorus of strident anti-Nazi boycotters and isolators and instead open a commercial corridor the Reich could still navigate, for his willingness to bring the world’s commercial summit to Berlin, for his value as a Roosevelt crony, for his glitter and legend, Hitler would bestow upon Thomas Watson a medal — the highest it could confer on any non-German.

Fast-forward to today and IBM’s Watson has been charged with user location tracking using an innocent-sounding weather app.

In a complaint filed Thursday in California state court, the city alleges IBM used detailed location data from users for targeted advertising and to identify consumer trends that might be useful to hedge funds, while at the same time telling consumers their location would only be used to localize weather forecasts. The suit doesn’t allege personally identifiable information was sold.

“Unbeknownst to many users, the Weather Channel App has tracked users’ detailed geolocation data for years,” the complaint alleges, calling the Weather Channel’s actions “unfair and fraudulent.” The complaint also says the Weather Channel profited from the data, “using it and monetizing it for purposes entirely unrelated to weather or the Weather Channel App.”

Again, it’s hard to fathom that IBM would want to name a big data machine Watson. It’s even harder to fathom that someone in IBM thought lying about user location tracking to monetize ill-gotten data was a good move…but then I just go back to them naming their machine Watson.

Arizona Rush to Adopt Driverless Cars Devolves Into Pedestrian War

Look, I’m not saying I have predicted this exact combat scenario for several years as described in my presentations (and sadly it also was my Kiwicon talk proposal for this year), I’m just openly wondering at this point why Arizona’s rabidly pro-gun legislators didn’t argue driverless cars are protected by Waymo’s 2nd Amendment right to bear arms, classifying vehicles as consumer-grade munitions that also carry people or goods inside. AZ Central reports:

People have thrown rocks at Waymos. The tire on one was slashed while it was stopped in traffic. The vehicles have been yelled at, chased and one Jeep was responsible for forcing the vans off roads six times.

Many of the people harassing the van drivers appear to hold a grudge against the company, a division of Mountain View, California-based Alphabet Inc., which has tested self-driving technology in the Chandler area since 2016.

The one or two people operating the tens of thousands of weapons (driverless cars) on public roads are counting on their surveillance capabilities as much as their armored weapons to keep the upper hand in this fight. AZ Central continues:

The self-driving vans use radar, lidar and cameras to navigate, so they capture footage of all interactions that usually is clear enough to identify people and read license plates.

According to police reports, Waymo test drivers rarely pursue charges and arrests are rare. Haselton was charged with aggravated assault and disorderly conduct, and police confiscated his .22-caliber Harrington and Richardson Sportsman revolver.

“Haselton said that his wife usually keeps the gun locked up in fear that he might shoot somebody,” Jacobs wrote in the report. “Haselton stated that he despises and hates those cars (Waymo) and said how Uber had killed someone.”

Let’s be clear here. The grudge being referenced is related to people in a neighborhood being upset about the rollout of armored weaponry.

Tense scene unfolds in Arizona 2018 as locals resist the Waymo rolling displays of unregulated power

Think of the irony that Arizona residents have a grudge against driverless cars because they are in effect weapons being wielded unsafely in a public space, killing people (this is the infamous state that won’t even hear an argument about regulating guns).

Waymo is like someone taking their gun off the gun range and not being able to keep their pistol holstered, let alone rounds unchambered, wandering around waving it in everyone’s face. You think the neighborhood is just going to look the other way while that barrel points at their family and friends?

Compare that grudge with some poignant analysis just a year ago that was titled “Arizona is a heaven for test new cars – USA TODAY” (which at some point changed its title to “Why automakers flock to Arizona to test driverless cars”. TL;DR:

  • relatively light regulatory environment of the past two and a half years
  • weather allows for year-round testing of vehicles, and low rainfall means minimal disruptions…low winds and a temperature range that is conducive to completing regulatory tests almost every day of the year
  • desert offers car manufacturers a remote and private testing location that’s away from the prying eyes

Allow me to translate this analysis into technology ethics: lawless and opaque makes for easy hurdles, and low standards means quick money for investors. The desert has no actual environmental risk. Testing in a vacuum chamber means your product is ready for use in a vacuum, not public streets. And testing with zero outside observability/validation of claims means you aren’t anywhere close to ready for deployment.

Desert vehicle development is about as sane as developing moon vehicles and saying it’s the wrong type of planet when they can’t move with earth’s gravity.

To put it another way, the Governor of Arizona scoffed at other states where leaders held human life up as a value worth protecting and preserving. The money hungry Arizona official literally said he is happy to promote profit over safety.

In August 2015, Ducey signed an executive order allowing the testing of autonomous cars on public roads, hoping the cars will fuel “economic growth, bring new jobs, provide research opportunities for the state’s academic institutions and their students and faculty, and allow the state to host the emergence of new technologies.”

It looks like Ducey didn’t think very hard about how selling out human life for a boom in weapons sales might backfire. Nothing in that list of benefits says there is an ounce of care for public safety or health, amiright?

Mo’ money, mo’ problems.

August 2015: regulations are dropped, standards are non-existent. Anyone wanting to develop weapons for public roads is invited to Arizona

December 2017: newspapers describe Arizona as “Heaven” for developing weapons to wave around in public without need of any safety training or controls

Wait for it…

March 2018: “The governor of Arizona has suspended Uber’s ability to test self-driving cars on public roads in the state following a fatal crash last week that killed a 49-year-old pedestrian”

Uber using an automatic weapon to kill one person and getting regulated in Arizona compares oddly to the 68% of all homicides in the state committed with a gun and the nearly 1,000 people killed a year in Arizona by guns that get zero regulation discussion (see above).

Oh, but who could have predicted that removing regulations and allowing weapon development to launch straight to the streets would invite bad corporate behavior? Not only me, giving public presentations about this problem, also internal engineers who documented how “there were a lot of warning signs” yet Arizona’s “Heaven” meant they were neither attended to internally to pass regulations nor exposed to regulators:

“A car was damaged nearly every other day in February,” Miller said. “We shouldn’t be hitting things every 15,000 miles.”

Miller pointed to an incident in November 2017, when an Uber car had a “dangerous behavior” that nearly caused a crash. The driver notified his superiors about the problem, Miller wrote, but the report was ignored. A few days later Miller noticed the report and urged the team to investigate it.

But Miller says his request was ignored—and when he pressed the issue with “several people” responsible for overseeing the program, they “told me incidents like that happen all of the time.” Ultimately, Miller said it was two weeks before “anyone qualified to analyze the logs reviewed them.”

So there you have it. 2015 effort to reduce safety control levels so weapons can flood the market. 2017 weapons entering market are causing harm and at frequent intervals, indicating escalation to wider and more severe conflict.

Doesn’t it seem obvious that this ended with a meek 2018 effort to put the weapon genie back in the bottle…yet any historian can tell you once battle lines have been drawn and people are angry about their clan being attacked, they are going to harbor some hostility.

So with all that in mind the big question now becomes as the weapons manufacturers switch to their all-encompassing surveillance systems to undermine the nascent groups of resistance, whether they also will claim their manufacture and sale of automatic high-power weapons is protected behavior anyway under the 2nd Amendment.

We have seen some of that messaging already, as Uber and Tesla used to be fond of saying their particular brand of automatic weapons will reduce deaths on the streets, much in the same way that totalitarian governments would argue how top-down centrally controlled armored divisions are the way to keep the public safe from itself.

And in that sense, are Arizonans actually crazy if they read the Uber story of deaths for profit and then think of themselves as preventing harm to their fellow citizens by stepping out into the street early to disable the Waymo munitions rolling into and over neighborhoods?

RIP Simcha Rotem

Simcha Rotem has passed at 94. He was only 15 when Germany invaded Poland. He and his mother were wounded by German bombing raids that killed his brothers and grandparents. By the time he was 19, he served under Marek Edelman to resist Nazi incursions, leading to the outbreak of combat.

The insurgents preferred to die fighting instead of in a gas chamber at the Treblinka death camp where the Nazis had already sent more than 300,000 Warsaw Jews.

Speaking at a 2013 ceremony in Poland to mark the 70th anniversary of the uprising, Rotem recalled that by April 1943 most of the ghetto’s Jews had died and the 50,000 who remained expected the same fate.

Rotem said he and his comrades launched the uprising to “choose the kind of death” they wanted.

[…]

As the Germans pounded the Ghetto and the uprising faltered, Rotem was instrumental in helping fighters flee to safety through the Warsaw’s sewer system to forests outside the city.

He continued to fight alongside Polish partisans and in 1944 participated in the Warsaw Uprising. After the war he joined avengers group Nakam, which was dedicated to exacting vengeance on Nazi war criminals.

RIP