The "RISKY BUSINESS" Blog

During a recent business trip to Phoenix I had an interesting interaction with the Transportation Security Administration (TSA) (www.tsa.gov/). The lines were unusually slow going through the security checkpoint. When we got to the checkpoint the cause was easily deduced – a bunch of TSA agents were trying to figure out how to turn back on one of the x-ray machines that another TSA person had turned off while troubleshooting a problem. One observation of concern was the obvious lack of training/knowledge of the system that the vast majority of the folks had. From a security line over I could see they were not turning up the main power switch. Another interesting observation was that on boot up the familiar Windows XP emblem waived on the screen.

As a security professional I must confess to being a bit disappointed that such a critical piece of air security is running on a desktop OS, especially, one with a dubious record for security. One of the TSA agents overheard my OS derogatory comment to my travelling companion and laughed, ‘I know XP … I couldn’t believe it either’. It’s what happens when you buy from the lowest bidder”.

On the plane ride home I pondered his comment. I think he was half right. The problem isn’t necessarily that they bought from the lowest bidder – more likely it is that they failed to perform an appropriate level of requirements definition. A simple requirement (inserted into the RFP) such as “The application needs to run on a server level Operating System (or a 64 bit Operating System) for the highest possible levels of availability (or performance) would likely have been sufficient to preclude ending up with an XP based system.

Does your team have any purchases planned where insufficient requirements definition may result in the acquisition of a sub-optimal solution? One where Information Assurance and Information Security are critical. Based on 10 years of auditing experience I’m betting the answer is yes. :>)