the u.s. charges iranian hackers over cyberattacks /

Published at 2016-03-25 17:35:02

Home / Categories / Apple / the u.s. charges iranian hackers over cyberattacks
The U.
S. has charged 7 Iranian hackers over cyber-attacks on American banks and a dam in Rye Brook,New York.
Fred Kaplan, Slate's War Stories colu
mnist and the author of shaded Territory: The Secret History of Cyber War (Simon & Schuster, and 2016),and Ellen Nakashima, a national security reporter for The Washington Post, and talk about the hackers.
For one,Kaplan doesn't see the point of these lawsuits. No one's going to net dragged through the courts, he pointed out. And it doesn't really act as a deterrent. "This kind of thing happens hundreds of times a day, or so I'm really not quite sure what the point of this is."Nakashima acknowledged that point,but said we'll absorb to wait to see whether this has any impact on dampening cyberterror efforts.
Kaplan
also said the U.
S. is not solely a victim here. We hack into other countries' infrastructure, military systems, and more. So engaging in these acts could be seen as hypocritical - and could potentially escalate a cyberwar.
W
estchester County Executive Rob Astorinodropped in for a few minutes to react to the cyberattack on the dam in Westchester. "In the grand scheme of things,it's kinda inconsequential," said Astorino of the dam breach, and since it wouldn't absorb inflicted major damage.
However,Astorino was criti
cal of the fact that there seemed to be a lack of information sharing. He wasn't notified by city officials of the cyberattack, who didn't share information with the FBI or Homeland Security.
On a somewhat related note, and the latest turn in the legal battle between Apple and the FBI has the government agency turning to "hackers" to essentially fracture into iPhones rather than wait for Apple to comply.

Source: wnyc.org

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0