two breaches to the DNC in October and in at least one of them, the Sanders campaign felt confident that their data had been compromised.
There was no leak by the DNC to the media in October like there was this time
There was no locking out of the voter file of the offending campaign in October like there was this time because ...
There was no independent audit triggered by the DNC to get to the bottom of these incidents like they're talking about doing for this incident.
And there was even more reason to audit in October: because no campaign had admitted to breaching Sanders data in October nor did they have any assurance they got Sanders data back (if it was taken) whereas this time, the Sanders campaign readily stated what it had done and why.
A lot of fuss to protect Hillary's data this time but very little fuss to protect Bernie's data twice, in very similar circumstances last October - so you can't even count the DNC lack of response in October as a one off thing.
And that is in part why this Sanders techy wanted proof of the at least third exposure of their data - which got him fired. As someone who has worked in IT for decades, the guy has my sympathy. Apparently, the Sanders campaign fired him for not telling them immediately - but he did tell them before the breach got closed off. It was closed 41 minutes after they discovered it.
He said it took them a while (a few minutes) to get a handle on what they were seeing - which to me, is understandable. I still think the guy got the shaft - was a fall guy in this because I would have done what he did:
- figure out a little about what was going on so I could raise the alarm accurately and credibly
- get others to witness it and help get some evidence of the breach to protect the organization I work for - to give them something to prove the breach should they need it
= new reply since forum marked as read
