5 ms·
I find the story or incorrect archive settings/setup to be reasonably plausible and even likely. I work in finance and misconfiguration of systems are not that
by giantg2 3y ago
I find the story or incorrect archive settings/setup to be reasonably plausible and even likely. I work in finance and misconfiguration of systems are not that uncommon. Testing and reviewing archive settings is often not very thorough.
For example, I was working on a system that handles holdings and trading information at the fund level which covers AUM that starts with a T and ends in rillions. There was an SQL injection vulnerability with schema owner access. Luckily this was an internal app, but still there are trade desk devs who could accidentally paste a drop table statement with a name collison. Anyways, I brought all this up to the principal. I was told this isn't a real big deal because they have real-time backups. I asked if they ever tested the backups... no. Do they have procedures for restoring from backups... no. They go nuts if there's a 5 minute outage, so how long would it take to restore... no idea.
Trust me ignorance is very believable, even in regulated industries.
- kindatrue 3y ago>I asked if they ever tested the backups... no. THIS. I briefly worked for a major European bank. There was a system that was backed up on tape. The way they checked the backups was to visually look at the tape spool - before sending the tapes off to a mountain to be preserved. One day, they needed something from a back up. Sure enough, the tapes were simply blank due a bug in the back up script.
- giantg2 3y ago"The way they checked the backups was to visually look at the tape spool" Lol
- 36479669thrw 3y ago> I find the story or incorrect archive settings/setup to be reasonably plausible and even likely. I work in finance and misconfiguration of systems are not that uncommon. Testing and reviewing archive settings is often not very thorough. GP's point stands: they should be fined to a degree that it becomes clear to management that these "not uncommon" practices must become very uncommon.
- JumpCrisscross 3y ago> they should be fined to a degree that it becomes clear to management that these "not uncommon" practices must become very uncommon Why? Fining isn’t done for fetish, it’s done proportional to harm. The article mentions twelve civil suits (four independent). JPMorgan will lose those. Any lawyer worth their salt, meanwhile, will be looking for claims which could reasonably involve the evidence which was deleted to file. In this way, the people actually harmed get compensated versus a government agency, which mitigates corruption concerns.
- 36479669thrw 3y agoDon't get stuck on the word "fine'. The fines cans be judgment at court. The cost of doing business this way must go up, way up, so that these critical institutions are legally transparent* and motivated by a strong desire to avoid drastic haircuts. *for example, no more "the dog ate our homework" excuses.
- JumpCrisscross 3y ago> Don't get stuck on the word "fine'. The fines cans be judgment at court. All fines are subject to court supervision. This sentence makes no sense. > cost of doing business this way must go up, way up We want regulators thinking of the public, not randomly increasing the cost of business. This seems more motivated by hatred for a thriving industry than claims to specific damages. Regulators who pursue this path are rightfully overturned by courts for acting capriciously.
- gmd63 3y agoRegulators are not thinking of the public when they allow corporate sociopaths to neglect societal best interest while market fixing / mismanaging records / etc., activities that have demonstrably siphoned wealth from the lower class and moved it increasingly to the ivory towers of companies that do not deserve the influence that makes them "too big to fail". The wealth inequality gap is widening and it's due to pussyfooted enforcement on white collar crime and strategic negligence.