INFOGRAPHIC: Is your WMS working as hard as you are?
Many warehouse managers today feel that the most mistakes come from things such as stocke replenishment, picking and inventory control. These are issues that can potential be made more efficient by having an effective warehouse management system.
Here is some valuable advice from Eric Carter, Solutions Architect at Indigo on what to consider when choosing the right warehouse management system for your business needs. Below this there is also an extremely usefule infographic.
- The most important criteria is to consider the suitability of the software in terms of feature rich complexity versus perfect match for business requirements.
- Don't overcomplicate processes so that you end up with a highly complex software system with functionality you pay for but never take advantage of.
- Bear in mind that businesses change so fast that old thinking like 'get a system for the next ten years' really has little or no value in the real world.
- When conducting return on investment calculations (ROI) a practical sensible head is required. You need to make sure that the projected ROI is tangible and can be achieved.
- Operators need to conduct a true business process review which identifies no value-add processes and then potentially streamlines them to make sure the overall procedure is not affected and runs as efficiently as possible.
- Operators also need to realise that it is not just the software itself that provides the complete solution - getting the implementation project right itself is just as important.
For more guidance on choosing the best warehouse management system for you, get in touch with Indigo.
INFOGRAPHIC: Is your WMS working as hard as you are? http://www.indigo.co.uk/article/2015/7/14/is-your-wms-working-as-hard-as-you-are
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”’.