IT securityFEMA's still struggles with IT security issues

Published 5 August 2008

DHS’s IG reports that “These issues collectively limit FEMA’s ability to ensure that critical financial and operational data is maintained in a manner to ensure confidentiality, integrity and availability”

The Federal Emergency Management Agency (FEMA) is still struggling to secure its information technology systems with 31 weaknesses carried over from previous years and 13 new weaknesses identified in fiscal 2007, according to a new audit report released by DHS Inspector General Richard Skinner. FCW.com’s Alice Lipowicz reports that FEMA corrected ten weaknesses last year, and it developed new policies, processes, and procedures to comply with cybersecurity guidelines, states the report on FEMA’s IT issues related to financial controls, written by the KPMG LLP auditing firm. Overall, FEMA continues to suffer from weak controls on employee and contractor passwords, shortcomings in application service development and service continuity, and a weakness in its systemwide documentation, among other problems, the report states. “These issues collectively limit FEMA’s ability to ensure that critical financial and operational data is maintained in a manner to ensure confidentiality, integrity and availability,” the report states. “Consequently, these weaknesses negatively impacted the internal controls over FEMA financial reporting and its operation,” KPMG said. FEMA managers generally agreed with the findings.

Among the problems identified in the report:

  • There are 770 former FEMA and contractor employees with some level of active password privileges
  • National Flood Insurance Program workstation deactivations are not programmed in compliance with security guidelines
  • Changes to mainframe applications were documented only about half the time
  • Excessive access privileges are in place on several applications
  • FEMA’s Continuity of Operations plan has not been updated to reflect concerns raised by the IT Service Division Continuity of Operations Plan