As an old IT guy, I keep wondering what Crowdstrike was doing during the DNC Hack? It looks like a Lifelock commercial. Here is the Crowdstrike timeline.
- In 2015 Crowdstrike knows that DNC information was transmitted to Russia.
- On April 29th, 2016, the DNC suspects they have been hacked.
- On May 4th, 2016, Crowdstrike installs “monitoring software”.
- On June 10th, 2016, Crowdstrike changes passwords at the DNC.
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? It looks like Crowdstrike set up the DNC network as a “bad” honeypot. Traditionally a honeypot consists of a network site that appears to be legitimate but is actually isolated, monitored, and contains non-vital data. Crowdstrike used the real DNC network as the lure. If Fusion GPS and Crowdstrike are the private contractors who had unsupervised access to raw FISA information on FBI systems, they had to know what the Russians were doing. Were their actions negligent, stupid, or an attempt to divert the attention from the damaging Podesta emails that the Russians were boasting about? Since the Podesta emails were far more damaging to the Clinton campaign, it looks like Crowdstrike felt it was more important to attribute the hack on the Russians than to protect the DNC data.