Deutsche Bank extends continuity plan to include avian flu scenario


Deutsche Bank extends continuity plan to include avian flu scenario

Deutsche Bank has conducted an exercise to assess the impact of a potential avian flu pandemic on its business during a continuity planning exercise in Hong Kong.

Last month the bank assessed the impact of two potential scenarios on business operations. The first was designed to simulate the disease breaking out slowly, and the second assessed a sudden break-out in several locations simultaneously.

The exercise, the latest in a series of simulations designed to test the bank's response to incidents, aimed to give an insight into the impact of an avian flu outbreak on its operations.

Scenario-based exercises help the bank to "see around corners" by identifying risks that might not otherwise be obvious, said Victor Meyer, Deutsche Bank's business continuity manager.

Last year the bank carried out an exercise involving a simulated attack on its networks from insiders and external hackers.

"It validated our approach to IT security. No system is foolproof and it is very difficult to deal with the insider. We have to assume our systems will be compromised at some point. At this point, how they are escalated is critical," said Meyer.

In March last year, Deutsche Bank worked with the Corporation of London, Scotland Yard, the City of London police and regulators to simulate the impact of a bomb attack on the London Underground during rush hour.

The exercise allowed the firm to be better prepared for the 7 July bombings, said Meyer.

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

This was first published in April 2006


COMMENTS powered by Disqus  //  Commenting policy