May 17, 2020

Toyota increases safety with new electric forklift

Materials Handling
Freddie Pierce
2 min
The 7FBMF, a member of the Traigo family
Toyota Forklifts has unveiled the latest addition to its range of electric forklifts, boasting a series of new features to enhance safety and producti...


Toyota Forklifts has unveiled the latest addition to its range of electric forklifts, boasting a series of new features to enhance safety and productivity.

The Traigo80 completes Toyota’s family of electric counterbalance forklifts, which include their 24v, 48v and HT ranges.

Offering a sneak peak of the new vehicle at last week’s IMHX, the Traigo80 is described as ‘robust, versatile and compact’, with capacities from 2.0 - 3.5 tonnes, including compact models. Equipped with the powerful and lean Toyota AC electric drive-and-lift technology and Toyota’s unique System of Active Stability (SAS) the truck is designed to be a reliable business asset and help customers’ drive down material handling costs.

According to Toyota, the entire Traigo family of trucks are all designed and built around the core values of productivity, safety, durability and driver comfort, to provide customers with trucks that add value to their business. This range provides solutions for any application and use, whether occasional or high intensity. Working indoors and outdoors, a wide range of cabins are available for improving comfort in all-weather operations.

In line with Toyota’s well-known principle of continuous improvement (Kaizen), the company claims its new Traigo80 takes leaps forward in many key areas; providing ‘improved productivity for users, maximum speed – paired with better energy efficiency – and superb all-around visibility’.  In addition, drivers can take advantage of clearer through-mast visibility in operations with a choice of masts to suit different application needs.

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