Wal-Mart warehouse contractor sued for wage theft
Written BY: k.scarpati
Lots of attention has been paid to the Dukes v. Wal-Mart case, the largest class-action civil-rights lawsuit in American history that could affect 1.6 million women, but a smaller class-action lawsuit indirectly against a Wal-Mart warehouse is slowly getting more and more attention.
Eight workers have accused Schneider Logistics, a Wal-Mart contractor, and another firm of violating state and federal labor laws. The suit could involve hundreds of warehouse employees should it be certified class-action.
Schneider Logistics runs an Elwood, Ill. warehouse, which basically serves as a Mid-West Wal-Mart distribution center.
The eight workers allege the distribution company failed to follow through on a promise of a $10 hourly rate, a “piece rate” for each items shipped and bonuses for “team lifts” that involved heavy loads.
“I noticed after a couple of weeks that my checks didn’t match my hours,” worker Robert Hines said. “People are breaking their backs, trying to feed their families and be right.”
Hines also claimed he sometimes worked more than 50 hours per week and was shortchanged on overtime.
SEE OTHER TOP STORIES IN THE WDM CONTENT NETWORK
Hines and other workers marched on the warehouse earlier this year, hoping to resolve the issue short of a lawsuit, but they were encouraged to go to court by a local advocacy group, Warehouse Workers for Justice.
Wal-Mart was the world’s largest public corporation in 2010 by revenue and has distribution centers and warehouses in 39 states and Washington D.C., according to an online listing.
The case is Collins, et al. v. Schneider Logistics, et al., and will be heard at the Illinois Northern District Court.
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”’.