Chapter summary
A security incident is anything that causes harm to staff or associated people, or loss of or damage to assets. Recording and tracking security incident data, as well as near-misses and threats, can inform decision-making across an entire organisation, within and outside security functions, and organisations should have procedures for reporting, analysing, sharing and using incident data internally.
Incident reporting supports staff and operational security in four main ways:
- Incident reporting and immediate response. To alert relevant teams so that they are aware and, if necessary, can provide help to anyone affected during an incident. Other humanitarian actors operating in the area can also be alerted, to enhance the security of the wider community.
- Incident analysis and lessons learned. To analyse the incident and implement lessons to prevent similar incidents from occurring in the future, and respond more effectively if they do.
- Context analysis. Tracking incidents and analysing trends and patterns informs context analyses and security risk assessments. Analysing aggregated incident data from within and outside the organisation assists decision-making and indicates if procedures need to be adapted.
- Informed strategic decision-making and policies. To enable the sharing of security incident information internally within an organisation to inform actions and decisions and improve ways of working.
Comparing incident data with that of peers in the same locations can allow for a more objective incident pattern analysis and help to determine trends if the data are analysed over time. External incident data can be accessed through interagency security forums and from open-source databases (see box below for examples).