Friday, July 29, 2016

Director of U.S. National Intelligence Is Not Ready To Name Who is Responsible For The DNC Hack

National Intelligence Director James Clapper, shown at the State Department in Washington on July 21, said U.S. intelligence agencies haven't reached a firm conclusion as to whether Russia or any other country was behind the recent computer breach that stole emails and other records from the Democratic National Committee. PHOTO: JOSHUA ROBERTS/REUTERS

Reuters: U.S. intelligence chief not ready to identify source of Democratic email hack

Director of National Intelligence James Clapper, speaking about the hack of Democratic Party emails, said on Thursday the U.S. intelligence community was not ready to "make the call on attribution" as to who was responsible.

The White House said earlier the FBI had not disclosed any information about who was behind the hack.

Cyber security experts and U.S. officials said on Monday there was evidence that Russia engineered the release of sensitive Democratic Party emails in order to influence the U.S. presidential election.

The emails were released by the anti-secrecy group WikiLeaks on the eve of the Democratic National Convention, and appeared to show that the Democratic National Committee favored Hillary Clinton over her chief rival, U.S. Senator Bernie Sanders.

Read more ....

More News On The Director of U.S. National Intelligence Not Ready To Name Who is Responsible For The DNC Hack

Top spy: Despite intelligence 'war' with Russians, it's too soon to blame them for DNC hack -- Politico
Top Intel Official Tells Americans to End 'Hyperventilation' Over DNC Hack, But Calls Breach Potentially 'Serious' -- ABC News
US Intelligence Not Ready to Name Party Behind DNC Hack -- Sputnik
U.S. Intelligence Chief James Clapper Says Russia Sees Meddling in Election as Payback -- WSJ
Intel chief: Americans need to calm down about DNC hack -- Washington Examiner
America's top spy just hinted at how much leverage Russia truly has over Washington -- Natasha Bertrand, Business Insider

No comments:

Post a Comment