NSA Silver Lining: Interesting Startups

People frequently ask me if I see any interesting startups in the security industry. Let me give you three examples but only because they fit an interesting trend.

Obviously there is a long history of warfare innovation leading to civilian products. What might we look for now? Today’s battles are fought with information tools. And the safety of information is most pressing to intelligence organizations so they seek and develop talent who innovate in data protection. Naturally this is leading us to a new generation of utility in securing information.

We are seeing those with deep experience and exposure to very difficult problems, within the intelligence community, get an entrepreneurial bug and launch startups. Whether you trust the founders or their product is not the point of this post.

Perhaps an historic example will clarify. Sometimes when I look at fancy kitchen knives from Japan I wonder if anyone ever protested innovations that made blades too sharp, too fair, or too strong. The utility of a tool in the kitchen surely benefited from innovations derived from battle. Making dinner with a better knife doesn’t mean you have to condone or even care about Samurai.

Here are three examples of companies that represent an emerging trend in creative thinking about tools we need to get better at protecting our data:

  • Ex-NSA staff start company to protect Big Data by extending Apache Accumulo (an NSA enhancement to a Google project that now has been released to the public): Sqrrl
  • Ex-NSA staff start company to make browsing the web safer by extending XWindows concept of centralized browser session pushed to remote displays: Light Point Security
  • Ex-Unit 8200 staff start company to make SaaS safer by proxying and tracking all user behavior: AdAllom

Back to the simple knife, there some interesting studies that try to explain how Japanese civilian innovations evolved out of conflict. Creative thinking relative to explicit and tacit knowledge:

Knowledge Training

AC34 Finals: Notes of Interest

I’ve noticed several things in the current America’s Cup finals that keep my interest. While others in San Francisco seem completely oblivious to the racing, and it’s hard to drag them out and watch, I’m still excited about watching these points:

  1. Overall performance (energy transfer) engineering: ETNZ has the best boat design engineers in the world. It’s clear. They’re getting 4-5 knots more speed upwind. That is a huge factor for match competition where getting on top of the other boat means controlling the finish — the deciding factor in several races so far. I’ve seen far more twist at the top of the ETNZ sail compared to Oracle. Basically, Oracle spent more than double yet ended up with a slower boat. A straight run speed delta also tends to have a serious psychological effect on the sailors, forcing other errors, because it’s hard to stay positive when side-by-side you fall behind.
  2. Reduced drag: Both teams position sailors further and further below deck level. One of the team engineers told me that one single sailor standing up causes enough drag at 25knts to impact performance by several seconds a kilometer. The boats are only a few seconds apart in the races so over a 1500m course a boat with less drag from sailors themselves will have a measurable advantage. ETNZ seems to have the more aerodynamic deck and cowlings. It also hurts when water hits you at 25knts (like cold nails) so working lower is probably welcome relief.
  3. Turns: As the boats jockey for dominance they carve incredibly fast turns. A 72ft boat that can pivot at speed within its own waterline is a phenomenal engineering achievement. The wind and water generate massive loads yet the captains clearly transfer the energy and shift quickly while keeping speed. ETNZ has an advantage in this area as they clearly make smoother turns and maintain more of their speed, which further capitalizes on straight-line speeds.
  4. Team fitness: These people have trained non-stop for three years, every day and often twice a day. They are at the peak of physical shape. Yet when I watch the videos with sound on I hear them wheezing and coughing as if they can barely catch their breath. Turning and tuning the boat completely maxes them out. And they can’t go anywhere. Unlike football, soccer, basketball, baseball, volleyball…there is no relief or substitution possible. The Round-the-World Ocean races once were described to me as playing rugby without any option of leaving. That is why professional sailing could perhaps be seen as one of the top physically demanding sports in the world.
  5. Tactics: I’m completely shocked at the errors a usually ultra-aggressive Spithill has made. I expected to see Oracle try and force errors, play dirty and get in Barker’s face at every chance. Instead Spithill has made repeated unforced errors and been charitably giving away races. Perhaps he is not in sync with his team, or the speed delta is getting into his head. When the match-racing heat is on high, Spithill starts melting and makes moves painful to watch. Meanwhile Barker, always the quiet gentleman, sails away confidently and cleanly.
  6. Team Nationality: Spithill almost made me spit up when I first saw him tell an audience Oracle is the “home team”. This man is an Aussie through-and-through. Nothing wrong with that, but he has stated in interviews that ever since 1983 (when he saw Australia win the cup) he has dedicated his life to Australia keeping the cup. In the post-race interview a few days ago he repeated his “home team” nonsense and said ETNZ is trying to “take the cup far away”. Barker, in a beautifully accurate retort said “if we win we’ll bring it closer to your home”. Indeed, Spithill might prefer a NZ win.

    Spithill thus comes across as awkward as if forced to ask for support now from the country he has loved to hate as a sailor. In addition, despite being in America, Oracle also has a reputation for disdain towards its home country and especially the cities lived-in by Ellison. A real-estate agent just told me the Oracle CEO bought a house in SF to watch the races and immediately demanded the neighbor, an elderly lady in retirement, cut down her trees so he could get a better view. She said no at first, since they were clearly on her property. Then Oracle lawyers promptly arrived and asked her if she really, really wanted them to wipe out all her retirement money in a messy legal fight and leave her for dead. With a home team like that who needs enemies?

    ETNZ, in stark comparison, has used a large percentage of funds direct (kick-started) from their government and held discussion about how the money spent will benefit taxpayers (jobs, business, trade, etc.).

  7. Boat Nationality: Both boats were built in New Zealand, which if advertised more might help recoup some of the national investment. More interesting than that, however, is the ETNZ boat was designed by the American team that won the cup back from NZ in 1988 with a catamaran. So the ETNZ boat is essentially a successor American boat to the 1988 campaign, while the Oracle boat is apparently not American at all. It may even be French, since they have boasted about finding their initial wing designer in France. Whatever the Oracle boat is or isn’t, to me ETNZ is really sailing the American boat design.
  8. Waterfront access for dinghies: Perhaps the most annoying fact of the entire event is that it is inaccessible to the common person. Super-yachts need more berthing space about as much as anyone needs a hole in the head. Those who aren’t billionaires, on the other hand, really REALLY need a place to launch a performance dinghy in San Francisco. Basically if you’re a kid in an Optimist you’re ok because clubs will support that but once you graduate to something fun where do you go? And if you’re a young professional ready to splash down some money and go for a hot ride…you basically can’t unless you go far away. The waterfront has no facilities and no support. None. That is perhaps the biggest oversight of this entire event. Even rockets are more accessible than high performance dinghy sailing to people who live in SF.

Those are some of the major notes. In summary, ahead I see a sea-change in the boat-building industry and very little change in the American sailing community. Globally we’ll get more efficient, faster and more fun boats of all sizes yet unfortunately this will not lead to any more American kids rushing to get into sailing.

I have a bunch more items I’m tracking but just wanted to share the biggest and most recent ones. Let me know if you have others to add or discuss.

AC34: ETNZ Bows Down…and Survives

Several people have suggested I explain the ETNZ crash. Usually it comes up casually. I get all animated and start describing the details of the event and then people say “that’s interesting, others need to hear this”…and I think why didn’t the America’s Cup put someone on the commentary team who actually races catamarans?

Just one source of reporting would be OK if it was amazing and insightful. Tell a few war stories, life in the trenches stuff, pepper it with math and science, and I’d be glued to the tube during the Louis Vuitton races.

Instead search the entire Internet and you will find only one video, one set of boring empty perspectives. Here it is. Notice how lame the comments are during the action at Gate 3:

The announcers mention a puff, and basically having nothing to say other than what happened after the bows dive down. Men overboard, damage on the front. Duh:

This all has to do with the pitch. The bows went down. […] They stuffed the bows for some reason…that wave hit them.

Thank you captain obvious!

Unfortunately this is not far from the official statement language of ETNZ, as reported by Sailing World. At least they provide some detail such as shift in speed:

The team’s AC72 Aotearoa popped up onto its hydrofoils rounding the mark and then a gust of wind hit. The port (left) bow of Aotearoa buried up to the main crossbeam, reducing the boatspeed from 40 knots to 13 and flicking two crewmembers, Rob Waddell and Chris Ward, overboard. The two grinders were recovered unharmed by the team’s chase boat, but the rush of tons of water tore the port side fairing off the main crossbeam and left the crew shaken.

“In this sort of racing, the boats are incredibly powerful. You see how quickly the speed rockets up as you make the turn around the top,” said skipper Dean Barker. “We came in there with good pressure. Through the turn we were always going to pick up a decent increase in speed; I’m sure there are a few things we could’ve done better.

Dropping from 40 to 13 knots in seconds feels like what, exactly? Unless you’ve been on a boat that stuffs the bows into a wave it’s hard to imagine. That’s why an announcer should be someone who has lived the danger, experienced the excitement, and can relay the feelings to a general audience.

So allow me to try. Here is the scoop (pun not intended) on what happened and why, and what it feels like.

This kind of event is all too common in catamaran sailing. This is what failure usually looks like:

Fail1

But not this:

Notfail

Not yet, at least. Those crazy cats in the last photo (pun not intended) are burying their entire hull and managing to avoid pitch-pole (tripping).

So the biggest risk of crashing in catamaran racing is actually when you turn to go down wind at the windward mark. It’s really quite simple and expected, which means ETNZ was about to crash in the area most likely to cause a crash.

If you’ve raced catamarans you simply know that when you approach the windward mark in a big wind, you might be experiencing a bowel movement as you turn the boat away from the wind. When the catamaran does not oppose or release power that builds in the sail it dives the bows. A big puff hitting ETNZ as it bore away (turned after the mark) certainly fits that equation.

But this isn’t the first time a puff has hit a boat in this critical moment. Catamaran sailors know puffs happen at the windward mark all the time. So why didn’t the team just handle it? Actually, like the last photo above, they did.

First of all, the wave-piercing design of the AC72, which some say look like inverted hulls, is meant specifically to allow the boat to survive a dive. From that perspective, they came out of the dive instead of crashing because they knew it could happen. Amazing risk engineering.

The announcers should have been all over the fact that a 72ft boat with wave-piercing hulls can survive a deep dive at 40knts. That was an unbelievably beautiful and planned graceful exit, unlike the Oracle incident where the boat flipped up and eventually broke apart.

Here is a clever comparison of the Oracle and ETNZ boats from CatSailingNews

Comparison

The article is mostly pointing out that Oracle has been copying ETNZ to stay competitive. Notice something else, however. The bows of the two boats are both inverted and designed for wave-piercing yet still quite different. The Oracle boat appears to have far less ballast (float) than ETNZ.

Could Oracle have survived such a dive? My experience on the A-Class catamaran over four generations of design is that a clever buoyancy model in the bows makes a MASSIVE difference. Oracle, like the current platform I sail (an A3.5), looks anemic in the front end. It would likely have had a harder time even with the re-design after their crash.

Oracle

This is what an announcer could have mentioned. Bow design. They also could have mentioned the effect of the T-shaped rudders, and L-shaped foils. And they could have mentioned the aerodynamics of the carbon relative to fluid density (wind above versus water below). Saying a crash is related to “pitch” simply isn’t good enough.

Second, a turn in puffs and big wind is scary business because of pressure for rapid decision-making. When Barker turned the corner he made a critical error by taking the turn too tight at the wrong moment. Bad luck, perhaps you could say.

It is a lot like turning a car into a hairpin curve. You know in your mind the speed you need to stay in control as you reach the apex. But in sailing you don’t get to take your foot off the gas or hit the brakes. There are no brakes. And a puff is like someone pushing your gas pedal to the floor.

Instead of smoothly turning you suddenly find a huge boost of power pushing you in a direction other than where you anticipated. Fractions of a second are all you have to decide how you’re going to handle all the excess power that threatens to toss you over.

Barker could have headed up, accelerated in a straighter line to keep the bows from diving. This actually compounds the danger if it doesn’t work, which I won’t go into here. His team also could have dumped power from the sails by stalling them. Stalling or luffing can be very complicated to do in extreme conditions at high speed, especially as it can cause the boat to lose stability.

The bottom line is Barker had several options and he turned a surprise into a strategy by keeping the boat flat enough that he could blast out of the water with speed after a dive instead of careening sideways. Fantastic boat handling married to fantastic engineering. Sideways would have been a disaster. Here’s what happened to Artemis in an AC45 race last year. Watch at 1:10

So we’ve covered some of the engineering and some of the boat handling (and trim) involved. What about feelings? The sensation of a pitch-pole is absolutely terrifying. It happens so fast you can barely process what is going on. Here’s an ETNZ team member recollection on SailingWorld

“I’m on the forward pedestal and was holding on for dear life,” McAsey said. “I was the second guy under water, with Jeremy Lomas in front of me. I was holding on as hard as I could. It all was a blur, everything’s wet and white, you come up, there’s a bit of broken carbon around the place and we’re two guys short. From there on it was just a matter of trying to cover the two guys lost.

Exactly right. One second you’re dry, flying and focused the next second you are blasted in the face by icy frothing salt-water and have no idea what is going on. The key to his story is probably the pedestal. My guess is he held that thing with a death grip as soon as the first drop of water touched his skin.

Keep in mind these sailors are the peak of professional athlete fitness. They train twice a day in the gym and have the strongest grip strength you can imagine. But things happen so fast, things get so slippery and cold, and everything can get turned around in tons of water hitting you at 40knts.

One time on my boat in a race I buried the bows so hard, so fast into the back of a giant wave that I was fired like a missile straight off the boat. I was sailing smoothly one minute and then BAM I’m three feet under water and trying to figure out which way is up.

A catamaran going from fast to slow quickly means it stops and you keep moving. There are no seat belts because you have to be able to move around. And that can mean you bounce off hard and often sharp carbon parts and line, and end up totally disoriented without vision or hearing…and dealing with the shock of rapid temperature change.

It hurts A LOT. I don’t bruise, ever, but one time I hit a wave so hard the boat stopped and I slammed into the back of a razor-sharp windward foil. It gave me a giant green, blue and black bruise on my thigh for weeks. Hanging on to a pedestal is far better option than getting catapulted, washed away or sliced into pieces.

So much to talk about. This tiny little snippet of sailing in the Cup could instantly bring up a ton of background and detail. Yet the “official” and only announcers just repeated “oh my gosh” and statements of the obvious.

Where is our John Madden of sailing? Can’t the organization find a seasoned and colorful catamaran sailor to fill in the commentary? I can think of so many, I have to wonder how the current announcers were chosen.

3 Realities of Big Data Security

HD Moore has been quoted extensively in an article called “3 Inconvenient Truths About Big Data In Security Analysis“. I found it interesting although not quite on target. Here is a possible dose of reality for his three inconveniences. I’ve kept his paragraph headers the same for clarity:

1. “Big Data Isn’t Magic”

HD tells us:

“People say if you have all of your data in one place, you’ll magically get the security benefit. That’s not true,” he says.

You know what else I bet is not true? That someone actually said “you’ll magically get the security benefit”. Sounds like HD had to prop up a straw-man argument in order to show us a knock-out argument.

Aside from that logical fallacy, I’ll discuss his more subtle point hiding behind the straw-man. Sales people are prone to making exaggerated claims.

HD is right. Finding meaningful insight in data is called a “science” for a reason. The complexity was highlighted recently at a presentation by SriSatish Ambati of 0xdata of an “open source math and prediction engine”. The presentation was called “Data Science is NOT Rocket Science” and about five minutes into the presentation a heckler in the audience yelled out “What was the title of this talk? I feel like I’m about to launch a rocket.”

Clearly even very intelligent and well-intentioned people are prone to overstate speed of value and ease of working with Big Data. However, this is where I disagree with HD. People are trying to market Big Data as easier than it is because they may actually believe it is NOT magic. Have you ever had a math professor say the subject is easy? They are not telling you it is magic.

To put this in perspective of other areas of science, Einstein was one of the biggest proponents of creativity and simplicity.

I know quite certainly that I myself have no special talent; curiosity, obsession and dogged endurance, combined with self-criticism have brought me to my ideas.

So if you are a company trying to sell Big Data, you are in the business of selling simplicity out of complexity. Perhaps if someone does not believe in science they would think they are being sold magic. Einstein’s point, that a transformation from the complex to simple requires an investment, is pretty-much the opposite of magic.

Should everyone really have to understand how results were achieved for our results to have value? I say no. Results have to be scientific, something that can be verified independently; I don’t think being unfamiliar with science means magic is the only other option.

HD himself reveals this when he calls for investment.

“So just be careful about where you invest, and make sure that if you are investing in a data analytics tool, you at least have one body sitting in front of it and you’re investing just as much in people as you are in the process,” he says.

At least one body? I disagree with that principle. It’s too vague to have meaning. What is that person doing? Robert Pirsig’s Zen and Art of Motorcycle Maintenance explores this dilemma at length but to put it briefly, some pay BMW a lot of money because they really have no idea how to build a motorcycle of their own. This does not mean they dedicate at least one body. They hire a mechanic as necessary, on demand.

So if HD had said make sure you have at least one person riding a motorcycle, ok fine I agree. Instead he seems to be saying make sure you have at least one mechanic on every motorcycle along with you as you ride it…

I do not disagree with a premise that you should invest wisely in people and process and technology to get the most benefit. Rather, I disagree that everyone has to peel back the covers on everything all the time (they instead can invest fractionally in someone else to do that for them) and…I also would like to see at least one example of someone who actually says Big Data is magic.

2. “Putting All Our Eggs In One Rickety Basket”

HD has a very good point here and takes it too far. This is the usual security professional lament to management: please verify that you can trust an environment. Put as a question: why and how should we trust any Big Data “basket”?

“We see a lot of stuff in development around big data toolkits — things like Mongo and Cassandra — and there’s not a lot of security built into these tools,” he says. For example, MongoDB doesn’t support SSL by default, and there isn’t the same level of security offered in similar tools as more established traditional relational databases. “It’s actually pretty frightening how insecure these tools are by default, yet they’re becoming the back-end for most of the big data services being sold today.”

Not frightening. Expected. New technology is often developed with priorities higher than security. Who is really surprised to read “stuff in development” and “not a lot of security built into” within the same sentence. What is frightening is that people would use this new technology without considering the risks. To put it more clearly we can see Hadoop continue to gain popularity, despite missing familiar controls such as communication encryption, as we leverage broader risk management strategies.

“You’re making these really juicy targets for someone to go after. Everyone kind of cringes when we look at some of those big password breaches in the past, but that’s nothing compared to a multiterabyte data leak.”

Telling executive management at some organizations that they have become a “really juicy target” might be taken as proof of success. After all, what is more successful than having assets of high value? And who said after a big password breach in the past “you know what, we should never again put our passwords in one place”?

Back to reality: First, some security controls are essentially impossible to implement in Hadoop so a business may have no choice but to move ahead after weighing risk of failure. Having no basket for eggs is in fact a worse option for some than having just one basket. I’m not advocating one basket, quite the opposite, but I’m saying there’s a cost associated with zero baskets. Second, perimeters and bastions make internal communication encryption far less important. We’re seeing some amazingly tight environments built because data owners know that they need a protected data lake to secure against unauthorized use. This is expensive, but it’s an option that allows a really juicy target to exist. Third, data processed does not have to be sensitive (although the definition of sensitive changes dramatically in Big Data environments). The juiciness of eggs (hey, it’s HD’s analogy, I don’t like it either) can be controlled when the environment can not.

3. “Law of Averages Says An Analytics Provider Breach Is Coming”

This is the grand finale of HD analysis, where he tells us the impact of the first two problems, and it seems to backfire.

“One thing that’s almost guaranteed to happen in the next year is we’re going to see one of the large providers of analytics services — whether security, log data, or something else — get breached,” he says. “It’s just the law of averages at this point. There’s enough folks offering services who don’t necessarily know what they’re doing that we’re going to see a big breach.”

Saying there will be a big breach within twelve months does not sound like Bernoulli’s “law of averages”. To me it sounds like a statement of the obvious. Almost every breach report I read indicates hundreds of breaches per year. Verizon in 2013, for example, issued a one-year report that starts with “621 Confirmed Data Breaches Studied”. So if I were a betting man I would say a big breach will come in the next 30 days…ok, 24 hours.

But seriously, it seems to me that predicting a “big breach within a year” is not the kind of statement that moves anyone to react quickly on an issue. HD said above in #2 that things are “actually pretty frightening” and yet he warns we have 8,766 hours before impact?

Most people will probably hedge their bets or adopt a wait-and-see response when told they are 12 months from impact. “Put that in the budget for next year” would be a lucky result.

Perhaps more importantly HD fails to mention why anyone would be required to report a Big Data breach to the public. Unless regulated data is in these environments, or someone external is affected, then what obligation is there to make the breach “seen” by us?

The Big Data examples he provides us (“whether security, log data…”) does not impact anyone external to the victim and has no legal requirement for disclosure.