China
Africa
Explore chapters and articles related to this topic
ISO Standards
Published in Boris Mutafelija, Harvey Stromberg, ® v1.2 and ISO Standards, 2008
Boris Mutafelija, Harvey Stromberg
Through the Incident Management process, incidents are reported, collected, identified, classified as to their severity, and tracked to closure. The priority of addressing the incident is usually established by service supplier management and agreed to by the customer. It is based, for example, on the incident’s business impact, risk of the loss of service, or the need for the continuation of operations. Because incidents cannot always be immediately resolved, the Incident Management process should take into account the possibility of operation with degraded service and provision of workarounds until full service is restored.
School Emergency Response Plan Template
Published in Michael L. Madigan, Handbook of Emergency Management Concepts, 2017
Communication is a critical part of incident management. This section outlines (add School/District name) communications plan and supports its mission to provide clear, effective internal and external communication between the school, staff, students, parents, responders, and media. (Add location of communication plan, policy, and procedures.)
Explainable AI for Security of Human-Interactive Robots
Published in International Journal of Human–Computer Interaction, 2022
Antonio Roque, Suresh K. Damodaran
Classic incident management has several steps: preparation, identification, containment, eradication, recovery, post-incident activity (Cichonski et al., 2012). We outline explananda that may be used in each of these steps, below. Preparation: prior to an attack, explanations for known attack effects can be pre-built for immediate use when needed for use by robot defender.Identification: control-loop based characterization, leading to identification of aspects the attack, can be explained to robot defender.Containment, Eradication and Recovery: defensive actions can be explained to the robot operator. Also, a robot defender can verify remedial actions based on the attack identification are going as planned. For example, if there is a false data injection to user interface attack (see Figure 8), the defensive actions such as the resetting the Sensor (Process), or deployment of alternate sensors can be verified through explanations.Post-incident activity: an attack replay capability associated with explanations can help to develop new explanations when none existed before.