| Recurring |
one_organization |
(a) The software failure incident having happened again at one_organization:
Marriott experienced another software failure incident, with up to 5.2 million guests at risk, following a previous breach in November 2018 [97175]. This incident involved unauthorized access to guest information through the credentials of franchise property employees, similar to the indirect nature of the 2018 breach [97175].
(b) The software failure incident having happened again at multiple_organization:
There is no specific mention in the provided article about similar incidents happening at other organizations or with their products and services. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase can be seen in the Marriott hack incident. The breach occurred when someone used the credentials of two franchise property employees to access an "unexpected amount of guest information." This breach was a result of vulnerabilities introduced in the system development or operation, as the credentials may have been stolen or misused [97175].
(b) The software failure incident related to the operation phase is evident in the Marriott hack incident as well. Marriott observed the suspicious activity by the end of February, indicating that the intrusion persisted for several weeks before being flagged. This delay in detecting the breach highlights operational issues or misuse of the system that allowed the unauthorized access to continue for an extended period [97175]. |
| Boundary (Internal/External) |
within_system, outside_system |
(a) The software failure incident reported in the article is primarily within_system. The breach at Marriott was due to someone using the credentials of two franchise property employees to access an "unexpected amount of guest information" [97175]. This indicates that the failure originated from within the system, specifically through compromised credentials within the organization. Additionally, the article mentions that Marriott's security posture and handling of the incident, such as the delay in notifying affected individuals, are internal factors contributing to the failure.
(b) The software failure incident also has elements of outside_system factors. The article highlights the vulnerability of companies like Marriott to supply chain attacks, emphasizing the need to secure not only their own business but also that of their partners, contractors, and franchisees [97175]. This indicates that external factors, such as the security practices of third-party entities connected to the organization, can contribute to software failures. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in Article 97175 occurred due to non-human actions. The breach at Marriott was initiated when someone used the credentials of two franchise property employees to access an "unexpected amount of guest information." This unauthorized access led to the compromise of sensitive data of up to 5.2 million guests [97175]. The breach was not a result of direct human actions but rather due to the exploitation of credentials, indicating a failure introduced without direct human participation. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident related to hardware:
- The article does not provide specific information about the software failure incident being directly caused by hardware issues. It mainly focuses on the hack that compromised guest information at Marriott [97175].
(b) The software failure incident related to software:
- The software failure incident at Marriott was due to a hack that compromised guest information. The intrusion occurred when someone used the credentials of two franchise property employees to access an unexpected amount of guest information. This indicates a failure in the software security measures that allowed unauthorized access to sensitive data [97175]. |
| Objective (Malicious/Non-malicious) |
malicious |
(a) The software failure incident reported in the article is malicious in nature. The incident involved a hack on Marriott's system, compromising the information of up to 5.2 million guests. The hack was initiated by someone using the credentials of two franchise property employees to access guest information, indicating a deliberate attempt to breach the system and steal sensitive data [97175]. |
| Intent (Poor/Accidental Decisions) |
unknown |
The software failure incident reported in the articles does not directly point to a specific intent behind the failure, such as poor decisions or accidental decisions. The incident primarily focuses on the details of the hack, the impact on the affected individuals, the response measures taken by Marriott, and the potential implications of the breach. Therefore, it is unknown whether the failure was due to poor decisions or accidental decisions based on the information provided in the articles. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident related to development incompetence is evident in the Marriott hack incident. The breach occurred when someone used the credentials of two franchise property employees to access an "unexpected amount of guest information" [97175]. This breach highlights the importance of securing not only a company's business but also that of their partners, contractors, and franchisees, emphasizing the vulnerability in the supply chain [97175].
(b) The software failure incident related to accidental factors is seen in the delayed detection of the suspicious activity by Marriott. The intrusion persisted for several weeks before being flagged by the end of February, indicating a lack of timely detection and response mechanisms in place [97175]. |
| Duration |
temporary |
(a) The software failure incident described in the article is temporary. The intrusion into Marriott's system occurred in mid-January, and Marriott only observed the suspicious activity by the end of February, indicating that the incident persisted for several weeks before being flagged [97175]. This indicates that the failure was temporary and not permanent. |
| Behaviour |
other |
(a) crash: The article does not mention a crash as the cause of the software failure incident. [97175]
(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). [97175]
(c) timing: The incident does not involve a timing failure where the system performs its intended functions correctly but too late or too early. [97175]
(d) value: The software failure incident in the article does not involve a value failure where the system performs its intended functions incorrectly. [97175]
(e) byzantine: The software failure incident in the article does not exhibit a byzantine failure where the system behaves erroneously with inconsistent responses and interactions. [97175]
(f) other: The behavior of the software failure incident in the article is related to a security breach/hack compromising guest information, indicating a breach of data security rather than a specific software behavior failure. [97175] |