From 218f1a5ecadd92b88a0d2dbde77790bb0feb45f4 Mon Sep 17 00:00:00 2001 From: Matteo Meucci Date: Tue, 17 Jun 2025 14:58:57 +0200 Subject: [PATCH] Update 2.0_Threat_Modeling_for_AI_Systems.md --- Document/content/2.0_Threat_Modeling_for_AI_Systems.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Document/content/2.0_Threat_Modeling_for_AI_Systems.md b/Document/content/2.0_Threat_Modeling_for_AI_Systems.md index fedba01..93ec54d 100644 --- a/Document/content/2.0_Threat_Modeling_for_AI_Systems.md +++ b/Document/content/2.0_Threat_Modeling_for_AI_Systems.md @@ -33,7 +33,7 @@ It’s important to map threats to a comprehensive AI architecture. (*) As threa In Stage II of PASTA, we define the architectural scope by aligning it with the Secure AI Framework (SAIF) [12], establishing a structured view of the AI system’s core security-relevant components. SAIF serves as a publicly available model for securing AI systems at scale, offering a practical, adaptable, and business-aligned framework that connects AI system security with broader risk management and operational resilience objectives. Specifically, the SAIF Risk Map [13] serves as a visual guide for navigating AI security and is central to understanding SAIF as a comprehensive security framework. It highlights many risks that may be unfamiliar to developers, such as prompt injection, data poisoning, and rogue actions. By mapping the AI development process, the SAIF Map helps identify where these risks emerge and, critically, where corresponding security controls can be applied. In Fig 1.1. we provide the visual of the SAIF components.

- Description + Description

**Fig 1.1 SAIF Architecture Layers & Components**