AI component SBOM and integrity verification

Control objective

AI component SBOM and integrity verification checks that every third-party building block of an AI system — models, libraries, embeddings, datasets, and tools — is inventoried in a Software Bill of Materials and cryptographically verified before use, so that no unsigned or tampered component can enter production; for a bank this guards against supply-chain attacks where a poisoned model weight or malicious dependency silently compromises a customer-facing agent. No quantitative metric or calcMethod is defined; the control is governed by its threshold conditions and verified through inventory and signature checks. Implement it by generating and maintaining a complete SBOM for all AI components, enforcing signature/hash verification in the build and deployment pipeline (a gate that rejects anything unsigned or with a failed checksum), and logging each component's source, version, signature status, and verification result. Re-verify on every update and re-deployment. The threshold requires 100% of third-party components to be in the SBOM and signature-verified, with 0 unsigned updates reaching production: any missing inventory entry or unsigned/unverified component is a breach that must block the deployment and trigger investigation, given the High priority of this supply-chain control.