Have you ever wanted to know when the next paradigm shift will occur in computing? Will it be mobile computing or large servers? I think it has started happening. As I write this, the newest iteration of the Apple iPhone (3G S) hits the street. Think about the metrics here. We have reached a mass of users that can listen to music, get directions, play games, manage their servers and VNC into their desktop and home. We have embarked upon a mobile device that is nearly all things to most people, of course, within the AT&T coverage.
Today, this mobile device is about twice as fast and will be reveling in the new 3.0 apps. We shall see more and more industries embrace this technology as the days of multiple devices will get smaller.
With the U.S. Senate now getting involved with the Apple/AT&T partnership, this strikes a chord with not the partnership, but the ubiquitous nature of the iPhone. If there is a good product with solid technology, it will sell and eventually win our hearts and minds. In just over 2 years, the iPhone has won over Apple and non-Apple customers. Like it or not, look for more integration/value using the iPhone in our daily and business lives.
Archive for June, 2009
Mobile Computing: The Coming of Age
Monday, June 22nd, 2009Avoid Disseminating Harmful Information – Use Tivoli Storage Manager
Wednesday, June 17th, 2009“Protect accidental or intential release of backup/recovery tape data with data encryption used in IBM’s Tivoli Storage Manager.”
…The newspaper headline read, “U.S. National Corporation Freely Releases Customer Information on the Internet.” The article begins, “U.S. National Corporation [USNC] earlier today provided public access to confidential customer information including names, addresses, social security numbers, and credit card numbers. The customer information was apparently routed internally to personnel not authorized for viewing. In accordance with ‘full disclosure reporting,’ USNC has posted the information in a file on their website and made it available for download and viewing.”
Further down in article, the CEO is quoted as saying, “…when we discovered that our customers’ records were mishandled, the board of directors decided to release the information on the Internet so that there could be no question of our guilt.” The article goes on to explain how a company human relations manager received an e-mail with the offending file attached. The file, created by the company’s backup / recovery system, was supposed to be delivered to customer support personnel that handles customer complaints but was incorrectly addressed by the sender.
Although there have been several well publicized incidents of accidental “leaks” of customer information in the past several years, this is the first known intentional release of such information on the Internet.
Susan Blume, USCN’s Director of Internet Security, was vehemently opposed to the release of customer information. In a phone interview, she expressed “extreme concern for the well-being of our customers. …there are thousands of individuals with criminal intent that would love to get their hands on the kind of information that was posted on our web site.” She added, “The Board of Directors believes that no one is sinister enough to use the information for evil purposes. I know better.”
Outrageous Disclaimer
In a press release, USNC’s CEO, explained, “We have procedures in place that were not followed. The offending employees have been disciplined. [Still], for sake of full disclosure and transparency, acts performed by the company that may be detrimental to customers will result in a ‘full and transparent’ public report…”
According to the CEO, company policy requiring full disclosure of compromising incidents was added to the USNC’s by-laws after the United States government assumed partial company ownership in the 2009 bailout. “Despite potential harm to our reputation and potential identity theft of our customers, we believe that we’ve achieved our goal of total transparency. The customers freely provided their information to us. We disavow fault if harm comes to them as a result of their information being disclosed publicly.”
No Way!
Of course the article above is pure nonsense and the event never really happened. No right minded board of directors or CEO would intentionally allow the release of information for public access that criminals could use to cause harm. Every company should protect its proprietary information from external access with every means possible. A company’s reputation (and chances for survival) is at extreme risk after unintended dissemination of information.
Protect What’s Important to Avoid Criminal Acts Against Your Customers
With this in mind, why is the US Congress preparing to allow dissemination of documentation that will incite criminals to bring harm to US citizens?
Consider the actions taken earlier this month by at least one congressional committee to strip an amendment barring the release of supposed torture pictures of terrorist suspects. US Senators proposed an amendment to block the release of photos that may inflame anti-American sentiment with people that mean to do us harm.
The photos in question are, in our President words, “…not particularly sensational…but they do represent conduct that did not conform with the Army manual. That’s precisely why they were investigated… and where appropriate, sanctions have been applied.” The President added, “This is not a situation in which the Pentagon has concealed, or sought to justify inappropriate action…” Like the fictional leak of information in the story above, it should be a “no-brainer” to approve legislation to block the release of the damaging information.
Regardless, the ACLU sued for the release of the photos citing the Freedom of Information Act.
In May, our President challenged a court decision (in favor of the ACLU) saying, “The most direct consequence of releasing [the photos], I believe, would be to further inflame anti-American opinion and to put our troops in greater danger.” The President said that he would seek to block the court-ordered release of the photos citing recommendations from US generals. The generals expressed concern that the photos could be used by terrorist organizations for recruitment purposes and to incite increased anger against the US, resulting in violence towards American troops and citizens.
Still, Speaker of the House reports that the amendment proposed by the Senators is likely to be stripped from legislation in committee.
If the photos are released, brave US soldiers serving in the Middle East and US citizens world-wide would be likely targets of terrorist attacks from radicals intending to do harm to the United States. It is logical to assume that terrorist activity against America will increase if the photos are made public.
As in the fictitious story about USNC above, public dissemination of damaging information is illogical. No right minded company would ever intentionally release information that would cause harm to its customers. Likewise, no honorable government should ever provide information that aids enemies sworn to harm to its citizens. Companies and governments alike should invest in technology and promote laws / policies designed to prevent accidental, malicious, or intentional dissemination of proprietary / classified information.
The US Congress should do the honorable thing and block the release of the photos. If Congress does not do their job and protect US troops and citizens, then the President should sign an executive order preventing the release of photos. It is the job of the President and Congress to prevent harm to the people and country they are sworn to protect.
Technical footnote: If the backup/recovery tape that was released by USNC had been created by IBM’s Tivoli Storage Manager, the data would have been encrypted. Without security keys, the customer data in the file (even though it was posted on the Internet) would have been nearly impossible to read.
Cloud Computing?
Monday, June 15th, 2009What is it? You probably have heard all the advertising and banting around of the term, but what value is it to you? Why should you care? Well, for one, cloud computing is not an “epiphany”. It is something the industry has been trying to deliver in a cost effective way for years.
It is this – delivering everything you need as an end user (infrastructure, platform and software) as a web service. That is it in a nutshell.
But here’s the tricky part – how to know what you need when you need it? There is the wide open field that companies are racing to fill.
The “cloud” in this case, is the Internet as we know it. The users are you and me, and we are delivered the services we need over the “cloud” on a per use fee basis, or a subscription. We aren’t required to invest in the infrastructure (hardware and software) to deliver these services, rather we “pay as we go”, kind of like how utilities are delivered. By utilizing this type of delivery, the companies who are delivering can get greater utilization out of their hardware and software, and spread the costs of the services across more recipients.
In the old days, we considered this type of delivery and labeled it “time sharing”. Telephone companies did it early on with Virtual Private Networks. In a recent article by Nicholas Carr, he likened this paradigm shift in the IT evolution as similar to the displacement of the electrical generators by the electric grid in the early 20th century. But, I digress.
Not only is this type of service more effective, it can also provide side effects like the reduction of CO2 by reducing energy required to deliver the service. If more companies utilize cloud computing as a service approach and fewer companies are at the hub of the cloud services, we potentially get greater service levels, and are happier people.
Now isn’t that what we want…to be happy? Go figure.
‘Cause I could…
Thursday, June 11th, 2009It has been a common practice for a lot of systems administrators to take systems in the Data Center for a spin; some are inspired by their buddy Chuck… you know Chuck, he is the outgoing guy from the local users’ group… and others by their own thirst for knowledge. They click around in the GUIs, look to see first hand what the command they heard about actually does, bang at the keyboard while exploring the CLI, and mull over what features they think they need to implement in their environment.
I see the hunger to expand their understanding of the systems as a very valuable trait – a trait I personally wish was more dominant in our world. I praise administrators who actually take the time to read the CLI guide, discover that they can create server farms full of 4-way SMP VMs in their new VMware Cluster, and see the possible benefits of implementing IVR in their Cisco SAN environment. Knowing the abilities of the systems is a wonderful thing and can make someone a more treasured resource; however, it must be said that actually implementing something because you could, and not because you should, can be the source of some major headaches for yourself and others.
I’d be the first to tell you that most of my headaches are brought on because someone did something because they could – the system had the ability to do it, they researched how it could be done, and they pulled the trigger. Some of these features worked well for the first six months until they needed to expand the environment, and now they needed to take an outage to address the issue or pay for workaround to their implementation of that nifty new feature.
“ ’cause I could ” is possibly the scariest response to many questions I ask about why and how something has been implemented. Please, do us all a favor the next time you, or your buddy Chuck, plan to pull the trigger on some feature you just learned about—slow down and ask yourself a few questions first…Did you research how this feature impacts the other projects and systems currently in the works? Is this actually needed, and will it really do what you think it will? Did you pick the brain of someone with more knowledge about that particular technology and ask about the gotchas? A few more questions may just save a trip to Rite Aid for another bottle of Excedrin Migraine.


