Blog Posts Tagged with "Norton GoBack"

7fef78c47060974e0b8392e305f0daf0

Symantec Source Code Leak: The Real Elephant in the Room

February 08, 2012 Added by:Infosec Island Admin

Everyone is all over the fact that the Symantec code had been hacked back in 2006 right? I have not seen anything about the real elephant in the room. Where has the code been lo’ these many years? Who had it? Who hacked Symantec in the first place? Anyone? Anyone? Bueller?

Comments  (0)

6d117b57d55f63febe392e40a478011f

Symantec: Emails Part of Law Enforcement Sting Operation

February 07, 2012 Added by:Anthony M. Freed

"The e-mail string posted by YamaTough was actually between them and... law enforcement. YamaTough actually reached out to us, first, saying that if we provided them with money, they would not post any more source code. At that point... it was a clear cut case of extortion..."

Comments  (1)

296634767383f056e82787fcb3b94864

The 2006 Theft of Symantec's Source Code - Response and Repercussions

January 26, 2012 Added by:Jeffrey Carr

Symantec has acknowledged that source code for multiple products was stolen in 2006. The worst part is that Symantec was clueless about the theft of its own source code for almost six years, which means that thousands of customers were clueless as well...

Comments  (1)

03b2ceb73723f8b53cd533e4fba898ee

Symantec: The Inconvenient Truth Behind the Data Breach

January 17, 2012 Added by:Pierluigi Paganini

Initially, Symantec spokesman Cris Paden said the hackers had stolen only the source code of Symantec Endpoint Protection 11.0 and Symantec AntiVirus 10.2, minimizing the seriousness of the breach. The situation has now changed dramatically...

Comments  (0)

69dafe8b58066478aea48f3d0f384820

Symantec Hacked in 2006? Claim Raises More Questions

January 17, 2012 Added by:Headlines

Symantec now claims that the company's own networks were in fact breached back in 2006, leading to the loss of proprietary product data: "...an investigation into the matter had revealed that the company's networks had indeed been compromised"...

Comments  (3)