Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

6/5/2009
11:04 AM
Keith Ferrell
Keith Ferrell
Commentary
50%
50%

Disaster Recovery: Location, Location, Location

A comment from a reader offers a reminder that effective disaster recovery planning -- and successful DR in the event of disaster -- requires more than just IT and personnel planning. You have to know where those resources are going to be able to work.

A comment from a reader offers a reminder that effective disaster recovery planning -- and successful DR in the event of disaster -- requires more than just IT and personnel planning. You have to know where those resources are going to be able to work.The comment, in reference to 3 Disaster Recovery Tips (Or Risks!) You May Have Overlooked, is worth repeating here:

One issue that is easily overlooked is the location of your key staff that will be needed on your recovery team. I am aware of a key financial services company that had most of it's key staff in one of two buildings, both in a target rich area of a major city. One building was over a commercial parking lot and the other had a circular driveway in front. Just getting to the backup site, if something happened downtown, would be a challenge.

While this company did build a new data center and office building a safe distance from downtown, I suspect that things are not better today due to staff reductions, among other things.

Lesson learned: to the extent possible, diversify the location of your key staff. If that's not possible, encourage telecommuting so that not all the key people are at work on any given day. As mentioned previously, you should promote and practice telecommuting anyway.

Good points all, and another reminder of the need to consider all the alternatives, complications and contingencies that may arise if you're hit with a disaster, whether a large regional catastrophe or a more localized (perhaps as local as your facility alone) interruption of your ability to do business.

When planning for disaster recovery, how much consideration have you given to the location where the recovery efforts will take place?

And do you have backup (as it were) locations in mind should your primary recovery facilities be rendered unavailable by the disaster?

These, by the way, were some of the DR topics discussed in out recent bMighty bSecure SMB Security On A Budget online event, now available on-demand.

Check it out here:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-22861
PUBLISHED: 2021-03-03
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted ...
CVE-2021-22862
PUBLISHED: 2021-03-03
An improper access control vulnerability was identified in GitHub Enterprise Server that allowed an authenticated user with the ability to fork a repository to disclose Actions secrets for the parent repository of the fork. This vulnerability existed due to a flaw that allowed the base reference of ...
CVE-2021-22863
PUBLISHED: 2021-03-03
An improper access control vulnerability was identified in the GitHub Enterprise Server GraphQL API that allowed authenticated users of the instance to modify the maintainer collaboration permission of a pull request without proper authorization. By exploiting this vulnerability, an attacker would b...
CVE-2020-10519
PUBLISHED: 2021-03-03
A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. User-controlled configuration of the underlying parsers used by GitHub Pages were not sufficiently restricted and made it possible to execute commands on the Gi...
CVE-2021-21353
PUBLISHED: 2021-03-03
Pug is an npm package which is a high-performance template engine. In pug before version 3.0.1, if a remote attacker was able to control the `pretty` option of the pug compiler, e.g. if you spread a user provided object such as the query parameters of a request into the pug template inputs, it was p...