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.

Assigning Responsibility

The Department of Defense's fiscal 2010 budget requires DOD to identify vulnerabilities at multiple levels of the supply chain for a number of major IT acquisition programs. The DOD will have to prioritize those vulnerabilities and their potential effects, create recommendations for managing risk, and identify someone to lead development of "an integrated strategy for managing risk in the supply chain."

The Comprehensive National Cyber Initiative, meanwhile, includes a group working on standards, another on sharing supply chain vulnerabilities, and a third on policy, chaired by DOD and the Department of Homeland Security, with participation from the National Institute of Standards and Technology.

Uncle Sam wants to ensure that when agencies purchase products, especially classified as high-impact systems (critical business and national security systems, among others), agencies think about "the threats that can come from the supply chain as systems and software are being built and delivered," says NIST computer security division IT specialist Marianne Swanson, who's heading up the standards working group.

NIST's draft guidelines include elements such as procurement strategies requiring suppliers to carry out specific risk mitigation processes. The departments of Defense and Homeland Security are testing these processes in a pilot project, and their findings will be integrated into a draft report early next year for public comment. The draft identifies 32 practices, such as using contract language that requires suppliers to inform agencies of the identities of their contractors and subcontractors and obvious steps like focusing on the supply chain security of agencies' most critical IT components.

It's too early to tell just what the final draft will look like, but a NIST presentation online lays out security steps throughout the technology life cycle, from design to retirement. The prototype strategy encourages the use of trusted suppliers, service-level agreements related to quality and security during the manufacturing stage, vetting of software updates, use of secure distribution channels, and secure destruction of media after use.

Once DOD and DHS carry out their pilot programs, the General Services Administration will use "market incentives" to make security a bigger part of hardware and software product designs and to encourage development of new security technologies and secure managed services. This process began late last year, when the Federal Acquisition Regulatory Council released a draft notice of proposed rule-making that would create an authenticity guarantee for federal contractors and software and hardware vendors. SAIC's Rossman expects policy to be rolled out formally in the next year.

Previous
4 of 5
Next
Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading December Tech Digest
Experts weigh in on the pros and cons of end-user security training.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2037
Published: 2014-11-26
Openswan 2.6.40 allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via IKEv2 packets that lack expected payloads. NOTE: this vulnerability exists because of an incomplete fix for CVE 2013-6466.

CVE-2014-6609
Published: 2014-11-26
The res_pjsip_pubsub module in Asterisk Open Source 12.x before 12.5.1 allows remote authenticated users to cause a denial of service (crash) via crafted headers in a SIP SUBSCRIBE request for an event package.

CVE-2014-6610
Published: 2014-11-26
Asterisk Open Source 11.x before 11.12.1 and 12.x before 12.5.1 and Certified Asterisk 11.6 before 11.6-cert6, when using the res_fax_spandsp module, allows remote authenticated users to cause a denial of service (crash) via an out of call message, which is not properly handled in the ReceiveFax dia...

CVE-2014-7141
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (out-of-bounds read and crash) via a crafted type in an (1) ICMP or (2) ICMP6 packet.

CVE-2014-7142
Published: 2014-11-26
The pinger in Squid 3.x before 3.4.8 allows remote attackers to obtain sensitive information or cause a denial of service (crash) via a crafted (1) ICMP or (2) ICMP6 packet size.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Now that the holiday season is about to begin both online and in stores, will this be yet another season of nonstop gifting to cybercriminals?