| Recurring |
one_organization |
(a) The software failure incident related to Goldman Sachs failing to record certain audio calls due to a software problem in 2014. This incident occurred within the same organization [91968]. |
| Phase (Design/Operation) |
design |
(a) The software failure incident in the article was related to the design phase. The failure occurred due to a software problem that resulted in Goldman Sachs failing to record the phone lines of trading and sales desks for around three weeks in 2014. This issue was attributed to a design flaw in the system that prevented the recording of audio calls, ultimately leading to the failure to comply with regulatory requirements [91968].
(b) There is no information in the article indicating that the software failure incident was related to the operation phase. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident mentioned in Article 91968 was within_system. The article states that a software problem within Goldman Sachs resulted in the bank failing to record the phone lines of trading and sales desks for around three weeks in 2014. This internal software issue led to the failure to make and keep certain audio recordings, which was a requirement by the U.S. Commodity Futures Trading Commission (CFTC) [91968]. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the article was due to non-human actions. The U.S. Commodity Futures Trading Commission (CFTC) ordered Goldman Sachs to pay $1 million for failing to make and keep certain audio recordings because of a software problem that resulted in the bank failing to record the phone lines of trading and sales desks for around three weeks in 2014. This problem was not intentionally introduced by human actions but was a result of a software issue [91968]. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident mentioned in the article was due to a software problem that resulted in Goldman Sachs failing to record the phone lines of trading and sales desks for around three weeks in 2014. This indicates that the failure originated in the software rather than hardware [91968]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident mentioned in Article #91968 was non-malicious. The failure occurred due to a software problem at Goldman Sachs, which resulted in the bank failing to record the phone lines of trading and sales desks for around three weeks in 2014. This failure was not attributed to malicious intent but rather to a technical issue within the software system [91968]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions, accidental_decisions |
The software failure incident at Goldman Sachs, as reported in Article #91968, was due to a software problem that resulted in the bank failing to record the phone lines of trading and sales desks for around three weeks in 2014. This incident could be categorized under both options:
(a) poor_decisions: The failure could be attributed to poor decisions related to the software implementation or maintenance that led to the inability to record the necessary audio calls.
(b) accidental_decisions: The failure could also be attributed to accidental decisions or mistakes made during the software operation or configuration that resulted in the lack of audio recordings.
Therefore, based on the information provided in the article, the software failure incident at Goldman Sachs could be associated with both poor decisions and accidental decisions. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident mentioned in Article 91968 was not attributed to development incompetence. The failure was specifically linked to a software problem that resulted in Goldman Sachs failing to record phone lines of trading and sales desks for around three weeks in 2014. This indicates a technical issue rather than a failure due to incompetence in development.
(b) The software failure incident in Article 91968 was more aligned with an accidental cause. The failure was described as a software problem that led to the bank's failure to record certain audio calls, which came to light when the bank was unable to provide the recordings during an investigation by the CFTC. This suggests that the failure was unintentional and not deliberately caused by human error or incompetence. |
| Duration |
temporary |
The software failure incident mentioned in Article #91968 was temporary. It occurred for around three weeks in 2014 when a software problem at Goldman Sachs resulted in the bank failing to record the phone lines of trading and sales desks. This temporary failure led to the bank being unable to provide audio calls when requested by the CFTC during a separate investigation [91968]. |
| Behaviour |
crash |
(a) crash: The software failure incident in the article was a crash where the system lost state and did not perform its intended functions. The article mentions that a software problem resulted in the bank failing to record the phone lines of trading and sales desks for around three weeks in 2014, leading to the system not being able to provide audio calls when asked by the CFTC [Article 91968]. |