May 17, 2020

Packaging Innovations two day seminar, February 26

Supply Chain Digital
Supply Chain
supply chain news
Logis
Freddie Pierce
2 min
Packaging Innovations
The two day seminar programme running throughout Packaging Innovations at the NEC on 26 & 27 February 2014, will also feature experts from Recoup...

The two day seminar programme running throughout Packaging Innovations at the NEC on 26 & 27 February 2014, will also feature experts from Recoup, Marks and Spencer, Wilkinson, Tesco, Asda and olive brand Oloves. These free to attend learnShops provide visitors with the latest thinking and developments, plus real-life examples of innovation in action that just might help their business or packaging idea evolve.

Paul Young, Head of Packaging Services at DHL Supply Chain, will open day one with ‘Packaging in 2050: A Scenario study’.  By using DHL commissioned research, Paul will divulge five visions of the most critical factors – including trade and consumption patterns, technological and social trends as well as climate change and an estimation of their probable impact on people’s behaviour and values in 2050.

Lars Wallentin, Founder of Packaging Sense, will be drawing upon his experiences after a 40-year career at Nestlé as head of packaging design, as he talks ‘Packaging Sense’ at the show. His learnShops session will take you on a 220 image trip from the very beginning of positioning through to the development of a concept and the execution of packaging design.

Retail giants will be out in force, Phil Huggett, Own Brand Packaging Manager at Wilkinson, will share his company’s insights into ‘How we made a million’ drawing on his experience in general merchandising and non-food packaging to explain what retailers want when commissioning packaging design and how to understand what the customer actually wants, as well as giving some common pitfalls to avoid.

Paul Earnshaw, Packaging Manager at Tesco, will provide ‘Tesco’s view of the packaging supply chain’. Correspondingly, Ian Schofield, Own Label Manager at Iceland Foods, will also cover the ‘Packaging Challenges for Retail’ and with online becoming a new driver, how packaging must change to reflect this trend. This key topic will also be discussed at this year’s BIG Packaging Debate, where a panel of packaging experts will form a lively Question Time style session. 

These independent seminars and case studies are selected to provide inspiration and practical guidance on packaging and print issues. To see the full learnShops line-up and to register for free entry to the exhibition visit www.easyFairs.com/PIUK

Visitor registration is free and now open via the Packaging Innovations website www.easyFairs.com/PIUK

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