From 8dd9bd8ac3372a3f42cd85c626e912a117fdd8f2 Mon Sep 17 00:00:00 2001 From: Matteo Meucci Date: Thu, 13 Nov 2025 16:45:51 +0100 Subject: [PATCH] Update and rename 2.2_Appendix_A.md to 4.1_Appendix_A.md --- Document/content/{2.2_Appendix_A.md => 4.1_Appendix_A.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename Document/content/{2.2_Appendix_A.md => 4.1_Appendix_A.md} (97%) diff --git a/Document/content/2.2_Appendix_A.md b/Document/content/4.1_Appendix_A.md similarity index 97% rename from Document/content/2.2_Appendix_A.md rename to Document/content/4.1_Appendix_A.md index ce51492..46228f3 100644 --- a/Document/content/2.2_Appendix_A.md +++ b/Document/content/4.1_Appendix_A.md @@ -1,4 +1,4 @@ -## 2.2 Appendix A: Rationale for Selecting SAIF as the Architectural Scope for AI Threat Modeling +## 4.1 Appendix A: Rationale for Selecting SAIF as the Architectural Scope for AI Threat Modeling We chose to use Google’s SAIF as the architectural scope for our AI threat modeling because it provides a clear decomposition of the system into data, model, application, and infrastructure layers, enabling structured testing and security control alignment.