recommended reading

Review finds information-sharing marred response to Fort Hood attack

Though intelligence agencies intercepted e-mails between Army Maj. Nidal Hasan and a radical Muslim cleric a year before he allegedly went on a violent rampage and killed 13 people at Fort Hood, Texas, in November 2009, lack of clear policy and procedures impeded sharing of such threat information with the Army, the service said in its final review of the deadly incident released on Tuesday.

The FBI also reportedly learned that Hasan had wired money to sources in Pakistan months before the shooting, but again this information did not make its way to the Army.

Foreign intelligence information is shared by the FBI through multiagency federal, state and local Joint Terrorism Task Forces, but prior to the Fort Hood attacks Defense Department participation in these task forces was inadequate, the Army said in its report. The Army now plans to station 26 criminal investigators with these task forces.

In April, Defense Secretary Robert Gates said the Pentagon will use the FBI's e-Guardian threat reporting system to access multiagency terrorist threat information. In its new report, the Army said it planned to merge information from e-Guardian with classified intelligence information to provide even better insight into potential terrorist threats.

The Army said it has also established a Threat Awareness and Reporting Program , which requires troops to report behavior by fellow soldiers viewed as a potential sign of terrorist or extremist sympathies.

This program is supported online by the new iSalute project, which allows anyone with an Army Knowledge Online account to automatically report suspicious behavior or potential threats.

On releasing the report, Army Chief of Staff George Casey said: "While we know we can never eliminate every potential threat, we've learned from the events at Fort Hood. We have made significant progress, particularly in threat awareness and reporting, coordination in intelligence sharing, and training for our security forces, but our work is not done."

The Fort Hood incident also pushed the Army to improve its background checks, and the service said it plans to fully deploy its Army Investigative Enterprise Solution to automate the process. The Army has budgeted $95 million for this system in fiscal 2011 and $76.2 million in 2012.

In addition, the Fort Hood incident is thought to have exposed the Army's inability to manage its response to a crisis at one of its installations because the service does not use the enhanced 911 phone system to coordinate with police and ambulance departments off base.

An enhanced 911 system, the Army said in its report, requires a well-managed telecommunications infrastructure database capable of providing automatic number identification and automatic location identification, using GPS technology and geographical information systems.

The Army said it will start deploying enhanced 911 systems at its bases in 2012, having budgeted $37.6 million for it in 2012 and 2013.

The Army also plans to deploy mass warning systems at its bases to ensure rapid notification of personnel in case of a crisis. These systems include outdoor "Giant Voice" loudspeaker systems, building speakers, and automated phone and computer alert systems. The Army has budgeted $105.8 million for mass warning systems in 2012 and $117.6 million in 2013.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.