Recurring |
one_organization, multiple_organization |
(a) The software failure incident having happened again at one_organization:
The article mentions that the attack on Vodafone Portugal came a month after the websites of one of Portugal's biggest newspapers and a major broadcaster were hacked, and both media organizations remain unable to access their websites. This indicates that Vodafone Portugal experienced a similar incident to other organizations in Portugal [124558]. |
Phase (Design/Operation) |
design, operation |
(a) The software failure incident at Vodafone Portugal was caused by a "deliberate and malicious" cyber attack, indicating a failure due to contributing factors introduced during the system development or system updates [124558].
(b) The disruption in services experienced by Vodafone Portugal's customers, where they were unable to make calls or access the internet, could be attributed to a failure due to contributing factors introduced by the operation or misuse of the system [124558]. |
Boundary (Internal/External) |
within_system |
(a) The software failure incident reported in Article 124558 was within_system. Vodafone Portugal stated that the disruption in services was caused by a "deliberate and malicious" cyber attack originating from within the system itself. The company assured customers that their personal data had not been compromised, indicating that the failure was contained within the system [124558]. |
Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident at Vodafone Portugal was attributed to a "deliberate and malicious" cyber attack, indicating a non-human action as the contributing factor [124558]. |
Dimension (Hardware/Software) |
software |
(a) The software failure incident reported in Article 124558 was due to a "deliberate and malicious" cyber attack on Vodafone's Portuguese unit, causing disruption to its services. This indicates that the contributing factor for the failure originated from an external source (hacker attack) rather than internal hardware issues [124558]. |
Objective (Malicious/Non-malicious) |
malicious |
(a) The software failure incident at Vodafone Portugal was malicious in nature. The article mentions that the disruption in services was caused by a "deliberate and malicious" cyber attack [124558]. The attack was aimed at causing harm to the system and disrupting the services provided by Vodafone Portugal. |
Intent (Poor/Accidental Decisions) |
unknown |
(a) The software failure incident at Vodafone Portugal was caused by a deliberate and malicious cyber attack, indicating poor decisions made by the hackers to disrupt the services [124558]. |
Capability (Incompetence/Accidental) |
unknown |
(a) The software failure incident reported in Article 124558 was due to a deliberate and malicious cyber attack on Vodafone's Portuguese unit. The attack caused technical problems, disrupting services for thousands of customers who were unable to make calls or access the internet. Vodafone Portugal stated that the incident was a result of a "deliberate and malicious" cyber attack, indicating that the failure was not accidental but rather a targeted attack by external actors [124558]. |
Duration |
temporary |
The software failure incident reported in Article 124558 was temporary. Vodafone's Portuguese unit experienced a disruption in its services due to a hacker attack, leading to technical problems that affected thousands of customers. However, the company assured that customer data had not been compromised, and they were working on restoring normal services gradually. This indicates that the failure was temporary and not permanent [124558]. |
Behaviour |
crash, other |
(a) crash: The software failure incident in Article 124558 can be categorized as a crash. Vodafone's Portuguese unit experienced a disruption in its services due to a hacker attack, leading to technical problems that rendered thousands of customers unable to make calls or access the internet on their devices [124558].
(b) omission: There is no specific mention of the software failure incident being caused by the system omitting to perform its intended functions at an instance(s) in the provided article [124558].
(c) timing: The software failure incident in the article is not attributed to the system performing its intended functions correctly but too late or too early [124558].
(d) value: The incident did not result from the system performing its intended functions incorrectly [124558].
(e) byzantine: The software failure incident does not involve the system behaving erroneously with inconsistent responses and interactions [124558].
(f) other: The behavior of the software failure incident in the article can be described as a deliberate and malicious cyber attack that disrupted the services, leading to a loss of functionality for customers [124558]. |