Wiz Shares Strategies to Reduce Cloud Supply-Chain Risk

Summary
Wiz outlines software- and identity-based cloud supply-chain risks, citing excessive third-party permissions in its analysis of 1,500 AWS accounts, and recommends inventory, vendor review and least-privilege access.
Key points
- Cloud software supply-chain risks can involve third-party agents, AMIs, container images and Lambda functions, as well as provider-managed software such as that involved in OMIGOD.
- Wiz says approximately 60% of surveyed environments were affected by OMIGOD.
- In an analysis of 1,500 AWS accounts and 40 popular vendors, Wiz found only 4% of organizations had not granted permissions to third parties.
- Wiz found 82% of environments had at least one vendor with overly high permissions; 76% had a vendor with permissions allowing full control of the customer’s cloud.
- The article recommends maintaining a cloud asset inventory and visibility into effective third-party permissions.
- It also recommends reviewing vendors and required permissions before approval, then limiting vendor access to what is necessary and monitoring software assets for patching and security.
Article Details
- Defense Focus
- Reduce cloud supply-chain risk by maintaining software asset visibility and inventory, reviewing third-party vendors and permissions, and limiting vendor access to the minimum needed.
- Detection Methods
- Maintain an inventory of third-party software deployed in cloud environments.
- Assess effective permissions granted to third-party vendors and identify excessive privileges.
- Continuously analyze software assets to verify patch status and expected behavior.
- Review and approve vendors and their requested policies and permissions before onboarding.
- Data Sources
- Cloud asset inventories, including third-party agents on VMs, AMI images, container images, and Lambda functions.
- Cloud identity and effective-permission data for third-party vendors.
- Platforms
- Cloud environments
- AWS
- Defensive Actions
- Establish a cloud supply-chain risk management process covering software and identity risks.
- Review third-party vendors before adding them and validate their required policies and permissions.
- Continuously assess and patch third-party software assets.
- Restrict vendor permissions to the least access necessary for their function.
- Account for third-party software that may be present through the cloud provider, even when it was not intentionally deployed.
