Kaspersky Explains Why They Won't Say Who Hacked Them
New submitter ChannelGonzo writes: Larry Walsh at Channelnomics scores the scoop in a Q&A with Kaspersky's Chris Doggett who says it's not the Russian security company's job to figure out who is responsible for a sophisticated cyber attack on its corporate network over the past few months. "We believe that to go beyond our area of expertise and speculate on the possible sources of attacks is not in the best interest of our customers," Doggett said.
Well, sometimes you can say somethings by saying "i won't say"... i think many of us can understand that they already said who they think those who hacked them were - i understand that as an international company they try to avoid any nationalistic references because it is really bad for business, especially when most of your clients will consider it as an attack to them personaly.
Antisthenes: "Wisdom begins by examining the words/names." - excuse my English, i am (slightly...) better with my Greek!
They wont say because if they do they will all have mysterious 'accidents'....just like happened to Putin's enemies in the past. http://www.cnn.com/2015/03/03/... http://www.theglobeandmail.com... http://www.businessinsider.com...
Whoever hacked Kaspersky was probably hunting moles. From the outside, it looks as if Kaspersky has been positively brilliant, revealing state level actors, cracking stuxnet, duqu, & duqu2. But what if some other state level actor had been feeding Kaspersky? What if spies, not security researchers, told Kaspersky where to look? It would be worth a lot for the authors of stuxnet etc to be able to confirm or deny that Kaspersky worked without help. That's the best reason I can see for hacking into Kaspersky.
--- Often in error; never in doubt!
The Mossad don't work for the US. It's the other way around.
You are welcome on my lawn.
I read the report and they were clear without saying directly.
1. From compile dates the office work week was Sunday to Friday.
2. There was much less activity on Friday and no activity on Saturday.
3. The time zone was UTC+2 hours
That is code for Israel. They could not be any clearer withut saying it directly.