Make NIMS/ICS more security focused
NIMS/ICS lacks a security component. With incident management being both natural disasters and man-made disasters (e.g. terrorist attacks) their seems to be a lack of terminology or wording within NIMS that focuses on preparation for man-made disasters. It is important to realize incident management on a natural disaster and terrorist disaster while similiar will have other components that need to be addressed within ...more »
NIMS/ICS lacks a security component. With incident management being both natural disasters and man-made disasters (e.g. terrorist attacks) their seems to be a lack of terminology or wording within NIMS that focuses on preparation for man-made disasters. It is important to realize incident management on a natural disaster and terrorist disaster while similiar will have other components that need to be addressed within each
For example, under Component II of NIMS, Communications and Information Management, it does mention breifly the need to use encryption or tactical language, but there is clearly no mention under the Component IV, Command and Management, which is the ICS section of NIMS stating the need to never use anything other than "plain english and common terminology". This is a major mistake to leave out the need for encrypted or tactical language under ICS. Training future incident managers to train their staffs to only use common terminology makes us vulnerable during man-made disasters. There is a time and place to use tactical or encrypted language as terrorists have been known to stage secondary attacks on emergency responders. The use tatical language during ICS will help emergency responders better protect themselves. A sectiion under Component IV of NIMS under the ICS section should note the use of tactical language under certain incidents.
« less full details »