What it asks for. The organisation must establish processes to identify and address weaknesses in the supply chain elements and processes for its systems, employ defined controls to protect against supply chain risks and document the selected controls.
In practice. This means a supply chain risk process that covers software, hardware and service providers, with controls such as approved supplier lists, contractual security requirements, software composition analysis and verification of updates. Auditors expect documented processes, the controls chosen and evidence they are applied. NIS2 explicitly requires supply chain security measures, and ISO/IEC 27001 supplier relationship controls cover related ground.
Common gaps. Supply chain risk is often treated as a procurement questionnaire with no technical controls. Open source dependencies are frequently left out of scope.