As An Old IT Guy Who Was Skeptical Of The Original DNC Hack Explanation, I Am Looking Forward To The #DNCLawsuit

I'm a security monitorLike many other IT guys and gals, I was never sold on the original explanation of the DNC hack. There were so many loose ends.

  1. Why did the Russians hack the DNC servers? All of the embarrassing Clinton emails came from the Podesta emails that were acquired prior to the DNC Hack. It was the Podesta emails the Russians were using to taunt Trump and Clinton surrogates in London in May 2016. Yet most people think Ms. Wasserman Schultz was fired because of the DNC Hack. The DNC had plenty of reasons to fire Ms. Wasserman Schultz. The two biggest reasons were the way the DNC treated the Sanders campaign and the proportion of donations collected by the DNC given to the Clinton campaign. Obviously, the bad relations between the DNC and the Sanders campaign had nothing to do with the Russians.  If the Russians hacked the servers, why disclose the hack via Wikileaks so quickly? It was so out of character! It is almost as if the Russians hacked the DNC servers as a favor to the DNC.
  2. What was Crowdstrike doing during the DNC Hack? In a previous post, I remarked that Crowdstrike’s actions reminded me of a Lifelock commercial. I said, “If Crowdstrike knew the DNC was hacked in 2015 and information was transmitted back to Russia, why did they install a security monitor in May 2016? Why did they wait until June to actually fix the problem?”

If the DNC proceeds with the lawsuit there are two things I would like to find out.

1. Was Either Crowdstrike Or Fusion GPS One Of The Private Contractors Who Ran Unsupervised FISA-702 Queries In Early 2016?

The rumor is that Fusion GPS was the private contractor who ran unsupervised FISA-702 queries that resulted in the first FISA abuse of 2016. As I said in a previous post:

By April 18, 2016, the FBI they knew that their FISA-702 “Queries” irregularities had triggered a full Compliance Audit by the NSA. This would lead NSA to admit a non-compliance issue to the FISA court on October 26, 2016.

Most of the FISA-702 “Queries” irregularities occurred before April 2016. This was a really big FISA abuse that happened just days before the DNC Hack. I think the FBI and the private contractor took the risk because they did not think they would get caught. This would explain the arrogance that was displayed later in 2016 when the FISA court would be further abused with the Trump dossier. Considering the abuse the FISA court has taken, I wonder if they would be willing to disclose the name of the contractor if that contractor was found to be collecting information that could be used against political opponents.

  1. Did the private contractor have a relationship with the Democratic party?
  2. Was this unsupervised access to raw FISA data used to spy on political opponents?
  3. Was this unsupervised access to raw FISA data used to spy on the Sanders campaign or the DNC?
  4. Were they looking for previously unknown classified or top secret Clinton emails from her server that were not part of the emails she turned over?

2. What Was Crowdstrike Doing In May 2016?

This is a question that near and dear to old IT guys. In my world, if our systems are hacked on April 29th them my job is to have them fixed by April 30th. The idea that Crowdstrike did not fix the problem until June 10th is shocking.  Obviously, this was a lousy plan. Why let your systems be hacked for over 30 days? What did they learn that was so important?