CEVA builds Iberian chemical presence
CEVA Logistics has expanded its services provided at its multiuser Ontigola hub in Toledo, building a 240 square metre specialist Chemical Storage Area.
The supply chain specialists built the new area in the Ontigola warehouse as part of its commitment to providing best in class services and give a more streamlined focus on customers. A team of specialised engineers built the area in compliance with all existing rules and requirements relating to the safe storage of chemical products and risk prevention in the workplace, and the completed area was approved by the relevant authorities.
The Chemical Storage Area is an independent fire fighting area, equipped with specialist fire-fighting equipment including sprinklers and manholes placed in every door to collect any possible spill of product.
“The building of the first Chemical Storage Area for CEVA in Iberia demonstrates our commitment to meet the needs of customers in this highly regulated market,” Marco Galbusera, CEVA’s Manager Director in Iberia said. “This investment will allow us to extend our relationships with our customers and will help us to keep growing our footprint in the logistics market.”
Strategically located south of Madrid, the Ontigola site is well connected by the N-IV road and the R4 highway, as well as the planned motorway to Valencia, an increasingly important import hub.
The center at Ontigola will make use of shared technologies, skills, space and transport, to deliver true value and considerable economies of scale to customers. In the current economy where cost effectiveness is critical for any supply chain, multi user sites offer synergies to meet the most complex needs of customers even in highly regulated and sophisticated markets, like the chemical industry.
Google and NIST Address Supply Chain Cybersecurity
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”’.