Crane Worldwide & Asia's first carbon neutral development
This move is in line with the company’s purported global commitment to sustainability.
“We are very excited to move to our new Singapore office in the carbon neutral development,” said John Magee, President and Chief Executive Officer of Crane Worldwide.
“We have been providing high touch, high service for our customers in Singapore since we opened in 2008. This office will allow us to not only continue to do that, but also make an impact on the sustainability in Singapore.”
The carbon neutral development is sustainable with green features designed for efficiency in energy and water, with an estimated savings of 620,000 kWh and 2803 respectively.
Crane Worldwide employs an initiative called Crane Cares, which focuses on three distinct pathways for helping others: Green Worldwide, Give Worldwide and Live Well Worldwide.
“The Singapore office continues to challenge the norm through the opening of this office. All of Crane Worldwide’s stations are encouraged to find their own way to make the world a better place and the Singapore team has done that through this office,” added Magee.
The office will continue to be led by Paul Westropp, Crane Worldwide’s managing director of Singapore and Malaysia.
The new Singapore office is centrally located in eastern Singapore with ease of transportation and close proximity to the airport and cargo center. The office is located at 11 Tampines Concourse, Units 01-06 & 07, Singapore 528729.
About Crane Wordwide
Crane Worldwide Logistics is a relationship-based organization that has a firm belief in the personal touch with its customers. Crane Worldwide Logistics offers a number of services including Air and Ocean freight forwarding, trucking, customs brokerage, warehousing and logistics as well as supply chain consultancy.
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”’.