“He said the program thought it had been hacked, which triggered a laborious process of rebooting the whole system with new passwords.”
My connections in the intelligence community seriously believe that this was a possibility.
That sort of thing will happen to people who imagine they are really running for president ~ you attract just all sorts of nasty characters.
"There were glitches in the system, I don't want to gloss over that. We were able to beta test it, but not at the volume of data we needed."
As I said on another thread early this morning, these types of failures happen for one of two reasons. One of the reasons I noted was the failure to test a system at peak load to ensure availability.
Looks like I was right.
I also said that an improperly designed system which did not take into account peak usage periods, nor an engineered capability to bring online additional capacity quickly, as needed could appear as though it had been hacked.
The appearance that the system was hacked is entirely due to a design failure in which an over-burdened system fails to respond.
As noted in the article, they did not test with the volume of data (peak performance) that they expected.
Systems Analysis and Design 101 would've taught them that's exactly what they should've done before going live. Anyone who's spent 25 years in Information Technology designing highly available, reliable and scalable infrastructures across banking, finance, insurance, legal advertising and automotive industries would say the same thing.