| Recurring |
one_organization |
(a) The software failure incident having happened again at one_organization:
The article mentions that in 2017, a cyber attack disrupted services at Kiev’s Boryspil International airport, indicating a similar incident had happened before at another airport [75805].
(b) The software failure incident having happened again at multiple_organization:
There is no specific mention in the provided article about the software failure incident happening again at multiple organizations. |
| Phase (Design/Operation) |
design |
(a) The software failure incident at Bristol Airport was attributed to a cyber attack, indicating a failure due to contributing factors introduced by system development or system updates. The attack caused a three-day technical meltdown, leading to the information screens being out of service and passengers having to rely on whiteboards for flight details [75805].
(b) The operation of the system was also affected by the software failure incident. Passengers were instructed to arrive early for check-in due to ongoing technical problems, and staff had to manually write flight details on whiteboards and paper to keep passengers informed about flight information [75805]. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident at Bristol Airport was caused by a cyber attack, indicating that the contributing factor originated from within the system itself. The attack led to the information screens being out of service, requiring staff to resort to manual methods like whiteboards and paper for displaying flight details [75805].
(b) outside_system: The incident was not attributed to factors originating from outside the system, such as environmental conditions or external events. Instead, the primary cause was identified as a cyber attack, indicating an internal system vulnerability that was exploited by external malicious actors [75805]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident at Bristol Airport was caused by a cyber attack, which is a non-human action [75805]. The cyber attack led to a three-day technical meltdown, resulting in the airport's information screens being out of service and passengers having to rely on whiteboards and paper for flight details. The attack forced several systems offline, including the application providing flight information, indicating a failure introduced by non-human actions. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident at Bristol Airport was caused by a cyber attack, indicating a hardware-related failure as the contributing factor originated in external hardware (the attackers' systems) [75805].
(b) The software failure incident at Bristol Airport was directly related to a cyber attack, which can be considered a software-related failure as the attack targeted the airport's software systems [75805]. |
| Objective (Malicious/Non-malicious) |
malicious |
(a) The software failure incident at Bristol Airport was malicious in nature, as it was caused by a cyber attack. The airport confirmed that the three-day technical meltdown, which resulted in information screens being out of service and passengers having to rely on whiteboards for flight details, was due to a cyber attack [75805]. The attack led to several systems being taken offline in an effort to contain the incident, indicating that the failure was intentional and aimed at disrupting the airport's operations. Additionally, the airport spokesperson mentioned that established contingency plans were implemented to keep passengers informed about flight information, highlighting the deliberate nature of the attack. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident at Bristol Airport was caused by a cyber attack, indicating poor decisions made by the attackers to target the airport's systems [75805]. The decision to launch a cyber attack on the airport's systems led to the disruption of services and the need to take systems offline to contain the attack, resulting in a three-day technical meltdown. This deliberate action by the attackers highlights the poor decision to target critical infrastructure like an airport, causing inconvenience to passengers and disrupting operations. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident at Bristol Airport was caused by a cyber attack, indicating a security breach that exploited vulnerabilities in the airport's systems [75805].
(b) The incident resulted in the airport's information screens being out of service, leading to passengers having to rely on whiteboards and paper for departure information. This accidental disruption in service caused frustration among passengers and required staff to manually write flight details to keep passengers informed [75805]. |
| Duration |
temporary |
(a) The software failure incident at Bristol Airport was temporary. The incident lasted for three days, with the information screens being out of service on both Friday and Saturday [75805]. The airport took several systems offline on Friday to contain the cyber attack, and some screens were restored early on the following days, although complete coverage was yet to be restored. Flight operations remained unaffected during the incident, indicating that the failure was temporary and not permanent. |
| Behaviour |
crash, omission, other |
(a) crash: The software failure incident at Bristol Airport resulted in a crash as several systems were taken offline on Friday in a bid to contain the cyber attack, including the application which provides details about flights. This led to the airport's information screens being out of service for three days, forcing passengers to rely on whiteboards and paper for departure information [75805].
(b) omission: The software failure incident also involved omission as the airport's information screens were out of service on both Friday and Saturday, leading to the system omitting to perform its intended function of displaying flight details to passengers [75805].
(c) timing: The timing of the software failure incident was affected as passengers were told to arrive early to allow plenty of time for check-in due to ongoing technical problems with the airport's systems [75805].
(d) value: The software failure incident did not specifically involve a failure due to the system performing its intended functions incorrectly.
(e) byzantine: The software failure incident did not exhibit behavior indicative of a byzantine failure.
(f) other: The other behavior observed in the software failure incident was the use of manual methods such as staff writing flight details on whiteboards and paper to provide information to passengers, which was not the typical functioning of the system [75805]. |