May 17, 2020

TGW prepares Danish logistics centre for peak season demand

European warehousing
Admin
2 min
TGW first installed an automated solution inside the distribution centre in Haderslev, Denmark
Automated logistics solutions provider TGW is extending the logistics centre of Bestseller, the Danish multi-label fashion retailer and one of Europes l...

Automated logistics solutions provider TGW is extending the logistics centre of Bestseller, the Danish multi-label fashion retailer and one of Europe’s largest clothing companies.

In 2009 TGW first installed an automated solution inside the distribution centre in Haderslev, Denmark, which enabled Bestseller to efficiently coordinate all of its European logistics activities from a single location. To accommodate a growing product range and to prepare for peak summer volumes, Bestseller is again optimising its on-site logistics processes.

The extension takes place in two phases. In spring, the never-out-of-stock (NOOS) area was extended in order to prepare for Bestseller’s peak season, which began in July. Here, TGW has installed four more of its Commissioner automated storage and retrieval (AS/R) machines to optimise the existing 12 machines.

In addition, the connection to the TGW PutStation has been modified to increase performance and essential algorithms in the warehouse management system have been upgraded according to changing wholesale and retail requirements.

In the second phase, Bestseller will extend its logistics centre once more, to be better prepared for an even greater annual high in July 2016. The existing installation will be expanded with a comprehensive conveying system alongside 17 additional aisles with 420,000 storage positions.

The expansion of the sorter and its controls will be particularly challenging. This will take place during the Easter weekend over 120 consecutive hours in order not to interrupt the running operation, with go-live scheduled for July 2016.

Share article

Jun 21, 2021

Google and NIST Address Supply Chain Cybersecurity

Google
NIST
SLSA4
Sonatype
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