Aug 5, 2020

Bext360: Start-Up in Sustainable Supply Chain Digitization

Supply Chain
Supplier Management
Emily Cook
2 min
supply chain startup supplier management utilising artificial intelligence blockchain technology to ensure sustainable ethical source
Bext360 utilises blockchain technology, machine vision and artificial intelligence to improve the global supply chain...

Founded in 2015 by Daniel Jones, Bext360 is a SaaS (software as a service) platform that provides traceability, authentication and sustainable intelligence. It offers a platform for every user and every step in the supply chain, from origin to consumer. Application Programming Interface allows for the platform to be integrated in websites, supply chain management systems and point-of-sale systems. 

What it does:

Bext360 is a startup that utilises machine vision and artificial intelligence. It locates and provides high-quality agricultural products, such as coffee, directly from the source. This creates transparency within the supply chain and encourages companies to be more honest about where they are sourcing their products. Bext360 then makes payments directly to farmers, communities, banks and other stakeholders and utilises blockchain technology where possible. Blockchain technology also creates an added layer of traceability and data storage. 

It’s system can then trace the products or services all the way to the consumer from the source, allowing the end consumer to directly interact with who provides the goods. This system then comes full circle, allowing the wholesalers and retailers to embed the technology into their own sites, marketing and supply chain management systems. 


Blockchain technology emerged in 2016 and allows data to be stored globally on thousands of servers, becoming a more efficient way to share information and data between businesses. It is difficult for just one person to control the network, making it more secure and hard to hack. 

Blockchain allows for real-time visibility, providing transparency and immutability therefore regaining trust and control to the supply chain. Blockchain is slowly being integrated into technology in the supply chain as it makes it more transparent and allows companies to regain trust from their customers if they can show directly where they are sourcing their products. 

Social Responsibility

Companies now have a responsibility to be more transparent with their suppliers and consumers. Consumers are demanding honesty from suppliers now more than ever. Bext360 is implemented worldwide and therefore can trace and receive data about dozens of suppliers.

It’s system greater increases business intelligence and provides a sustainability metric. These measure aspects of sustainability like environmental, social and economic and tracking the process of all three. More specifically, a sustainability metric can measure things such as; water and materials use, waste management and energy efficiency. With the data received using blockchain technology, Bext360 can measure and trace environmental damage caused by a particular process or service. 

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