Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Cloud Security, Java IoT, Microservices Expo, Microsoft Cloud, Containers Expo Blog, @CloudExpo

Cloud Security: Article

Cybersecurity: A Human Problem

It seems that Cyberwar is no longer science fiction. It’s a reality, and we’re in the midst of one.

The latest Cyberattack to hit the news: a worm called Gauss, a relative of Stuxnet, targeted certain Lebanese banks. Kaspersky, a Russian security firm, discovered the attack. On their blog post, the Kaspersky researchers note that “after looking at Stuxnet…, we can say with a high degree of certainty that Gauss comes from the same ‘factory’ or ‘factories.’ All these attack toolkits represent the high end of nation-state sponsored cyber-espionage and cyberwar operations, pretty much defining the meaning of ‘sophisticated malware.’” They go on to say that “this is actually the first time we’ve observed a nation-state cyber-espionage campaign with a banking Trojan component.”

And this after a New York Times article exposed Stuxnet as being a joint US-Israeli covert operation targeting the Iranian nuclear industry, authorized by President G. W. Bush and further authorized by President Obama. The article further suggests that Iran is now mounting its own Cyberwar initiative, a result that the Obama administration understood and feared.

It seems that Cyberwar is no longer science fiction. It’s a reality, and we’re in the midst of one.

Whether you think the Stuxnet and Gauss worms were a good idea or not, this article is not the place to debate moral or ethical questions. Rather, we’re here to help you understand the reality of the situation in order to provide insight. And like it or not, we have a Cyberwar on our hands—and as with other wars, technology defines and constrains the rules of engagement. Yesterday we may have spoken about tanks or guns; today we speak of viruses and worms. But as with traditional machines of war, the human element is every bit as important as the technology, if not more so.

Problem between Keyboard and Chair
Here are some examples of what we’re talking about. When the press heard about the Gauss exploit, they asked the obvious question: who would benefit from attacking Lebanese banks? The obvious answer: anyone interested in the secret financial dealings of Hezbollah, the terrorist organization based in Lebanon. In other words, Israel and the US. The appearance of Gauss led many people across the world to come to a similar conclusion.

Assume for a moment, however, that someone wanted to make Israel and the US look bad, say the Iranians. Could the Iranians have come up with Gauss in order to gain political advantage against Israel and the US? Unlikely, perhaps, but possible. How would we know? After all, if the US and/or Israel were behind Gauss, they could have hidden their motivation simply by expanding the target to banks outside Lebanon. So maybe the fact that Gauss had such a narrow target should suggest that someone was trying to frame the US and Israel?

Here’s another twist: Kaspersky Lab was founded by Eugene Kaspersky, a Russian cryptography expert who learned his trade from the KGB’s cryptography school. Presumably he has substantial ties with Russia’s current secret police as well. Perhaps the Kaspersky report on Gauss was either fictitious or somehow skewed, a dastardly Russian plot of some sort? We have no reason to believe so, but again, how would we know for sure?

Sounds like a Robert Clancy spy novel, and for good reason—subterfuge has been a part of warfare (and in particular, espionage) since the Stone Age. But the problem is, the more we focus on the technology, the less we focus on the human aspects of the Cybersecurity problem. And that lack of focus both makes us more vulnerable, and prevents us from mounting efficacious attacks of our own.

Agile Architecture and Cyberwarfare
In a recent ZapFlash we recommended a “best defense is a good offense” approach: preventing future attacks with agile, self-innovating software. But even the most cutting-edge code is only a part of the story, because it still doesn’t address the human in the system. Targeting people is nothing new in the world of Cyberattacks, of course. Social engineering is becoming increasingly sophisticated as hackers plumb the weaknesses of our all-to-human personalities. Not a day goes by without a phishing attack arriving in our inboxes, not to mention how easy it is to talk people into giving up their passwords. But while social engineering works with individuals, Cyberwar is presumably between countries. How, then, might we go about what we might call political engineering: the analogue to social engineering, only taking place on the global stage? And how do we protect ourselves against such attacks?

The answer to both questions is to focus on how technology-centric actions will influence human beliefs and behavior. Creating a sophisticated computer virus and releasing it may achieve a technical end, the result of the software itself. But it will also likely achieve a variety of human ends, as well: it might arouse suspicion, cause people to shift their priorities or spend money, or it might make someone angry enough to retaliate, for example. Furthermore, these human ends may be more significant and desirable than the actual impact of the software itself.

ZapThink considers the focus on human issues as well as technology to be an aspect of Agile Architecture. We’ve spoken for years about the role governance plays in Agile Architectures like SOA, because governance is a best practice-driven approach for bringing human behavior in line with the goals of the organization. The big win for SOA governance, for example, was leveraging SOA for better organizational governance, rather than simple governance of the SOA initiative. The essential question, therefore, is what architectural practices apply to the human side of the Cybersecurity equation.

Our Cybersecurity example is analogous to SOA governance, although it turns governance inside out: we’re no longer trying to influence human behavior inside our organization, but rather within the world as a whole or some large parts of it. But the lesson is the same: the technology influences human behavior, and furthermore, the human behavior may be more important than the technology behavior. Protecting ourselves from such attacks also places us in the greater context of the political sphere as well.

Playing Defense

Education is the key to protecting yourself and your organization from human-targeted Cyberattacks. Take for example a phishing attack. You receive an email that looks like it’s from your bank. It tells you that, say, a large withdrawal was just made from your account. If you don’t realize it’s a phishing email, you might click on the login link in the email to check your account to see what the problem is. The link takes you to a page that looks just like your bank’s login page. But if you attempt to log in, you’re only giving your credentials to the hackers.

There are automated anti-phishing technologies out there, of course, but the hackers are always looking for ways around them, so you can’t rely upon them. Instead, you must proactively influence the behavior of your employees by educating them on how to recognize phishing attacks, and how to avoid them even when you don’t recognize them. Still not foolproof, but it may be the best you can do.

Protecting against political Cyberattacks would follow the same pattern, but would be far more difficult to implement, as educating a populace is far more difficult than educating your employees. Instead, the most effective course of action may once again be a good offense: you can use the same techniques as your opponent to influence beliefs and behavior.

Let’s use the hacker group Anonymous as an example. Any member of this loose association of hackers can propose an action—from taking down the MasterCard Web site to finding the location of a fast food worker who stepped on the lettuce, to name two real examples—and any member can vote to take that action. There’s no central control or consistent strategy. Now, let’s say you worked for a government Cyberwar department, and you were responsible for creating a Gauss-like worm with a narrow target, only you didn’t want anyone suspecting it was your country who created it. Could you make it look like Anonymous created it? Even the members of Anonymous might not realize their group wasn’t actually responsible.

The ZapThink Take

Your sphere of concern might not involve international espionage, but there are important lessons here for every architect. All too often, techies get techie tunnel vision, thinking that technology problems have technology solutions, and furthermore, the only interesting (or important) problems are technology problems. Architects, however, must also consider the human in the equation, whether you’re fooling the Iranians, making sure interface specifications are properly followed, and everything in between.

This principle is no truer than when you’re protecting against Cyberattacks. No password scheme will prevent people from writing their passwords on Post-It notes and sticking them to their computers. No firewall will prevent all phishing attacks or stop people from visiting all malware-infected sites. Education is one technique, but there’s more to governance than education. And whatever you do, always cast a skeptical eye toward any conclusions people draw from news about Cyberattacks. The technology is never the whole story.

If your job, however, is mounting Cyberattacks, understanding the human in the equation is a critically important tool—and often far less expensive and time-consuming than a purely technical attack. As any good poker player will tell you, the secret to winning isn’t having good hands, it’s knowing how to bluff, and even more importantly, knowing how to tell when the other guy is bluffing.

More Stories By Jason Bloomberg

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.