Cloud Computing in Cyberwarfare
Cloud Computing in Cyberwarfare
2012
ALECSANDRU PĂTRAŞCU1
DIANA MAIMUŢ2
EMIL SIMION3
1. Introduction
Cloud computing, as defined by the National Institute of Standards and
Technology (NIST) [1], is a model for enabling convenient, on-demand network
access to a shared pool of configurable computing resources (e.g., networks,
1
Faculty of Automatic Control and Computer Science, University “Politehnica”
of Bucharest, 313 Splaiul Independentei, Sector 6, 060042, Bucharest, Romania,
e-mail: alecsandru.patrascu@gmail.com
2
Département d’Informatique, École Normale Supérieure, 45 rue d’Ulm, F-75230,
Paris Cedex 05, France, e-mail: maimut.diana@gmail.com
3
Advanced Technologies Institute, 10 Dinu Vintila, Sector 2, 021102, Bucharest,
Romania, e-mail: ati@dcti.ro
159
160 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
servers, storage, applications, and services) that can be rapidly provisioned and
released with minimal management effort or service provider interaction.
On the other side, cyberwarfare is defined by the U.S. government
security expert Richard A. Clarke in his book [2], as “a set of actions taken by a
nation-state in order to penetrate another nation’s computers or networks for the
purpose of causing damage or disruption”. In a simple way, we can say that
cyberwarfare is the modern representation of the classic information warfare
which is represented an Internet-based conflict involving politically motivated
attacks on information and information systems in order to hack, sabotage, or
espionage.
Within this paper, we will discuss about the security involving today’s
Cloud Computing deployments, with a short description of this model’s goal, as
well as its advantages and disadvantages. All presented sections are included
and detailed in [3]. At this point, ReC2S system contains the needed
infrastructure for supporting these features. Within Section 2, we present
security issues in Cloud Computing and within Section 3, we tackle new
directions with respect to this domain. In Section 4, we further give the
definition of homomorphic encryption and describe the way in which it can be
related with ReC2S. Throughout Section 5, we will tackle the possible
connection between Cloud Computing and cyberthreats and we will briefly
present today’s malware action and propagation methods. In Section 6, we will
detail the case of the Flame malware, a threat that was designed especially for
cyberwarfare purposes. Finally, we conclude our document and shortly describe
future directions for this research domain.
As mentioned before, the Cloud Computing model promotes availability
and is composed of: a) five essential characteristics (On-demand self-service,
Broad network access, Resource pooling, Rapid elasticity, Measured Service),
b) three service models (Cloud Software as a Service – SaaS, Cloud Platform as
a Service – PaaS, Cloud Infrastructure as a Service – IaaS), and c) four
deployment models (Private Cloud, Community Cloud, Public Cloud, Hybrid
Cloud).
The Cloud Computing model offers the promise of lower costs combined
with increased IT support. The fact that governments and industry must consider
adopting this technology can be viewed as a critical point. However, Cloud
Computing technology is not yet mature and raises many challenges within
today’s datacenters and application design, especially concerning security. As
Armbrust et al. mention in [4], information security is the main issue in case of
Cloud Computing and for this reason there are potentially additional barriers to
cross to make Cloud Computing environments as secure as in-house IT systems.
In order to ensure the secureness of the data (it cannot be accessed by
unauthorized users or simply lost, data privacy must be maintained), cloud
providers interact with the following areas: data protection and reliability,
Cloud Computing in Cyberwarfare 161
computing providers like Amazon EC2 and Microsoft Azure that the
data handling is made securely and nobody except the source of it can
intercept or decode it. Above all, recent studies have shown that is
possible for a malicious user to discover and map the internal
infrastructure of the cloud infrastructure [11].
2.2 Availability of cloud computing applications
In this category, we gathered vulnerabilities concerning critical
applications and the availability of data they are processing. Well-publicized
incidents of cloud outages include Google Mail (one day in October 2008, two
hours on September 2009 and almost one day in February 2009), Amazon (over
seven hour on 20 July 2008 and up to 36 hours on July 2011).
Concerns in this category include:
– Cloud applications uptime. The same problem arises here, just like in
Traditional Security in a Computer Network section mentioned above.
Cloud providers are often too confident on their infrastructure and tend
to propagate this false assurance feeling to the end users and publish
lots of graph and white papers comparing their server’s uptime to the
one in a regular datacenter or network. Also, another issue appears
with the possibility of third-party cloud providers to fully scale to a
certain application requirements.
– Single point of failure. From the user point of view, cloud services
are thought of as providing more availability. This can be true only if
the providers assure that no possible points of failure and attack exist.
– Valid computation. The question that is issued here is how can a user
or an enterprise be assured that a cloud provider is correctly running a
hosted application and giving valid results? One example is Stanford’s
Folding@home project, which gives the same task to multiple clients
to reach a consensus on the correct result, but unfortunately this is not
a general behavior in cloud providers.
2.3 Third-party data privacy
This category contains vulnerabilities of legal implications of the data and
applications being held by third-party cloud providers. In this case, a lack of
control and transparency may be noticed. Because these issues are not fully
understood, users and more often companies prefer to implement their own
private clouds.
Concerns in this category include:
– Auditability. The problem in this case is quite different from the one
mentioned before: How can a cloud provider make sure that it offers
enough transparency for audit purposes? Also, how can the companies
responsible with audit be sure the information gathered is real and
Cloud Computing in Cyberwarfare 163
3. New Directions
Considering current evolution of cloud computing and cloud providers
some new directions, which will become more and more important over time,
emerge. According to the Cloud Computing Journal [12] the technology
advances very fast within this new domain and, most important, “for the last
three years there has been no technology that is expected to have a
transformational impact in the next couple of years” [13]. It’s easy to see the
need of improvement with respect to this area.
We further describe some of the new directions in cloud computing
securities (which, in our opinion, are the most important ones):
164 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
over Gentry’s scheme by giving smaller key and ciphertext sizes, but still not
fully practical. C. Gentry and S. Halevi presented at Eurocrypt a working
implementation of their research [31]. In 2011, J.-S. Coron, D. Naccache, and
M. Tibouchi presented a compression technique for reducing the public key size
of DGHV scheme [32]. Also, in December last year, C. Gentry, S. Halevi, and
N.P. Smart described in [33] an improvement of Gentry’s bootstrapping
technique (the only known one that gives a “pure” FHE scheme).
The reader may wonder how an FHE scheme can be described. As we can
see in [17] and [14], an FHE scheme includes the next four algorithms: the key
generation one (Keygen), the message encryption algorithm (Enc), the message
decryption one (Dec), and the homomorphic evaluation algorithm (Eval).
A scheme is fully homomorphic if for any boolean circuit
f : ^0, 1` p ^0, 1` , inputs m1 , ..., mA having values in ^0, 1` , pair of keys
A
rely on Amazon Cloud Computing infrastructure. One day, you notice that you
can’t process payments because the online credit card transaction processor is
under attack. Then, you notice that the entire payment infrastructure goes down
because Amazon is also under attack. Company X Mail servers are also facing a
Distributed Denial of Service attack. Finally, you can’t even send requests for
support to the card processor, the payment infrastructure or even the email. At
this point your company is effectively knocked off from the Internet, even if
your own website is up and running.
The previous scenario, even if it seems a nightmare for any company, it
was put to practice in reality. A croudsourced group of pro-Wikileaks activists
have taken down, for a short period of time, the entire mentioned infrastructure
for companies like Paypal or Mastercard. Some were even more unlucky: the
PostFinance bank, a Swiss bank that shut down Wikileaks funding was down for
33 hours in the late 2010 [35].
Internet infrastructure is nowadays characterized by a major problem: the
more interconnected we are, the more dependent on the third-party technologies
and the more vulnerable we are in front of these attacks. The unpleasant part is
that we cannot disconnect ourselves from a certain supplier or the Internet these
days. One solution is to use multiple service providers as a backup. This allows
remaining online in case of an outage.
Cyber threats are no longer just a theoretical subject left over the last
pages in the security books. As we are starting to have an online life in parallel
with our physical life, they are a real threat. In our days, Internet Technologies
optimize the time needed for taking human and organizational decisions. For
example, we are using Internet for electronic communications, electronic
commerce, transactions and banking, for accessing different data bases in order
to process the information. All these actions, which interact with virtual
activities, must be protected from electronic fraud. Thus, we need to implement,
in the virtual space, security measures similar to real security measure.
But there is a difference: behind real life thefts there are humans which
interact with the goods and in the virtual space the thefts are made by viruses,
worms, malware applications which interact and monitor the actives of the
system. If we think that all these weapons (viruses, worms, malware applications
etc.) are produced by humans we can conclude that in the protection of the
system actives the human intelligence plays a definitive role and the critical
decisions must be taken by humans.
The problem is how to order these decisions (which are many) in such a
way that to be made, corrected and modified by a limited human intervention.
Terms like “zero-day attacks”, “botnets” and “malware” are becoming an
increased problem and are mentioned more and more. We will briefly present
these threats in the next paragraphs.
168 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
6. Flame
Flame malware was discovered on 28th May 2012 by the Iranian MAHER
CERT, Kaspersky Labs and the CrySyS Lab. The news coming from
cybersecurity researchers sounded like a story from a science fiction movie: a
surveillance program laid dormant on computers around the world for years,
secretly turning on microphones, taking screenshots, copying files, recording
keystrokes, spreading through Bluetooth, and sending all the information to
unknown servers over the Internet. Following an investigation request by the
United Nations International Telecommunications Union, the discovery of
Flame, the world’s most sophisticated known weapon of cyberwar, was made
public. Many of the infected computers belonged to deliberately targeted home
users. The most worrying fact was that this fine crafted software escaped
evasion by the world’s best antivirus software suites for years.
170 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
More details about Flame, with brief information regarding the way it is
infecting hosts, spreading mechanism and the command and control servers can
be found in this paper’s appendix.
6.1 General characteristics
Called “Flame” by Kaspersky Labs and “Flamer” by Symantec, the
malicious code beats Stuxnet in size – the infrastructure-sabotaging malware
that is believed to have breached Iran’s nuclear program in 2009 and 2010.
Although Flame has both a different purpose and composition than Stuxnet, and
appears to have been written by different programmers, its complexity, the
geographic scope of its infections and its behavior indicate strongly that a
nation-state is behind Flame, rather than common cyber-criminals – marking it
as yet another tool in the growing arsenal of cyber weaponry.
The researchers say that Flame may be part of a parallel project created by
contractors who were hired by the same nation-state team that was behind
Stuxnet and its related malware – Duqu [36].
Newer threats are also influenced by Flame. The Gauss malware [37] was
discovered on 9th August 2012. It is a complex cyber-espionage toolkit designed
to steal sensitive data, with a specific focus on browser passwords, online
banking account credentials, cookies, and specific configurations of infected
machines. The online banking Trojan functionality found in Gauss is a unique
characteristic that was not found in any previously known cyber-weapons.
Early analysis of Flame by the security labs indicates that it is designed
primarily to spy on the users of infected computers and steal data from them,
including documents, recorded conversations and keystrokes. It also opens a
backdoor to infected systems to allow the attackers to tweak the toolkit and add
new functionality.
The malware, which is 20 megabytes when all of its modules, with all the
versions are installed, contains multiple libraries, SQLite3 databases, various
levels of encryption – some strong, some weak – and 20 plug-ins that can be
swapped in and out to provide various functionality for the attackers. It even
contains some code that is written in the LUA programming language – an
uncommon choice for malware programming.
Flame appears to have been operating in the wild as early as 2007, though
it remained undetected by antivirus companies. As stated by security
researchers, “it took us half a year to analyze Stuxnet. This is 20 times more
complicated. It will take us 10 years to fully understand everything”.
Among Flame’s many modules is one that turns on the internal
microphone of an infected machine to secretly record conversations that occur
either over Skype or in the computers near vicinity, a module that turns
Bluetooth-enabled computers into a Bluetooth beacon and a module that grabs
and stores frequent screenshots of activity on the machine, such as instant-
Cloud Computing in Cyberwarfare 171
messaging and e-mail communications, and sends them via a covert SSL
channel to the attackers command-and-control servers.
The malware also has a sniffer component that can scan all of the traffic
on an infected machine’s local network and collect usernames and password
hashes that are transmitted across the network. The attackers appear to use this
component to hijack administrative accounts and gain high-level privileges to
other machines and parts of the network.
It is also the first malware to use “prefix collision attacks” and uses five
different encryption modules based on substitution tables and linear feedback
shift registers.
What is interesting is the built-in capability to “suicide”. Compromised
computers regularly contact their pre-configured control server to acquire
additional commands. Following this request, the C&C server shipped them a
file named browse32.ocx. This file can be summarized as the module
responsible for removing Flame from the compromised computer. One could
also call it the “uninstaller”.
The module contains a long list of files and folders that are used by
Flamer. It locates every file on disk, removes it, and subsequently overwrites the
disk with random characters to prevent anyone from obtaining information about
the infection. This component contains a routine to generate random characters
to use in the overwriting operation. It tries to leave no traces of the infection
behind. It is natural that this component has not been seen and recovered from
the field, but instead it was captured in honeypots. Any client receiving this file
would start to remove all traces of Flame from the infected computer, including
this module itself.
6.2 Command and control servers
Since both Flame and Duqu appear to be targeting similar geographical
regions and have been created with similar goals in mind, we will provide an
analysis from the point of view of comparing the Flame C&C infrastructure with
the Duqu infrastructure.
These C&C servers resemble very much with a Cloud infrastructure
today. As malware is becoming smarter with every generation found in the wild,
we cannot see that the “traditional” one-computer way of infecting is rapidly
evolving and now is targeting whole computer networks, both personal or
public. This was a direct result following the evolution of the Internet. If slow
dial-up or ISDN connections were available as a way of connecting to the
Internet about 12-14 years ago, now we can buy rather cheap subscriptions from
ISP’s with a very large connection speed. This aids the malware designers,
allowing them to create large computer networks, which cooperate and work
together, with a single point in mind: helping a malware spread, auto-update,
collect and process data from the users. We can easily see that the points
172 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
mentioned before are the same as the promises made by the Cloud Computing
technology.
In the past, Kaspersky Lab analyzed the Duqu C&C infrastructure and
found several important details, such as the attackers preference for CentOS, the
use of SharpSSH to control the proxy servers and the huge number of hacked
proxies used to hide the true identity of the attackers.
In the case of Flame, a similar analysis was performed. First of all, it is
interesting to point out a big difference between Flame and Duqu: while all the
Duqu C&C proxies were CentOS Linux hosts, all of the known Flame C&C are
running Ubuntu.
Additionally, while Duqu used the super stealthy way of hiding the true IP
of the mothership using SSH port forwarding, Flame’s scripts are simply
running on the respective servers. The reason is simple – on Monday May 28, all
control scripts started returning 403/404 errors. In the case of Duqu, the real
malware scripts were on a remote server and were never found.
From this point of view, we can state that the Duqu attackers were a lot
more careful about hiding their activities compared to the Flame operators. In
Table 1 we can see a comparison between the Duqu and Flame C&C
infrastructure.
When a computer is infected with Flame, it uses a default configuration
which includes 5 C&C server domains. Before contacting these servers, the
malware validates the Internet connection by trying to access
www.microsoft.com, windowsupdate.microsoft.com, and www.verisign.com
using HTTPS. If the connection is successful, it will proceed to talk to the C&C
domains.
In addition to the static configuration, Flame maintains a database of
additional 5-6 C&C servers. In total, a running Flame installation can use a list
of about 10 domains to try to contact the C&C. Interestingly, Flame maintains a
log of activities which includes reports of connections to the C&C servers
together with timestamps.
While analyzing the Flame samples recovered from the Middle East, we
noticed they were trying to contact 5 different domains. Additional
configuration included 6 other domains. From activity logs, there were
recovered 5 other domains, from a total of 11 unique domains used by the
malware.
By looking at the IPs where the servers were hosted, there were identified
another 30 domains which were hosted on the same machines. By checking the
IP history of the additional domains, we discovered another 40 domains which
appeared to be connected. In total, over 80 different domains which appear to
belong to the Flame C&C infrastructure were discovered.
Cloud Computing in Cyberwarfare 173
The Flame C&C domains were registered with an impressive list of fake
identities and with a variety of registrars, going back as far as 2008. In general,
each fake identity registered only 2-3 domains but there are some rare cases
when a fake identity registered up to 4 domains.
Table 1.
C&C server comparison between Flame and Duqu
Flame Duqu
Server OS Ubuntu Linux CentOS Linux
Running remote
Running on
Control scripts through SSH port
servers
forwarding
Number of victims
50+ 2-3
per server
Connection SSL and some
SSL
encryption proprietary AES
Compression Yes, Zlib and
No
of connections PPMD
Known C&C’s
80+ n/a
domains
Known C&C IPs 15+ 5
Proxies used to hide
Unknown 10+
identity
Time zone of C&C
Unknown GMT+2/GMT+3
operator
Infrastructure
Unknown .NET
programming
Built-in C&C
5, can update list 1
IPs/domain
SSL certificate Self-signed Self-signed
Servers status Most likely bought Most likely hacked
SSH connections Yes No
7. Conclusion
As a conclusion, we can state that fast advances in cybercrime and
cyberwarfare technology and techniques have resulted since the beginning of
2012 in an unprecedented rise in data breaches. We think that we need planning
in order to ensure that our online world is trustworthy and secure and as a direct
result we need to consider the fundamental changes that are occurring in the
cyberspace and try to adapt to them. Cloud Computing, being a new direction
for the entire cyberspace, together with the perspective on security issues of
174 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
such systems and their implications in today’s malware are beginning to get
more and more attention from researchers community and governments. In our
opinion, looking forward into the future of the 3 billion Internet users existing
today we can see four big directions for resolving the cyber security issues:
online users security education, mobile devices cryptography, online data
obfuscation, and Cloud services transparency and security.
References
[1] http://www.nist.gov/itl/cloud/index.cfm
[2] R.A. CLARKE, R.K. KNAKE – Cyber War: The Next Threat to National
Security and What to Do About It, Ecco, New York, NY, 2010
[3] A. PĂTRAŞCU, C. LEORDEANU, C. DOBRE, V. CRISTEA – ReC2S:
Reliable Cloud Computing System, Proc. of the European Concurrent
Engineering Conference, ECEC 2012, pp. 54-60, Bucharest,
Romania, Apr. 18-20, 2012
[4] M. ARMBRUST, A. FOX, R. GRIFFITH, A.D. JOSEPH, R.H. KATZ,
A. KONWINSKI, G. LEE, D.A. PATTERSON, A. RABKIN,
I. STOICA, M. ZAHARIA – Above the Clouds: A Berkeley View of
Cloud Computing, Technical Report No. UCB/EECS-2009-28,
University of California, Berkeley, CA, Feb. 10, 2009
[5] Security Guidance for Critical Areas of Focus in Cloud Computing V.30,
Cloud Security Alliance, https://cloudsecurityalliance.org/
guidance/csaguide.v3.0.pdf, Nov. 14, 2011
[6] R. CHOW, P. GOLLE, M. JAKOBSSON, E. SHI, J. STADDON,
R. MASUOKA, J. MOLINA – Controlling Data in the Cloud:
Outsourcing Computation without Outsourcing Control, Proc. of the
ACM Workshop on Cloud Computing Security, CCSW 2009, pp.
85-90, Chicago, IL, Nov. 13, 2009
[7] http://www.vmware.com/
[8] http://www.citrix.com/lang/English/home.asp
[9] http://www.microsoft.com/en-us/server-cloud/windows-server/hyper-v.aspx
[10] http://wiki.openvz.org/Main_Page
[11] T. RISTENPART, E. TROMER, H. SHACHAM, S. SAVAGE – Hey, You,
Get off of My Cloud: Exploring Information Leakage in Third-Party
Compute Clouds, Proc. of the 16th ACM Conference on Computer and
Communications Security, CCS 2009, pp. 199-212, Chicago, IL, Nov.
9-13, 2009
[12] http://cloudcomputing.sys-con.com/
[13] http://cloudcomputing.sys-con.com/node/2154641
Cloud Computing in Cyberwarfare 175
Appendix
178 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
Appendix (continued)
Cloud Computing in Cyberwarfare 179
Appendix (continued)
180 ALECSANDRU PĂTRAŞCU, DIANA MAIMUŢ, EMIL SIMION
Appendix (continued)
Copyright of MTA Review is the property of Military Technical Academy Publishing House and its content
may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express
written permission. However, users may print, download, or email articles for individual use.