Risk
11/5/2009
01:45 PM
50%
50%

Securing The Cyber Supply Chain

Many parties touch your organization's systems and software, potentially exposing them to malware, breaches, or worse. A new end-to-end approach is required to minimize the risks.

Beware Back Doors

Software pedigree--knowing who developed code at every step, and being able to verify its trustworthiness--is one of the most critical, yet challenging, steps. Earlier this year, Arab telecom provider Etisalat pushed to BlackBerry users what it said was a software update for improving performance. In fact, it was spyware capable of providing access to information on the devices.

Brian Chess, chief scientist at Fortify, a company that specializes in assuring software security, recommends a three-step process: Take a software inventory and apply tools that analyze code for vulnerabilities; ask software vendors to document the steps in their development processes; and recognize that neither of those steps is enough, and therefore be rigorous in your other cybersecurity efforts.

Once software is installed, to make sure hackers aren't using back doors built into code, it's important to baseline network traffic, says NetForensics VP Tracy Hulver. If something looks amiss, "I can be alerted and do something about it," he says. That applies to anomalies in user behavior, as well. "You say, I'm getting database access from an IP address that's outside the United States, and that's unusual, so I need to terminate that," Hulver says.

Verizon's Sachs recommends a multitiered approach to risk mitigation, including establishing new coding standards in the software industry, close monitoring of offshore software development, and a mandate that all critical software used by government agencies be written domestically.

The software industry is in the early days of figuring out how to discuss supply chain issues. SAFECode is working with Adobe, EMC, Juniper, Microsoft, Nokia, SAP, and Symantec to develop best practices in secure software development. "We discovered there really wasn't a common lexicon or template for describing supply chain integrity," says Paul Kurtz, executive director of SAFECode and a top White House cybersecurity official in the Bush administration. "Now they're looking at this collectively, which is incredibly important because they're developing a common framework."

Bill Billings, chief security officer for Microsoft's federal group, believes the computer industry should adopt what he calls the Campbell's soup model, where a product-tracking number on every can makes it possible for consumers to get information on where and when soup was made. "You're not changing the quality of it, but you are changing the fact that it comes from somebody you knew rather than somebody you didn't," he says. "It's getting rid of the man-in-the-middle attacks."

chart: Alignment is Off

Previous
3 of 5
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-1449
Published: 2014-12-25
The Maxthon Cloud Browser application before 4.1.6.2000 for Android allows remote attackers to spoof the address bar via crafted JavaScript code that uses the history API.

CVE-2014-2217
Published: 2014-12-25
Absolute path traversal vulnerability in the RadAsyncUpload control in the RadControls in Telerik UI for ASP.NET AJAX before Q3 2012 SP2 allows remote attackers to write to arbitrary files, and consequently execute arbitrary code, via a full pathname in the UploadID metadata value.

CVE-2014-3971
Published: 2014-12-25
The CmdAuthenticate::_authenticateX509 function in db/commands/authentication_commands.cpp in mongod in MongoDB 2.6.x before 2.6.2 allows remote attackers to cause a denial of service (daemon crash) by attempting authentication with an invalid X.509 client certificate.

CVE-2014-7193
Published: 2014-12-25
The Crumb plugin before 3.0.0 for Node.js does not properly restrict token access in situations where a hapi route handler has CORS enabled, which allows remote attackers to obtain sensitive information, and potentially obtain the ability to spoof requests to non-CORS routes, via a crafted web site ...

CVE-2014-7300
Published: 2014-12-25
GNOME Shell 3.14.x before 3.14.1, when the Screen Lock feature is used, does not limit the aggregate memory consumption of all active PrtSc requests, which allows physically proximate attackers to execute arbitrary commands on an unattended workstation by making many PrtSc requests and leveraging a ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.