SCGP & Go-Pak: A Multinational Match Made in Modernity
Promising that it’s very much ‘business as usual’, has been acquired by (SCGP), the Thailand-based total packaging solution provider, and have maintained that their current management, operations, customers and identity will not change, s relief no doubt for the turbulent world of 2020.
SCGP, established in 1975, has been somewhat of a rising star across South East Asia, offering integrated packaging solutions with a variety of innovative products and services, ranging from smart packaging to waste paper purchase services.
Go-Pak, founded in 2009, is the UK’s fastest-growing privately-owned supplier of food and service packaging, offering an entirely compostable and biodegradable product range, as well as supporting big brands like Greggs, Starbucks and Pret A Manger, to name a few.
The acquisition comes as no surprise when you view the company’s capabilities alone, and the support they can provide each other, coupled with an expanded global reach and the shared vision of sustainability being the focus of future endeavours,
Simon Lawley, the founder of Go-Pak, noted on such a powerful union: “Go-Pak has found the perfect home in joining together with SCG Packaging. Go-Pak has achieved so much as an independently-owned business over the past 11 years. It has been a great journey so far, and our growth strategy and potential will continue to flourish as part of the SCG family. Not only does this make Go-Pak stronger, but it will also allow the business to maximise its full potential as part of SCG Packaging.”
Wichan Jiptukdee, CEO of SCGP, shared Lawley’s optimism: “We are extremely pleased to collaborate with Go-Pak, our new partner with whom we look forward to working together to grow in the European market as well as expand the business in the United States, as we plan to build upon this impressive platform and strong B2B2C focus. We welcome their knowledge, flexibility and creativity to our business.”
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”’.