Risk
11/5/2009
01:45 PM
Connect Directly
RSS
E-Mail
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
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6335
Published: 2014-08-26
The Backup-Archive client in IBM Tivoli Storage Manager (TSM) for Space Management 5.x and 6.x before 6.2.5.3, 6.3.x before 6.3.2, 6.4.x before 6.4.2, and 7.1.x before 7.1.0.3 on Linux and AIX, and 5.x and 6.x before 6.1.5.6 on Solaris and HP-UX, does not preserve file permissions across backup and ...

CVE-2014-0480
Published: 2014-08-26
The core.urlresolvers.reverse function in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not properly validate URLs, which allows remote attackers to conduct phishing attacks via a // (slash slash) in a URL, which triggers a scheme-relative URL ...

CVE-2014-0481
Published: 2014-08-26
The default configuration for the file upload handling system in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 uses a sequential file name generation process when a file with a conflicting name is uploaded, which allows remote attackers to cause a d...

CVE-2014-0482
Published: 2014-08-26
The contrib.auth.middleware.RemoteUserMiddleware middleware in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3, when using the contrib.auth.backends.RemoteUserBackend backend, allows remote authenticated users to hijack web sessions via vectors relate...

CVE-2014-0483
Published: 2014-08-26
The administrative interface (contrib.admin) in Django before 1.4.14, 1.5.x before 1.5.9, 1.6.x before 1.6.6, and 1.7 before release candidate 3 does not check if a field represents a relationship between models, which allows remote authenticated users to obtain sensitive information via a to_field ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Three interviews on critical embedded systems and security, recorded at Black Hat 2014 in Las Vegas.