New Orleans Cold Storage Warehouse Marks Katrina Recovery
The oldest cold-storage company in North America, New Orleans Cold Storage, opened a 142,000 square-foot warehouse in the Port of New Orleans, Louisiana, Thursday. Affected like many New Orleans businesses by Hurricane Katrina, NOCS President and CEO Mark Blanchard says the expansion is a sign of new growth after a long road of recovery.
"The storm and subsequent closing of the Mississippi River-Gulf Outlet made it uncertain whether we could keep operations in New Orleans open," Blanchard said. More than 30 million pounds of chicken rotted in the New Orleans Jourdan Road warehouse during Katrina. Blanchard references the State of Louisiana and The Port of New Orleans as a giant help in the expansion of the new terminal at the Henry Clay Street Wharf. The $40 million terminal was built in part with the help of a $23.5 million grant from Louisiana's Disaster Recovery Program. The remainder of the $40 million project was paid by the Port of New Orleans, which owns the terminal.
The new facility will house 38 million pounds of perishable products - NOCS is one of the largest suppliers of beef, pork and poultry - and freeze up to 1.25 million pounds of fresh product each day. Constructed with green standards in mind, the buliding has technology to increase efficiency and energy savings, including LED lighting. Other features in the new storage facillity include containers for transfer directly to the Port of New Orleans container terminal for transport. The proximity of the Clay WHarf facility will improve efficiency with shipping.
The NOCS currently owns four facilities wiht more than 12 million square-feet of space in New Orleans, Houston and Charleston, S.C. New Orleans is happy to see the recovery of NOCS as well, according to Louisiana Department of Agriculture and Forestry Commissioner Mike Strain.
"From an economic standpoint, this provides jobs to our residents working at the storage facility, keeps our poultry industry valued at more than $1.6 billion and it benefits our ports," Strain said.
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”’.