cloud computing
Using Ephemeral Clients to Interface with Virtual Environments
When I come in to work every morning I follow a standard routine. First, I make sure to grab some coffee and fruit down at the cafe. I then check my email, voicemail, calendar, etc. and plan my day accordingly. Next, I catch up on the news - technical, political, weather, security, sports, etc. Trite, cliche, boring eh? Well, the way in which I go about accessing the Internet is somewhat unique....
A colleague of mine recently turned me on to the concept of 'ephemeral desktops'. The idea behind ephemeral desktops is simple. The reality is, an attacker can catch any one of us snoozing at any given time. Maybe clickjacking? Perhaps drive-by downloads? Phishing malware? etc. Inevitably, every organization at some point or another will have an employee fall prey to persistent malware and put their company's network at risk. Ephemeral desktops are a great tool for mitigating persistent malware threats. How do they do this? What exactly does this mean?
Getting back to my daily routine...before I check the news, I load a custom Ubuntu 9.04 live CD (that my colleague has put together). This Ubuntu live CD is read-only with a few useful applications to assist me in doing my job including both SSH and VPN clients. The idea behind the ephemeral desktop, in my case the tinkered with Ubuntu live CD, is that nothing can be written to disk. This means, no persistent malware can be written to disk because I am manipulating the Internet with a browser on a read-only CD. Perhaps, while using my ephemeral desktop, I browse the Internet and accidentally download some form of persistent malware. It really doesn't matter. The next time I boot from my Ubuntu live CD I will be starting, once again, from a clean state. I can lose the battle but still win the war.
The idea behind lightweight, ephemeral desktops, is auspicious considering the direction we are headed with the cloud. As for virtual environments, users require a client to interface with a particular environment. Currently, virtual environments rely too heavily upon these clients for functionality (scripting and condensed physics engines). It may be interesting to pursue research concerning ephemeral clients (with similar principles to the ephemeral desktop) that will always start from a clean state. Despite what malicious content may or may not have been downloaded from a previous virtual experience, a user can trust that no persistent malware has been written to their disk.
Delicious
Digg
TechnoratiSecurity Visualizations of Complex Systems in Virtual Environments
A few weeks ago I was fortunate to attend a talk concerning the utility of virtual and synthetic worlds. One idea mentioned was the concept of using virtual environments as a means of which to visualize and interact with complex systems. From a security perspective, complex systems and the amalgamation of varying components often result in many unforeseen security issues. Systems interacting with, and depending upon one another in ways they were not originally designed will leave holes in the fabric (a fun platitude for security folks to chew on once more). Unfortunately, no revolutionary solution for devising uniform, comprehensively secure systems from their genesis are coming any time soon. So what can the security community do to compliment these manifold systems?
This idea of using virtual environments to visualize complex systems is very powerful, especially from a security perspective. Visualization would provide security engineers (network admins, application developers, etc) to see, dynamically, how systems are working and interacting. For instance, if a Web server begins to see heightened traffic rates, perhaps a visual image of the Web server (a blue server box or something to make it uniquely distinguishable) would expand to raise a red flag of a potential DDoS attack. Perhaps, a visualization of a complex system would allow admins to see what different protocols (lines w/ different colors?) are being used for disparate systems to communicate. Maybe, with regards to the "cloud", visual representations for depicting VM segmentation and resource allocation could be used to symbolize data leaks between VMs, exposure to the host and hypervisor. The potential ways to use system visualizations via a virtual environment are endless. The next question is, how can one trust the visualizations one is seeing? But that's for another day...
What about the ease of which users would be able to interact with their infrastructure? No more manually grep'ing through log files and modifying systems via command line and shell scripts. It'd be much easier to visually see a comprehensive view of one's infrastructure and be able to make modifications with a few mouse clicks. Instead of interacting with complex systems by means of such complex methodology, we should be working to interact with them in more simplistic, intuitive ways.
Today, every systems engineer devises many system and network diagrams before deployment and implementation. But these forms of documentation are static. We need to begin implementing living visualizations that dynamically interact with our living systems.
DDoS’ing Second Life Sims to fend off business competitors
A sim, or simulation server, is a Second Life architecture component that “simulates” a 256x256 meter region in Second Life’s metaverse. Sim servers handle most of the critical processing power necessary to maintain perpetually consistent object and terrain height-map state. They utilize an involved physics engine, Havok, which performs visibility calculations on both objects and map terrain. Upon completion, the sim server processes the results and transmits them to the client via UDP.
Second Life real estate consumers essentially purchase their own sim server, or island, hosted in the Linden Labs’ cloud. As we know, many Second Life land owners develop upon their islands and operate their own virtual businesses. Many such virtual businesses have been successful and seen significant profit gains. All such virtual undertakings rely heavily on Linden Lab’s infrastructure and require their sim servers to be fully operational at all times.
If I am a business owner in Second Life I am most likely looking for opportunities to gain the upper hand on my competitors. I could perhaps spend tedious amounts of time conducting market research, perform user poling and reviews, hire outside consulting, etc. All of which are costly, time-consuming, extremely boring and still do not ensure the right business decisions will be made to overtake my competitors.
Why not instead outsource my dirty work, contract cyber criminals to leverage a massive botnet, and DDoS my competitor’s sim servers back to the Stone Age?? This will render them unusable and perhaps even take them offline. Instead of hours and hours of market research and business study I’ll simply wipe them off the map. After taking down my competitors and monopolizing the market, consumers will be forced to seek out my virtual goods and services. My business’s name will become omnipresent and ubiquitously recognized throughout Second Life thus giving me a significant market advantage over my competitors once their sim servers come back online. That’s the vision anyway.
The obvious question is what can be done to combat these DDoS attacks? Currently, Second Life land owners are at the mercy of Linden Labs. They rely on Linden Labs to maintain and operate their individual sims securely. This is essentially the primary security issue concerning cloud computing. Consumers rely on cloud providers to secure their infrastructure.
From a Linden Labs infrastructure perspective, it would be interesting to see sim locations in the infrastructure dynamically rotate and still maintain a perpetual virtual state. The cluster representative server, or space server, would essentially orchestrate the dynamic changes while the data servers in parallel, perform the necessary corresponding data processing. This type of dynamically orchestrated architecture would give the various sim servers ephemeral IP addresses and make them more difficult to target with DDoS attacks. This dynamic architecture is conceptually similar to the way in which attackers use DNS fast flux to obfuscate phishing and malware delivery sites.
DDoS attacks against sim servers in the virtual context can be used in countless ways to make money just as they can in today’s two-dimensional web. As virtual worlds and a three-dimensional Web become more relevant it will become imperative for world providers to account for DDoS attacks and build their infrastructures accordingly.
