Jul 28, 2020

Tradeshift: Owning The Supply Chain Marketplace

Supplier Management
Jack Grimshaw
2 min
Tradeshift: Owning The Supply Chain Marketplace
Can the procurement process become more like the everyday purchasing experience? Tradeshift’s solutions are making that possible...

With increased control and compliance, Tradeshift is helping to make procurement more similar to the process of purchasing on private marketplaces. The Tradeshift Buy platform is bringing the procurement process into a modern, digital world, making it compatible with marketplaces of today.

With Tradeshift Go, another solution of the company’s, users are able to request, approve and make purchases whilst on the move. The solution, a virtual credit card, enables more efficient, quicker spend for supply chain leaders.

With modern, technologically-enabled, buying-experience tools, integrated into e-procurement solutions with ease, Tradeshift can elevate operations to the next level, in no time at all, creating supply chain networks ready to compete with the best.

The Tradeshift cloud solution for end-to-end supply chain management enables businesses to do things the way that they want. Company purchasing is fully controllable, no on-premise or legacy software is required, and cost efficiency is, again, accelerated to a new level.

Managing a procurement marketplace can be complex and difficult. By integrating and adopting the Tradeshift suite of solutions, this complexity can be significantly simplified. From products to services, a marketplace for employees to shop with ease can be created through the solutions.

With all content from suppliers in one place, private marketplaces full of goods and services beneficial to companies can be created. Employees can be directed towards purchasing the correct products and services from suppliers that have been contracted and approved. 

Discounts and improved pricing can also be achieved through a simplified, personalised marketplace, without approved vendors being more trustworthy and worth purchasing from. Access to public spot markets is also available, enabling the discovery of new suppliers, new opportunities for collaboration, and the ability to identify and qualify sources of supply.

Process cycle times can be reduced significantly through the suite of solutions. By improving order collaboration with suppliers, Tradeshift delivers the ability to become proactive when ordering or delivering, and when things change. Improved collaboration and validation can ensure that multiple purchasing documents will support any change order, with 2 and 3-way matching and contract compliance processes that work from up-to-date, accurate data sets.

Complete supplier adoption of the suite is key to gaining a competitive advantage in the market, with all technology, financial services, and third-party businesses allowed to take advantage of the benefits of the industry-leading adoption and engagement rates.

Share article

Jun 21, 2021

Google and NIST Address Supply Chain Cybersecurity

Elise Leise
3 min
The SolarWinds and Codecov cyberattacks reminded companies that software security poses a critical risk. How do we mitigate it?

As high-level supply chain attacks hit the news, Google and the U.S. National Institute of Standards and Technology (NIST) have both developed proposals for how to address software supply chain security. This isn’t a new field, unfortunately. Since supply chains are a critical part of business resilience, criminals have no qualms about targeting its software. That’s why identifying, assessing, and mitigating cyber supply chain risks (C-SCRM) is at the top of Google and NIST’s respective agendas. 


High-Profile Supply Chain Attacks 

According to Google, no comprehensive end-to-end framework exists to mitigate threats across the software supply chain. [Yet] ‘there is an urgent need for a solution in the face of the eye-opening, multi-billion-dollar attacks in recent months...some of which could have been prevented or made more difficult’. 


Here are several of the largest cybersecurity failures in recent months: 


  • SolarWinds. Alleged Russian hackers slipped malicious code into a routine software update, which they then used as a Trojan horse for a massive cyberattack. 
  • Codecov. Attackers used automation to collect credentials and raid ‘additional resources’, such as data from other software development vendors. 
  • Malicious attacks on open-source repositories. Out of 1,000 GitHub accounts, more than one in five contained at least one dependency confusion-related misconfiguration. 


As a result of these attacks and Biden’s recent cybersecurity mandate, NIST and Google took action. NIST held a 1,400-person workshop and published 150 papers worth of recommendations from Microsoft, Synopsys, The Linux Foundation, and other software experts; Google will work with popular source, build, and packaging platforms to help companies implement and excel at their SLSA framework


What Are Their Recommendations? 

Here’s a quick recap: NIST has grouped together recommendations to create federal standards; Google has developed an end-to-end framework called Supply Chain Levels for Software Artifacts (SLSA)—pronounced “Salsa”. Both address software procurement and security. 


Now, here’s the slightly more in-depth version: 


  • NIST. The organisation wants more ‘rigorous and predictable’ ways to secure critical software. They suggest that firms use vulnerability disclosure programmes (VDP) and software bills of materials (SBOM), consider simplifying their software and give at least one developer per project security training.
  • Google. The company thinks that SLSA will encompass the source-build-publish software workflow. Essentially, the four-level framework helps businesses make informed choices about the security of the software they use, with SLSA 4 representing an ideal end state. 


If this all sounds very abstract, consider the recent SolarWinds attack. The attacker compromised the build platform, installed an implant, and injected malicious behaviour during each build. According to Google, higher SLSA levels would have required stronger security controls for the build platform, making it more difficult for the attacker to succeed. 


How Do The Proposals Differ? 

As Brian Fox, the co-founder and CTO at Sonatype, sees it, NIST and Google have created proposals that complement each other. ‘The NIST [version] is focused on defining minimum requirements for software sold to the government’, he explained, while Google ‘goes [further] and proposes a specific model for scoring the supply chain. NIST is currently focused on the “what”. Google, along with other industry leaders, is grappling with the “how”’. 


Share article