| Recurring |
multiple_organization |
(a) The software failure incident at the Australian stock exchange (ASX) is not explicitly mentioned to have happened again within the same organization in the provided article [108164].
(b) The article mentions a similar incident in neighboring New Zealand, where they faced cyber attacks in August that crashed their website and impacted trading. This incident in New Zealand could be considered a similar event happening at another organization [108164]. |
| Phase (Design/Operation) |
design |
(a) The software failure incident at the Australian stock exchange was related to the design phase. The issue affected trading of multiple securities in a single order and led to inaccurate market data. The problem arose as the ASX's new equity market trading platform went live on Monday, despite more than a year of testing by customers, third parties, the ASX, and Nasdaq [108164].
(b) There is no specific information in the provided article indicating that the software failure incident was related to the operation phase. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident at the Australian stock exchange was within the system. The article mentions that a software problem affected trading of multiple securities in a single order and led to inaccurate market data. ASX and its technology provider Nasdaq identified the root cause internally and planned to resolve the issue overnight [108164]. The incident was related to the ASX's new equity market trading platform, indicating an internal system issue. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in this case was primarily due to non-human actions. The article mentions that a software problem forced Australia's stock exchange to halt trading, affecting multiple securities in a single order and leading to inaccurate market data. The issue was related to the ASX's new equity market trading platform, despite extensive testing by various parties including customers, third parties, ASX, and Nasdaq [108164].
(b) The article does not provide specific information indicating that the software failure incident was directly caused by human actions. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident reported in Article 108164 was due to contributing factors originating in software. The Australian stock exchange had to halt trading due to a software problem that affected trading of multiple securities in a single order and led to inaccurate market data. ASX and its technology provider Nasdaq identified the root cause as a software issue and were working on a resolution to fix it [108164]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident reported in Article 108164 was non-malicious. The incident was attributed to a software problem that affected trading of multiple securities in a single order and led to inaccurate market data. The issue was identified by the ASX and its technology provider Nasdaq, and they were working on resolving it overnight to reopen the market the next day. ASX's CEO, Dominic Stevens, accepted responsibility for the failure and emphasized the obligation to provide a reliable and resilient trading system for the market [108164]. |
| Intent (Poor/Accidental Decisions) |
unknown |
(a) The software failure incident at the Australian stock exchange was not explicitly attributed to poor decisions. However, it was mentioned that the issue affected trading of multiple securities in a single order and led to inaccurate market data. The incident occurred as the ASX's new equity market trading platform went live on Monday, despite more than a year of testing by customers, third parties, the ASX, and Nasdaq [Article 108164].
(b) The software failure incident at the Australian stock exchange was not explicitly attributed to accidental decisions. The article mentioned that ASX and its technology provider Nasdaq identified the root cause of the issue and were working on a resolution to fix it overnight. ASX's CEO, Dominic Stevens, accepted responsibility for the incident and emphasized the obligation to provide a reliable and resilient trading system for the market [Article 108164]. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident at the Australian stock exchange was attributed to a software problem that forced the exchange to halt trading shortly after opening. The issue affected trading of multiple securities in a single order and led to inaccurate market data. Despite more than a year of testing by various parties, including customers, third parties, ASX, and Nasdaq, the problem arose as the ASX's new equity market trading platform went live [108164]. This indicates a potential failure due to development incompetence, as the issue was not identified and resolved during the extensive testing phase.
(b) The software failure incident at the Australian stock exchange was described as a software problem that led to the halt of trading shortly after opening. The issue affected trading of multiple securities in a single order and resulted in inaccurate market data. ASX and Nasdaq identified the root cause and planned to resolve it overnight [108164]. This suggests that the failure was accidental, as it was not intentional but rather an unforeseen issue that arose during the trading process. |
| Duration |
temporary |
(a) The software failure incident in this case was temporary. The Australian stock exchange had to halt trading 20 minutes after opening due to a software problem, but they planned to reopen the market the next day after identifying the root cause and resolution path to fix it [108164]. |
| Behaviour |
crash, omission, value, other |
(a) crash: The software failure incident in the ASX stock exchange caused a crash, leading to the halt of trading just 20 minutes after opening on Monday [108164].
(b) omission: The software issue resulted in the omission of trading multiple securities in a single order and led to inaccurate market data [108164].
(c) timing: The incident caused the market to open late, as it was planned to reopen on Tuesday at 10 a.m. instead of the usual opening time [108164].
(d) value: The software failure incident led to the system performing its intended functions incorrectly, affecting the trading of securities and market data [108164].
(e) byzantine: There is no specific mention of the software failure incident exhibiting byzantine behavior in the provided article.
(f) other: The software failure incident also involved the ASX's new equity market trading platform going live on Monday despite more than a year of testing, indicating a potential oversight or misjudgment in the deployment process [108164]. |