Welcome Guest. | Log In | Register | Membership Benefits

Hackers Claim Breach Of Norton Antivirus Source Code; Experts Say Claims Are Exaggerated

Symantec says disclosure poses 'no threat' to the security of its AV products or their customers

Jan 07, 2012 | 12:48 PM | 

By Tim Wilson
Dark Reading
Symantec confirmed that a hacking group has gained access to some of the source code of its Norton Antivirus product, but also stated the code was old and not stolen directly from Symantec servers.

An Indian hacking group called the Lords of Dharmaraja has threatened to publicly disclose the source code.

"Symantec can confirm that a segment of its source code has been accessed," a spokesman told the publication InfoSec Island. "Symantec’s own network was not breached, but rather that of a third party entity. We are still gathering information on the details and are not in a position to provide specifics on the third party involved.

"Presently, we have no indication that the code disclosure impacts the functionality or security of Symantec's solutions. Furthermore, there are no indications that customer information has been impacted or exposed at this time."

The security company made a slightly longer statement on its Facebook page:

"Symantec can confirm that a segment of its source code used in two of our older enterprise products has been accessed, one of which has been discontinued. The code involved is four and five years old. This does not affect Symantec's Norton products for our consumer customers. Symantec's own network was not breached, but rather that of a third party entity."

The Facebook statement repeats the spokesman's statement about the limitations of the threat. However, it also makes reference to a "remediation process."

"Symantec is working to develop remediation process to ensure long-term protection for our customers' information," the statement says. "We will communicate that process once the steps have been finalized. Given the early stages of the investigation, we have no further details to disclose at this time but will provide updates as we confirm additional facts."

[From social media abuse to mobile malware to major busts, past year filled with new twists on old scams. See Social Media Abuse, Mobile Malware Headline 2011 Top Internet Security Trends.]

Symantec says it has investigated the claims made by the hacker group, and that data posted in Pastebin was not source code, but documentation dated from April 1999 related to an API used by Norton Antivirus.

The hacking group also shared source code related to the 2006 version of Symantec's Norton AntiVirus product with Infosec Island.

A hacker called "Yama Tough," a spokesman for the gang, posted the content to PasteBin and subsequently published messages on Google+ about the alleged breach. The content on PasteBin has since been removed, and Yama Tough's Google+ posts were deleted, Symantec says.

Although Symantec will not say where the source code came from, experts at the security firm Sophos say it's possible that the code was stolen from government servers after the Indian authorities demanded source code from many software providers.

Mike Lloyd, CTO at RedSeal Networks, says the hack could offer a lesson in protecting enterprise data from third-party breaches.

"The fact that Symantec suffered a breach due to lax protections in someone else's network is a significant wake-up call," Lloyd says. "It is not enough to ensure you follow best practices; in an interconnected world, you have to worry about the security of other organizations. Your business partners and strategic customers may be friendly, but they are not going to expose specifics to you about how well they protect themselves.

"This issue -- needing to understand the risk of a network you cannot see -- has led to standards like PCI, FISMA, and DISA STIGs, which establish agreed, measurable baselines of 'basic hygiene,'" Lloyd observes. "As we steadily lose control of our own critical assets, and as attackers increasingly automate their attacks, we will need more baselines like this so that one organization can show another that it is well-run."

Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports