| Recurring |
unknown |
The articles do not provide information about the software failure incident happening again at either the same organization (one_organization) or at multiple organizations (multiple_organization). |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident in the article was primarily due to a design-related factor. Arran Brewery fell victim to a ransomware attack after an email attachment containing a virus was opened, leading to the locking out of their computer system and the demand for ransom to restore it. The attack exploited a security hole in vulnerable software or tricked someone into installing it, highlighting a design flaw or vulnerability in the system [75823].
(b) The software failure incident also involved an operation-related factor. The attack was initiated when the attackers posted a fake job vacancy on the brewery's website, leading to multiple emails with infected CV attachments being opened by the staff, which triggered the virus. This aspect of the incident relates to the operation or misuse of the system, as the staff unknowingly interacted with the malicious content, contributing to the system's compromise [75823]. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident at Arran Brewery was caused by a ransomware attack that originated from within the system. The attack occurred after an employee unknowingly opened an email attachment containing a virus, leading to the encryption of the brewery's computer system and a demand for ransom to restore access [75823]. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident at Arran Brewery was due to non-human actions, specifically a ransomware attack. The brewery was locked out of its computer system after opening an email attachment containing a virus, which then demanded a ransom to restore the system [Article 75823].
(b) Human actions also played a role in the software failure incident. The attack was initiated by tricking someone into opening the malicious email attachment. Additionally, the attackers posted a fake job vacancy on the brewery's website, leading to the receipt of infected CVs that further spread the virus within the system [Article 75823]. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident occurring due to hardware:
- The incident at Arran Brewery was a ransomware attack where the company was locked out of its computer system after opening an email attachment containing a virus [Article 75823].
- The ransomware attack exploited a security hole in vulnerable software or tricked someone into installing it, leading to the hardware failure [Article 75823].
(b) The software failure incident occurring due to software:
- The ransomware attack that hit Arran Brewery was a result of a virus being introduced into the system through an email attachment, indicating a software-related failure [Article 75823].
- The attack involved computer viruses that threatened to delete files unless a ransom was paid, highlighting a software-related issue [Article 75823]. |
| Objective (Malicious/Non-malicious) |
malicious |
(a) The software failure incident at Arran Brewery was malicious in nature. The incident was a ransomware attack where the brewery was locked out of its computer system after opening an email attachment containing a virus. The attackers demanded a ransom in bitcoins to restore the system, showing clear intent to harm the company's operations [75823]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions, accidental_decisions |
(a) The software failure incident at Arran Brewery was primarily due to poor decisions made by the employees. The incident occurred when the company fell victim to a ransomware attack after an employee opened an email attachment that contained a virus. This action led to the company being locked out of its computer system and facing a demand for ransom to restore the system [75823]. Additionally, the managing director mentioned that the attackers had posted a fake job vacancy on an international jobs site, leading to multiple emails with infected CV attachments being received by the company. This shows that the initial decision to open the email attachment was a result of poor judgment, contributing to the software failure incident [75823]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in the article was not due to development incompetence. It was caused by a ransomware attack where the company was tricked into opening an email attachment containing a virus, leading to the encryption of their computer system and a demand for ransom [75823].
(b) The software failure incident in the article was accidental in nature. The company fell victim to a ransomware attack after opening an email attachment that contained a virus, which was disguised among genuine job applications received by the company. This accidental action led to the encryption of their system and the loss of three months' worth of sales data [75823]. |
| Duration |
temporary |
(a) The software failure incident at Arran Brewery can be considered temporary as the company was locked out of its computer system due to being duped into opening an email attachment containing a virus. The incident resulted in the loss of three months' worth of sales data from one server. However, the company took action by using an IT consultant to eliminate the virus and was working on restoring the lost data [75823].
(b) The software failure incident can also be seen as temporary as the company was actively working on restoring the lost data and had taken steps to eliminate the virus from its system. Additionally, the incident was caused by a specific event - the opening of the malicious email attachment - rather than being a permanent failure due to inherent flaws in the system [75823]. |
| Behaviour |
other |
(a) crash: The software failure incident in the article is not described as a crash where the system loses state and does not perform any of its intended functions [75823].
(b) omission: The software failure incident in the article is not described as an omission where the system omits to perform its intended functions at an instance(s) [75823].
(c) timing: The software failure incident in the article is not described as a timing issue where the system performs its intended functions correctly, but too late or too early [75823].
(d) value: The software failure incident in the article is not described as a value issue where the system performs its intended functions incorrectly [75823].
(e) byzantine: The software failure incident in the article is not described as a byzantine failure where the system behaves erroneously with inconsistent responses and interactions [75823].
(f) other: The software failure incident in the article is described as a ransomware attack where the system was compromised due to a virus introduced through an email attachment, leading to the encryption of data and a demand for ransom to restore the system's functionality [75823]. |