Commentary

Make Contingency Plans For Your Enterprise

Scientists estimate the chances of a catastrophic earthquake jolting Southern California in the next 30 years could be nearly 70%. An AT&T study asked L.A.'s IT execs if they were prepared for such an eventuality. Is your enterprise?

Scientists estimate the chances of a catastrophic earthquake jolting Southern California in the next 30 years could be nearly 70%. An AT&T study asked L.A.'s IT execs if they were prepared for such an eventuality. Is your enterprise?While earth-shattering events such as the S.F. Bay area earthquake of '89 or 9/11 are indeed rare, they do happen from time to time. Surprisingly, 30% of the execs surveyed by AT&T agreed that contingency planning is important, but have no plan in place to actually provide that protection.

Enterprises that are highly mobile or spread over large geographic regions may face a somewhat lower risk than those that use a single center for operations, but that doesn't mean they can't lose everything. De-centralizing information, or having multiple storage sites, is a critical safety net to employ.


More Mobility Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

According to the survey, cybersecurity is a top worry, with 26% of respondents saying the thought of worms or viruses keeps them awake at night. Natural disasters ranked second in the sleep-deprivation category with 21%, followed by security breaches (18%), and man-made disasters (15%).

If there's one lesson learned in the wake of 9/11, it's that centralized business operations create an inherent risk in the eventuality that those locations are destroyed by acts of god or madmen. Finance firms in Manhattan have moved many of their central data and information resources away from Wall Street, with some pushing business-critical data to safer locations across the Hudson River in Jersey City.

If these companies already have taken the steps to protect their information, shouldn't you protect yours?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links