They call me the content machine. I write about information security topics, with an emphasis on cryptography and distributed denial-of-service (DDoS) attacks. I've written for DarkReading, SC Magazine, and Network World. But most people know me from my monthly column at SecurityWeek.
Click the selectors in the Content pane to filter the content.
Debbie Walkowski interviewed me about my 'Post-Quantum' report. Consider this the cliff notes to that larger paper.
All, all those branded SSL vulnerabilities. True to my word, I've continued writing articles comparing them to each other so you can have some idea about how much to freak out. This article adds two more; the DUHK and ROCA vulnerabilities.
SecurityWeek mentions an old column of mine about HTTP Strict Transport Security (HSTS).
After a conversation with a chip-maker, I did a bunch of research into Quantum Computing, and collected my notes into this pretty cool report.
My response, representing the vendor community, to US-CERT's warning about SSL interception products.
Ladies and Gentlemen! Gamers and Cryptoheads! Have you ever wondered which major gaming console has the best message encryption? Well, I’m going to reveal the clear winner in my own recent personal test.
Took me three years to compile the data for this report. It started out as a personal project that I wrote in a hotel room in Cologne Germany over a weekend. But hundreds of hours and millions of computer scans later... this report. It's all about global encryption trends over a three year period, with some analysis about why each trend is going the way it is. Warning: usual doses of Holmes humor contained within.
I wrote, starred in, or was mentioned in 48 pieces last year. A new record. Here's the best of them.
Q: Explain who you are and what you do
Thank you. Before we start, I need you to promise me something. You can only ask me one question about Donald Trump, okay? No more than that.
Q: How long have you been at F5?
I’ve been at F5 for 16 years, which is an eternity in the tech world. I was the last person hired during the so-called dot-com bust, during which time a hiring freeze was put in place. On my first day, there were already rumors of layoffs, and I thought “oh no, I am the new guy, of course they will eliminate my position!” So I worked day and night to show my value but I six months later I was still “the new guy”. One day the police sent us a picture of a dead body in an F5 T-shirt and I thought “oh no, the reduction in workforce is really starting!” But it turned out to be a homeless man who had gotten the shirt from the local food bank. Anyway…
Q: Many people know F5 from their ADC solutions, why the increased focus on security these days?
Yes, many people know F5 as the world’s most-expensive, I mean the world’s best load balancer, but what they don’t realize is that we’ve spent the last 10 years moving into Security. There are two reasons for this.
First, the reason it is called an ADC and not just a LB is because it naturally consolidates adjacent functions, such as caching or acceleration but now security functions like firewalls as these technologies become commodities.
Second, F5 is the number one commercial SSL termination device. If someone is paying to decrypt SSL, they are most likely deploying F5 devices. As more and more of the world’s traffic goes encrypted, it makes the F5 the first device in the network that can do layer 7 security controls. And that means attaching WAF functionality, or doing cookie inspection, or passing through to devices like FireEye. Q: You travel the globe as part of your job – do you see that security has a different place on the agenda here in Europe than North America for instance?
This is my 13th country, and fourth continent visited in 2016. So I do get to see a bit of how businesses are dealing with security around the world. What I can say about Europe is that continually impressed at the technical depth of the security professionals here. In my opinion, Europe has the best defensive security expertise in the world. There are so many excellent security conferences here, such as the CCC in Germany, RSA Europe and Hack-in-the-box in Amsterdam. The level of security awareness among everyday operations people is excellent as well.
Belgium functions as a hub in Europe. Many organisations have European headquarters here and you have institutions like the European Parliament and NATO. Naturally the security demands of these organisations are extremely high. Perhaps this is also one of the reasons the security expertise in EMEA is so high and organisations like Securelink are instrumental in maintaining the security at the highest level.
I remember one conversation I had with a customer in eastern Europe, and then first thing he said was <accent here> “David, ve will not put our data in Amerikan cloudt.”
Q: What about Australia or New Zealand?
Australia is the opposite. They are SUPER friendly with public cloud. In 2012 one of the CIOs of their four banks gave a keynote where he announced that his bank was aggressively adopting a “cloud first” strategy. Now there are telcos there that are trying to re-sell “multi-cloud” solutions but it’s tricky. Multi-cloud might seem like the ultimate availability solution, but I think we’re years away from consistent, reliable APIs.
Q: What about Africa?
Africa has its own challenges. In Nigeria, distributed denial of service is getting to be a thing, so of course we try to sell them our DDoS service. This service is classified as “Insurance” but nobody in Nigeria believes in insurance and even if they did, they want the premium to be approximately 0 euros.
Also, a big security thing in Africa right now are little plastic physical locks that you put on your Ethernet ports. They are locked with a key. [ aside: they keep the key taped under the desk ]. That’s Africa.
Q. We see many organisations looking at their cloud strategy, public vs private etc. How do you think organisations should handle their security when moving to a hybrid or public cloud scenario?
Let me give you three short cuts for cloud security, whether that’s public, private or hybrid.
For users, deploy federated logins using SAML assertions. You get SSO and don’t have keep your passwords in the cloud. And if you do it right, you can even prevent your passwords from ever transiting to the cloud and back. There’s a trick to it and we’re helping a lot of people right now who are transition to Office 365 and don’t want the CXO passwords going to Microsoft.
Second, for applications, when possible, embed your application security policy into your applications! So if you move them to the cloud, the policy goes with them. Or if they burst here and there or jump clouds, the policy goes with them too.
Lastly, if you’re considering moving to the cloud, leave your really old legacy stuff behind. If an app isn’t based on a recent Windows or Linux suite, it’s often not worth moving it to the cloud. The analyst firm Securois has an interesting term for people who try to move their really old apps to the cloud: cloud tourists. They visit the cloud, look around, start to spend some money, realize that it’s a sunk cost and not going to get them any value, and they go back home.
Q. Let’s talk about so-called Hacktivism. You track Anonymous, right? What is Anonymous doing?
I love anonymous. They used to have a brilliant leader named Sabu (expand). But lately they’ve been somewhat floundering – not a real central figure since then ( e.g. Anonymous 127.0.0.1 story).
However, they have launched their own political party in the United States called The Humanity Party, or ThuMP for short. It has three main tenants, the first of which is to establish a single, united one-world Government (the United Kingdom has already voted out of it). The other two are social equality and um, free WiFi for everyone. Can’t say I disagree with that last one. Instead of donations they invite you to Like their Facebook page.
Q. Let’s talk a moment about cryptography and SSL. What is new there?
Ivan Ristic, the author of the book “Bulletproof SSL/TLS”, runs an SSL scoring service over at Qualys SSL Labs. The scoring uses the grading system, A, B, C, D, F, which is nice because I can remember that.
So for the last five years, half the SSL administrator’s I’ve worked with are trying to get an A+ on their website. And it’s not just pride because people are writing articles basically “SSL shaming” entire industries. It started in Australia where Troy Hunt (the owner of the HaveIBeenPwnd website) posted the scores of all the banks in Australia.
But I’ve seen that done in Poland and even here Belgium as well. In the states, someone posted the SSL scores for all of the presidential candidates. Wouldn’t it be cool if that’s how we actually choose our presidential leaders? By their cryptographic security posture? That would be much better than how we’re doing it now, because apparently whatever we are doing isn’t working very well.
Would you like to know what Hillary Clinton gets?
She gets an A, but it’s actually a private server in her laundry room.
Q. What do you see as the most serious security threat?
There are rumors of the Russian’s hacking our election and trying to throw it to Donald Trump. Why they would do this, other than as the ultimate party joke, is sort of beyond me. But it is quite concerning. Security professionals have been warning about the dangers of automated voting systems for years, and I worry that people aren’t taking it as seriously as they should. I would imagine that you’ve been doing it here for years, and it’s working?
But if you meant “what are the most serious threats to the Enterprise” I’d have to say Malware. It has been the number one threat this year, and the last five years running. That’s why FireEye was such a security darling. The biggest problem with malware, at least in the states, is that all the malware authors know that they need to hide their malware inside SSL connections so it won’t be detected.
In the States we can decrypt that traffic (if the customer wants) and clone it over to FireEye or an IDS. You can’t do that in many places here in Europe, and I’m interested to see how that works out. Q. To what extent is IoT the next driver for increased security risks?
Do you know what an oxymoron is? Two words that don’t go together, like ‘military intelligence’ or ‘found missing’ or ‘Microsoft Works’. Well ‘IoT Security’ is like that. It used to be a joke until about 2 weeks ago, when someone launched a 620 Gbps attack using (at least partly) a new IoT botnet. That was the largest DDoS attack I’m aware of, though the record has possibly been broken since then.
Most IoT devices connect one-way up to a cloud module, so that’s good. I think IoT security is going to be a huge issue for a long, long time because that’s basically a brand new industry. I mean, the Internet has been around for 30 years and it’s still far from secure even with every researcher in the world trying to fix it, so why would anyone assume the IoT universe won’t be anything but suboptimal?
I think for Europe this is a real challenge and opportunity. Germany is still the economic powerhouse of Europe, and they rely on manufacturing. They absolutely have to get IoT security right as they build their internet-connected cars and airplane engines.
Q. How can do you provide protection against multi-faceted DDoS attacks?
I just wrote a whitepaper called the 2016 DDoS Trend analysis, and buried within that paper are 8 references to Huey Lewis. I mention that because no one has been able to locate them all yet and I have gift card I need to give away.
But in our paper we note that we now see the majority of DDoS attacks as comprising multiple attack vectors and they’re getting more sophisticated, too. For example, stateful TCP floods are way up, and on some days they are outnumbering stupid UDP floods.
So we have some customers who don’t want to deal with any of it at all and just contract us to handle all their attacks for them 24/7. But many other customers are going for a blend of cloud-protection and on-premises DDoS.
For on-premises, if you have an F5, there’s a LOT you can do. We have a best practices document that shows you how to handle every DDoS attack type we’ve ever seen. Just google ‘David Holmes DDoS Recommended Practices’ and you’ll find it.
Q. Looking in a crystal ball, where do you think the security threats will come from in 5 to 10 years?
First, let me say that I think people are terrible at predicting the future. Just awful. With that said, let me um, try to predict the future.
I think finding sufficient entropy will continue to be a source of frustration among security professionals. Computers today are awful at getting real random data from which to generate keys or other cryptographic material, so everyone cheats at this. Professor Nadia Heninger from the University of Michigan has done some amazing work here [talk a little about her work]
Time synchronization is going to be another sore point. Real authentication and authorization systems require at least some kind of crude but secure time synchronization. The Internet has always been terrible about this so both Microsoft and Google are coming up with their own secure time mechanisms.
Lastly, as I get older, I am really hopeful that we will achieve The Singularity before I expire.
In this piece, yours truly evaluates the SWEET32 cryptographic attack relative to other SSL cryptographic attacks such as DROWN and BEAST.
We commissioned the analyst firm IDC to do an encryption survey. They asked questions that I always wanted to know the answer to. So what does that have to do with goat parkour? Read on and find out.
David Holmes clarifies how the SSL Orchestrator makes outbound SSL faster and more resilient
SecurityWeek reported that Microsoft disabled the RC4 cipher in Edge and Internet Explorer 11, and referenced David Holmes’ byline column from last year about the simplicity of RC4 being its greatest appeal.
F5 commissioned the analyst firm IDC to survey hundreds of infosec professionals. The goal was to find out exactly how much enterprise traffic is encrypted. Their answers? Between 25-50% in 2016. That's a lot! Read the survey to find out how infosec is dealing with all the encrypted traffic, and the malware that hides within.
Here's a more technical version of my article that came out of a customer visit to Oslo. This has to do with Dan Bernstein's elliptic curve 25519, and how its unexpected deployment threw off a competitor's inspection.
You’ve been having trouble sleeping because of the SSL visibility problem with all the fancy security tools that don’t do decryption. Put down that ambien, because this Lightboard Lesson solves it. In episode, David Holmes diagrams the Right Way (tm) to decrypt and orchestrate outbound SSL traffic, improving SSL visibility, decreasing failures and improving network performance.
I heard about this problem with a customer in Oslo, Norway. It has to do with an advance in cryptography throwing surveillance devices into darkness.
This year's high-profile battle of wills between Apple and the US Federal Bureau of Investigation (FBI), which sparked worldwide discussions about the propriety of security 'back doors', was eventually resolved when the FBI found another…”We're seeing more and more Internet traffic encrypted over time, particularly after Edward Snowden came out and told everyone that people are watching them,” David Holmes, worldwide security evangelist with F5 Networks, recently told CSO Australia…
I’ve just returned from a long tour of Australia and New Zealand (ANZ), where some exciting developments are worth capturing. Both countries are island nations, and one thing Darwin noted in “On the Origin of Species” is that islands can become crucibles of evolution. Australia is evolving a new way to leverage cloud, and New Zealand is evolving a new efficiency model for government security services. Both countries share one aspect with the rest of the world: challenges around encryption.
A SecurityWeek article quotes me about SSLv3 and RC4.
It took me 23 hours to write this! But people LOVED IT. Continuing my tradition of the top security features of each F5 BIG-IP release.
During my last visit to Australia, I talked with some customers who were running into some fascinating problems trying to secure multiple components across different public clouds. Wrote it up for SecurityWeek.
Should you panic about the DROWN SSL vulnerability? Is it cute and kid-friendly, or is it a monster vulnerability coming to expose your most sensitive data? This piece I did for SecurityWeek builds upon the "Stack Ranking SSL Vulnerabilities" article I'd written the year before.
SecurityWeek quotes me about strict transport security.
I know it sounds like I pick on Let's Encrypt, the free, open CA. And I guess I do kinda. Not in a mean way, because what they are doing is pretty freaking cool. But in a skeptical way, because so often the road to hell is paved with good intentions. On the other hand, there are altruistic endeavors that I would have said would never work, like Wikipedia, and um, well that's about it. Anyway, this piece is a more measured look at the early public stages of Let's Encrypt.
SecurityWeek article quotes me about my favorite algorithm of all time, RC4.
Another of the famous top ten lists for F5. Selecting the best of over 100 security features is a daunting task. I had considered using the darts-against-printed-spreadsheets approach, but ultimately just went through them all, one by one, and selected the best, just for you. Remember, these are the hardcore security doodads, of interest to network operators, security engineers and the paranoid.
Here's the complete list of everything authored by yours truly in 2015. Except the NC-17 stuff, which I've been told should remain unpromoted. Actually, this website you're reading right now is basically my greatest hits, but this blog post gather just a single, awesome year of it.
This is is one of my favorite articles. There was a crazy rumor going around after the Paris attacks that the terrorists were using Sony PlayStations to communicate with each other. And that the PS4 encryption was hiding their communications from Europol. So I decided to find out what kind encryption the PS4 uses. And how resistant would it be to surveillance.
East-west data center traffic needs to be secured. Here's the easy way to do it with the load balancers you already have.
My love letter to my favorite algorithm of all time, RC4.
Strict Transport Security is a simple but very powerful security fix. So why does no-one use it? I explore the topic in this piece for SecurityWeek.
My third piece in the trilogy of articles I've written about the open CA "Let's Encrypt" for SecurityWeek. This one is a more measured look at how LE might impact Internet Security.
Here's one that came right from the field - we knew that iOS9 was coming, and was going to include changes for cryptography. Here's my write-up of what knobs everyone was going to have to turn to be compatible.
When the POODLE vulnerability came out in 2014, it was hailed as the death knell for SSL version 3. In the quarter just prior to POODLE, 98% of Internet sites supported SSLv3, but a year later that support had dropped to just 33%. Here's an article that shows you how to tell how much of your traffic is still SSLv3.
Cryptography has been a passion of mine since I was 9. NINE. I used to write code books to encrypt messages as a kid. So of course I gravitated to internet encryption, and spent a lot of time working with the Secure Sockets Library (SSL), which is now TLS. Here's a 50+ page magnum opus I wrote about the proper ways to use F5's SSL capabilities. Great stuff in here.
Not all SSL vulnerabilities are the same. Some are way worse than others, but often the media doesn't know that. My attempt to provide a relative scale based on quantifiable cryptographic assets. Also uses a cute Japanese Monster Alert level.
Banki coraz cz??ciej atakowane przez hakerów
Ataki na banki zdarzaj? si? wsz?dzie. Banki na ca?ym ?wiecie s? zaniepokojone hakerami i kradzie?? pieni?dzy.
Here's a 3 minute interview with yours truly in Warsaw, Poland. They have a polish guy talking over my audio track, which is neat if you know Polish. I don't.
An in-depth piece about the SSL Logjam vulnerability. How vulnerable are you, and here's how to mitigate it if you are.
LOGJAM was an exploit against SSL published in 2015. Here's me picking it apart and showing how to mitigate it with F5. I wrote this in a hotel room in Glasgow. Can't remember why I was there. Just killing time between engagements I think.
A tiny blog explaining this awesome graphic.
This was a great interview, got lots of coverage. Good chemistry between myself and the awesome Pete Silva. F5 Worldwide Security Evangelist, David Holmes, talks about why the internet is going SSL Everywhere. He explains why there’s been a surge in encrypted traffic and reveals some interesting statistics from his ongoing research on the SSL protocol. Always an engaging guest, David takes us through Forward Secrecy, Strict Transport Security and SSL v3. What they solve and how they are being used in the wild.
F5 launched a new web application firewall (WAF) in the cloud service. Here's my take on why it will succeed.
I submitted this piece with multiple possible titles. This was one that got chosen - the most inflammatory. But hey, strong opinions sell, I get it. Read the piece and see if it stands on its own, title notwithstanding.
I was born to write this article. It was floating around in my head for years and years, and finally came together. I've delivered a talk about the topic of RNG to dozens of audiences around the world, and the best parts of that talk are summarized in this SecurityWeek piece.
I've been scanning the SSL universe since the summer of 2014, so I was able to see the effects of the POODLE vulnerability. Here's the writeup I did on both for SecurityWeek.
This is wicked important, and you should read it right now. This could improve your entire cryptographic security posture. For free. You're welcome!
Here's a whitepaper I did on the expectation of SSL everywhere and what it means for business today. Topics covered include Forward Secrecy, Privacy, advanced key management and how to protect everything with an "always on" architecture.
An article I did for DataCenterKnowledge. A look back at 2014 and all the ShellShock and Heartbleed fallout for Data Center Knowledge. Nice, crisp piece. License for the xkcd image: https://xkcd.com/license.html
Here's an article where I compare Bitcoin (and other blockchain fintech) to another virtual currency, the one promoted and used by tens of millions in Africa: m-pesa.
I still get questions about this SecurityWeek piece, which is good because I'm quite proud of this one. It's a look at three different systems that tried to patch one of the nagging security "holes" in the Internet and why they all failed.
Here's where the Top Ten really started to get funky. Check out the mood music while you read this. It's David Holmes.
Caught between high-profile security breaches, APTs, and “millennial” employees who expect 24/7 Internet access, forward-looking IT organizations can consolidate web access and security into a highperformance, strategic point of control: F5 Secure Web Gateway Services.
This is almost top secret stuff. I probably shouldn't even be writing about it, but other's have, so if someone were to weaponize this, well I can't be held responsible. And at least I provided a defense.
This is the one that started it all! Okay so that means it was the worst, and yeah I hadn't figured out to do the top ten in reverse order yet.
My technical piece about the Heartbleed vulnerability. Also includes my own rant about OpenSSL. And how to scan your own network for it. And other cool stuff related to it.
Here's an old DevCentral video podcast featuring yours truly! Talking about security stuff of course
Written in 2012, this was a new way to think about Data Center Firewalls. Written with the amazing Lori MacVittie.
Here's an update to the SSL Renegotiation DoS article. This iRule is tighter and more performant, if that's even a word.
This is one of the articles that launched my career as a technical evanglist. I worked on this blog article in my spare time (waiting for builds) as a developer. It hit at just the right time and got a few mentions in the right places. And now here I am, doing this for a living.