Monday, April 9, 2012

Using the Cloud... To start your car?!

With the software-intensive automobile, updates to your car's operating system (you knew your ride had an OS, right?) is typically a "sneaker net" operation. Your dealer plugs a USB drive into the iPod port, and updates the code that controls the gasoline-air mixture of the fuel injection system, or some other mission-critical onboard process.

Mercedes now utilizes a wireless system (that normally carries entertainment and an OnStar-like safety network) to update its products remotely -- much like Software Update on your Mac or IPhone.

http://www.txchnologist.com/2012/new-york-auto-show-upgrading-auto-software-in-a-flash

So let's keep our eyes open for the first Merc hacking incident!


- Posted by Tom/Bluedog

Friday, April 6, 2012

Guest blogger says, "Try searching the web for a better deal on Content!"

Guest written by our friend Solomon Thompson
.
When you are looking for a television cable company it is really important to scour the internet for all the good deals you can find. You will see that there are a million sites out there talking about how they have the best deal or the cheapest connection fee or the most channels etc. I decided to go with directtv.com about a year ago and I have been really happy with the service and the extras that come along with it. I thought I would share that even though all these other companies may claim to be the best and the cheapest there is no way that they can compare to the whole package that I found with Direct TV. I have all the channels I could possibly watch as well as multiple DVR boxes for the different televisions in my home to record multiple shows at once. I also love the mobile feature where you can schedule or edit any recordings right from your mobile smart phone. Go to their site and check it out for yourself.

Thursday, April 5, 2012

Encryption followup

Not sure I completely agree that the author's perspective, that this particular approach to enciphering data will be the "big breakthrough" in cloud security, but the article is worth reading for two reasons, IMHO,

- A novel approach to a way to ensure security of data; this method seems to offer a compelling means.

- It illustrates why the use of patents to secure investment in a new technology is a double-edged sword.

By making the monopolistic use of a technology possible for inventors, the theory goes that inventors are motivated by the potential profits. On the other hand, useful inventions are denies by artificially maintaining high prices.

This particular approach utilizes homomorphic concatenation (concatenating two fragments of ciphertext, and can be found in RSA's approach as well as others. When considering cloud computing, "encrypting in the cloud" (on the server side) might not make the most sense. But because one buys computing resources on as-needed basis, it is very easy to increase the number of available servers when peak usage occurs, and reduce the number when not needed. While you can secure the channel to the cloud resource (via SSL), what do you do with the data on the persistent storage side?

As Craig Stuntz explains, what if it were possible for a user to upload their information encrypted under a public key? Then their data would be secure. This is possible today, but the server-side resource would be unable to act on the data. If, however, the encryption method used was also fully homomorphic, then the cloud-based web service could do all of the work without first decrypting the user’s information. The output of would still be encrypted under original public key. In fact, you'd be providing a valuable service without ever decrypting the end user's data.

Read more...

Thursday, March 29, 2012

Encryption remains a core technology of the Internet


With the use of Cloud services, we mustn't skip the all-important securing of sensitive data. Many web services and the apps build from them process sensitive information -- we have the need to securely store and retrieve that data. One easy way to accomplish this (at least when using Amazon's cloud services) is to use a client-side Java app that automatically encypts data when it is uploaded to the cloud. In the case of AWS, your data is stored encrypted in Amazon S3 in such a manner that no one can decrypt it without your private encryption key. The developer controls the private encryption keys used for the enciphering, and those keys are never exposed outside the client-side application. Of course, it is up to you to protect your encryption keys just like any other security credentials. The AWS client is a handy way to easily protect information residing on the cloud. Implemented properly, a developer may call the encryption/decrypt routine without other code having to be aware that the encryption and decryption is happening automatically in the client.

This approach is very different from ones based on historical models -- such as ones based on the operations of the infamous Enigma machines. The technology, patented in 1919, has been utilized for almost 100 years. On a typical Enigma machine, letters are scrambled by a set of rotatable cogs each with 26 contacts on either side. Each contact on one side is wired to a contact on the other side in some random fashion. Some models have 3 such rotating wheels, but later models in the war, have 4 wheels. This type was used exclusively on German U-Boats. Each time a key is pressed, the right most wheel is rotated by one step, resulting in a different mapping of the internal wires. As a result, each new letter is encoded differently.

Check out this fellow's work on a spreadsheet version of a well-known WWII encryption technology. This solution was used for many years after the war (and after it was compromised) by other parties. You can read more about the Enigma machine.

If you want to implement your own encryption approach based on the Enigma, this online course will get you started.

Friday, March 23, 2012

Did you get a disaster recovery plan for the New Year?

So we are approaching the end of the first quarter of 2012. How are your new years resolutions coming along? Still hitting the gym? Off the smokes? What about that disaster recovery plan your organization was lacking, when old Saint Nick came around?

Traditional disaster recovery planning usually involves a hot site with duplicates of all your IT and network infrastructure -- and there's the direct and indirect costs of staff relocation, logistics and more. When your business continuity plan calls to run as usual when disaster strikes the primary data center, a hot site is mandatory. But such planning brings challenges in terms of complexity and cost. And executing your plan involves a complete set of processes with all components being tested regularly. have you considered the cost of unplanned downtime? If downtime occurs, how much it will cost? How long will a recovery will take?

My advice: use what works, and borrow best practices from agile software development/ Come up with a prototype and put the plan in action, learn from it, and go back to to re-work the next iteration.

Spending a year studying what to do is foolhardy; attack the problem with a series of end-to-end sprints that allow your plan to evolve. You will know you've reach reached close to the end-state and built a better solution with each new iteration, which will require planning and execution. Like a software development sprint, deliver something every three months and involve all the stakeholders.


Your planning should cover moving the data you need to your recovery cloud, to ensure you have it available when you need it. Since we are talking technology here, make effective use of automation tools. Amazon's cloud provisioning, workload automation and process automation are good examples of the facilities you can tap today, so your organization can recover quickly, using tested and proven processes, with a clear audit trail and avoiding human error.


Inc. has a good article about this exact strategy... worth looking into. Any plan is better than no plan, and the cloud makes backups all the easier.