When it comes to disasters, people and businesses tend to think big, really big. Take for example Superstorm Sandy that hit the eastern US earlier in November. It can be pretty much guaranteed that a whole string of businesses will be preparing diligently for the next big storm. While this is important, smaller issues that happen at a higher frequency will be pushed to the side. One common issue revolves around passwords, and who manages them.
Search for Terry Childs online and you'll find a number of articles about a former Network Administrator for the city of San Francisco who is currently in jail for supposedly doing his job. His job, as a network administrator, was to manage the city's network. When he was asked by his boss for the passwords to critical parts of the network, he refused on the grounds that the request went against the established network policy.
Issues like this: One employee or vendor in control of vital passwords, can pose a big problem to companies, especially during times of disaster. Imagine if you work with an administrator who is based in New York, and they lost power during Sandy. What could you do if your network crashed, or you needed access to your system and someone else has all the passwords?
The most crucial factor is you shouldn't trust one person or organization with passwords to vital systems. We don't mean personal passwords to systems, we mean passwords to vital systems, like servers or Internet connections. If one person has the passwords, there's just too much risk. If they are disgruntled, they have the power to do some serious damage, and if they are injured or are no longer alive, you'll face untold amounts in lost profit, and fees in recovering passwords and information.