A "Corporate IS Gotcha" is an avoidable disaster waiting for the right circumstances to happen. It's a problem whose solution before it happens costs far less than the consequences of letting it happen. It's a situation where an ounce of prevention now saves a pound of cure later.

Traditionally, such 'defensive' network design was entirely the province of large organizations. Today, though, an increasing reliance on computers combined with more sophisticated systems means that just about any organization needs to analyze the risks and take action now -- before the disaster happens.

The key to analyzing these risks stems from standard risk management practices. How much will it cost to prevent; how much would it cost if it happened; how likely is it to happen? Combining those factors gives a fairly straightforward numerical answer. However, there are some intangibles to consider.

Any business manager would agree that, all other things being equal, smooth operations are better than disrupted operations. Likewise, predictability is preferable to risk. Finally, technical experts agree that correcting a problem when a system is smaller is easier and less costly than fixing the system after it has grown in size and complexity. All of these are compelling arguments for correcting problems sooner rather than later.

Some of the risks presented here may not apply to your organization. Some of them may already have been corrected. Some of the disasters might not occur even if left alone. However, just as most of us wouldn't continue to drive a car we knew had bad brakes, we should also make sure that our computing infrastructure receives the needed maintenance to keep it healthy and productive.