Supply Chain – Infrastructure
Supply Chain and Provenance Supply Chain 4 mitigations Full text and sources
The pathway
What it is
Attackers compromise the technical environment in which an AI system is developed and operated: cloud services, development tools, and third-party software components. This gives them access to systems, data, and models.
Where mitigations take effect
0 of 2 available effect classes are covered by at least one mitigation you marked. For 3 effect classes the catalogue lists no mitigation here: Impact-limiting, Corrective, Restorative.
All mitigations for this threat
Tick what is already in place in your organisation. The selection stays in this view and is not stored.
-
Use trusted suppliers
Reason for the classification
Primarily a contracts and third-party management control: Selection, verifiable commitments, and audit or enforcement rights toward third parties enable the protective effect; complemented by binding workflows.
-
Infrastructure hardening
Reason for the classification
Primarily technical: Safe formats, restrictive defaults, or protective layers reduce unsafe execution paths and exploitable attack surface.
-
Supply chain security audits
Reason for the classification
Primarily a contracts and third-party management control: Contractual audit, information, and remediation rights enable control; binding audit workflows put those rights into practice.
-
Continuous monitoring of hosting environments
Reason for the classification
Primarily technical: Software or analytical tools systematically produce and evaluate measurements, deviations, or attack indicators; complemented by binding workflows.