BlackBerry outage underscores need for a backup plan

BlackBerry outage underscores need for a backup plan
BlackBerry outage underscores need for a backup plan

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

Content-Transfer-Encoding: QUOTED-PRINTABLE

By Patrick Marshall
GCN Staff
04/30/2007 issue

You don=E2=80=99t miss the water until your well runs dry. And when millions of 
BlackBerrys lost their e-mail capability April 17, it suddenly became 
clear how dependent many people in federal agencies and departments have 
become on the devices.

=E2=80=9CCertainly, the senior folks in the agency view them essentially as an 
extension of their bodies,=E2=80=9D Corey Booth, chief information officer of 
the Securities and Exchange Commission, told Government Computer News. 
And when the e-mail service went out, Booth said dryly, =E2=80=9Cit was 
certainly a source of complaint.=E2=80=9D

At first, Research in Motion offered few details of why the service was 
down. Only two days later did the company explain the outage, chalking 
it up to insufficient testing of new caching software in its network 
operations center (NOC) in Canada.

One factor that made the outage more widespread than it otherwise might 
have been is the BlackBerry system=E2=80=99s highly centralized message routing. 
All e-mails are routed though one of two NOCs =E2=80=94 one in Canada serving 
the Western Hemisphere and one in England serving Europe, Africa and the 
Middle East.

Booth said agencies and departments would be well-advised to plan on 
future failures.

=E2=80=9CThe thing that everyone has to understand is that there are very few 
forms of technology, particularly of communications technology, that are 
foolproof,=E2=80=9D Booth said. =E2=80=9CYou can have a RIM-related failure, you can 
have a telephone company-related failure, you can have a failure within 
our e-mail system, you can have a failure at any of the gateways between 
those various systems. There are a lot of places where problems can 

That=E2=80=99s why it=E2=80=99s critical for staff to have a Plan B.

=E2=80=9CPlan B can be pretty simple,=E2=80=9D Booth said. =E2=80=9CIt can be just carrying 
around peoples=E2=80=99 cell phone numbers. Plan B can be knowing how to log in 
to your e-mail from home. There are lots of things that people can do 
that are in the category of somewhat inconvenient but workable 

Some analysts have also voiced concerns about the security and 
reliability of a system that depends on such a centralized architecture. 
And, particularly for federal agencies and departments, there may be 
concerns about routing e-mails through NOCs that reside in a foreign 

=E2=80=9CIf the software vendor can be forced to cooperate with government 
agencies, the possibility exists that the wireless e-mail software could 
include hidden eavesdropping capabilities in accordance with governments 
or intelligence agencies for various purposes,=E2=80=9D a recent Gartner report 
states. For that reason, some governments =E2=80=94 including France, Germany, 
Great Britain and the Netherlands =E2=80=94 have opted not to rely on such 

However, Booth said, not all federal agencies need to be concerned. =E2=80=9CI=E2=80=99m 
not arrogant enough to believe that our business [at SEC] is so 
mission-critical that we would be unable to perform our mission without 
having two NOCs owned by RIM,=E2=80=9D he said. On the other hand, =E2=80=9Cif we were, 
say, a first-response agency of some kind =E2=80=94 like a FEMA or a DOD =E2=80=94 I 
might have some concern.=E2=80=9D

RIM=E2=80=99s response to the outage is not likely to put concerned minds at 
ease. Apart from its brief statement citing the software glitch as the 
culprit, the company has been quiet on the issue. A week after the 
incident, no mention of the outage or its cause had been posted on the 
company=E2=80=99s Web site nor had RIM responded to a request for an interview.

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Subscribe to InfoSec News 

Site design & layout copyright © 1986-2015 CodeGods