xref: /arm-trusted-firmware/docs/threat_model/index.rst (revision 91f16700b400a8c0651d24a598fc48ee2997a0d7)
1*91f16700SchasingluluThreat Model
2*91f16700Schasinglulu============
3*91f16700Schasinglulu
4*91f16700SchasingluluThreat modeling is an important part of Secure Development Lifecycle (SDL)
5*91f16700Schasingluluthat helps us identify potential threats and mitigations affecting a system.
6*91f16700Schasinglulu
7*91f16700SchasingluluAs the TF-A codebase is highly configurable to allow tailoring it best for each
8*91f16700Schasingluluplatform's needs, providing a holistic threat model covering all of its features
9*91f16700Schasingluluis not necessarily the best approach. Instead, we provide a collection of
10*91f16700Schasingluludocuments which, together, form the project's threat model. These are
11*91f16700Schasingluluarticulated around a core document, called the :ref:`Generic Threat Model`,
12*91f16700Schasingluluwhich focuses on the most common configuration we expect to see. The other
13*91f16700Schasingluludocuments typically focus on specific features not covered in the core document.
14*91f16700Schasinglulu
15*91f16700SchasingluluAs the TF-A codebase evolves and new features get added, these threat model
16*91f16700Schasingluludocuments will be updated and extended in parallel to reflect at best the
17*91f16700Schasinglulucurrent status of the code from a security standpoint.
18*91f16700Schasinglulu
19*91f16700Schasinglulu   .. note::
20*91f16700Schasinglulu
21*91f16700Schasinglulu      Although our aim is eventually to provide threat model material for all
22*91f16700Schasinglulu      features within the project, we have not reached that point yet. We expect
23*91f16700Schasinglulu      to gradually fill these gaps over time.
24*91f16700Schasinglulu
25*91f16700SchasingluluEach of these documents give a description of the target of evaluation using a
26*91f16700Schasingluludata flow diagram, as well as a list of threats we have identified using the
27*91f16700Schasinglulu`STRIDE threat modeling technique`_ and corresponding mitigations.
28*91f16700Schasinglulu
29*91f16700Schasinglulu.. toctree::
30*91f16700Schasinglulu   :maxdepth: 1
31*91f16700Schasinglulu   :caption: Contents
32*91f16700Schasinglulu
33*91f16700Schasinglulu   threat_model
34*91f16700Schasinglulu   threat_model_el3_spm
35*91f16700Schasinglulu   threat_model_fvp_r
36*91f16700Schasinglulu   threat_model_rss_interface
37*91f16700Schasinglulu   threat_model_arm_cca
38*91f16700Schasinglulu
39*91f16700Schasinglulu--------------
40*91f16700Schasinglulu
41*91f16700Schasinglulu*Copyright (c) 2021-2023, Arm Limited and Contributors. All rights reserved.*
42*91f16700Schasinglulu
43*91f16700Schasinglulu.. _STRIDE threat modeling technique: https://docs.microsoft.com/en-us/azure/security/develop/threat-modeling-tool-threats#stride-model
44