May 17, 2020

DHL announces €40 million investment in Indonesia

DHL
Indonesia
investment
Warehouse
Freddie Pierce
2 min
The investment was announced at DHL's new warehouse launch
DHL Supply Chain has announced an investment of €40 million in its Indonesian operations over the next few years, following the launch of its late...

DHL Supply Chain has announced an investment of €40 million in its Indonesian operations over the next few years, following the launch of its latest 17,000 sqm warehouse in Cimanggus.

The company plans to increase its transportation fleet by over 100 percent, up from its current fleet of 370 vehicles at present. In addition, the company plans to grow its current staff complement of over 2000 employees by over 70 percent and add 60 percent more warehouse space to its 164 warehouses in the country.

Oscar de Bok, DHL Supply Chain CEO for South and Southeast Asia said, “Indonesia is a key focus for us. Industry experts estimate average growth this year in Indonesia will be a regional high of 6.3%¹ and within the supply chain industry we actually expect to see double digit growth here. This is why we are proactively investing to ensure we have the right infrastructure and people to support this.”

New multi-user warehouse

DHL Supply Chain unveiled the first of these investments last week, a new 17,000 square meter warehouse located in Cimanggis, which includes specialty features tailored for customers in the fast-moving consumer goods (FMCG) industry.

 The facility consolidates and stores shipments, then re-distributes to 300 distribution channels and four factories in the area. The warehouse has enough docks to accommodate 176 containers per day or 64,240 per year. Its strategic location enables faster delivery within the Jakarta area and also provides easy access to key export departure points.

The latest warehouse complements DHL Supply Chain’s offering of other specialist warehouses in the Jabodetabek area which support customers in automotive, retail, and the high-technology sectors. The Cimanggis warehouse is the third BTS warehouse by DHL, after the ones at Cikarang and Cililitan.

Abdul Rahim Tahir, Managing Director, DHL Supply Chain Indonesia said “Part of our strategy to strengthen customer footprint in Indonesia is to continue to expand our services in the rapidly growing industries in Indonesia, such as the consumer, retail, automotive, energy and technology sectors. We have developed core expertise in these areas in our global network and have replicated these best practices for local execution.”

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