Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

1/10/2012
06:11 PM
50%
50%

When Someone Else's Insider Is Your Threat

Contract language and enforcement are necessary to protect your IP in another company's network. Just ask Symantec, which had its source code stolen from a third party by hackers.

Protecting intellectual property against insiders is tough enough when the insiders are a company's own employees. The problem becomes even more difficult when a third party -- whether a vendor or customer -- has access to confidential information.

Just ask Symantec. Last week, the company confirmed that a group of hackers had stolen the source code to two of the firm's older products -- Endpoint Protection 11.0 and Antivirus 10.2 -- from a third party. The group of allegedly Indian hackers, using the name "The Lords of Dharmaraja," claimed that the leak came from the Indian government and planned to release the code to the public.

"Symantec’s own network was not breached, but rather that of a third party entity," a Symantec spokesman said in an e-mailed statement.'"We are still gathering information on the details and are not in a position to provide specifics on the third party involved."

The leak is an embarrassment to the company, but Symantec maintains that it does not represent a major threat. The source code from the two program is four to five years old, Paden says.

"Presently, we have no indication that the code disclosure impacts the functionality or security of Symantec’s solutions," he says. "In 2010 alone, we distributed 10 million updates to our products in response to new cyber threats. If you extrapolate to four and five years, you can get an idea of how much our ... code has evolved over the following years."

Yet, a significant question for companies is why did the Indian government, if the code was indeed stolen from the government, keep the code so long, says Rob Rachwald, director of security strategy for Imperva.

"This incident will change how companies go about letting governments vet their source code," he says. "I don't think they will just hand it over anymore."

Companies need to rethink their approach, not just to their government clients, but to any third party that has access to their proprietary information, says Michael R. Overly, a partner in the security and information practice at law firm Foley & Lardner LLP. Every company should follow a three-step plan: do their due diligence and investigate the third party, create a contract that holds the third party liable, and follow up with the firm to validate its compliance.

"This is a sliding scale," he says. "You don't do all of this for every transaction. It depends on the sensitivity of the information."

Due diligence is extremely important because in many cases, such as with many commodity cloud vendors, a company cannot change the contract, says Overly. Checking on the third party's security measures, conducting audits, and even site visits can help assure a company that their partner will take data security seriously. When the contract is negotiable, placing liability on the third party can help address concerns.

"It is not enough to do due diligence," Overly says. "If the vendor has no responsibility for your data, then it doesn't mean much."

Validating that the third party is following the contract with periodic compliance check is also important, says Jason Lewis, chief technology officer of Lookingglass Cyber Solutions, a security monitoring and intelligence provider.

"I can tell someone to do something, but if they are intent on doing the opposite, there's little you can do about it," he says.

Technology can both be a contract requirement and a way to ensure compliance. Companies looking for a good place to start should refer to their own practices, says Nikfar Khaleeli, group product marketing manager for data-loss protection at McAfee.

"When you are working with anyone, you need to extend your data protection practices out and make sure that your third-party vendor is following the policies as well," he says.

For third parties that may not protect the data as stringently as the intellectual property owner, digital rights management (DRM) technology can act as a gatekeeper, allowing the owner to have some control over access to the confidential information.

In the case of Symantec, for example, the company could have encrypted the information with a DRM scheme and revoked the keys to its source code after a certain time period. The company would not have then had to worry less about whether copies of the code continued to exist.

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

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-27132
PUBLISHED: 2021-02-27
SerComm AG Combo VD625 AGSOT_2.1.0 devices allow CRLF injection (for HTTP header injection) in the download function via the Content-Disposition header.
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...