blob: f172bf6d019b280349fde24f1bf66e4906a25aa5 [file] [log] [blame]
Anton Komlevf7a44042023-01-26 14:50:22 +00001########
Summer Qinabf66982021-04-06 17:22:15 +08002Security
Anton Komlevf7a44042023-01-26 14:50:22 +00003########
4
Summer Qinabf66982021-04-06 17:22:15 +08005.. toctree::
6 :maxdepth: 1
Summer Qinabf66982021-04-06 17:22:15 +08007
Anton Komlevf7a44042023-01-26 14:50:22 +00008 Threat Model <threat_models/index>
9 Security Advisories <security_advisories/index>
10
11Security Disclosures
12--------------------
13
Nicola Mazzucato0feca422024-09-18 16:40:49 +010014Trusted Firmware-M (TF-M) disclose all security vulnerabilities, or are advised
Anton Komlevf7a44042023-01-26 14:50:22 +000015about, that are relevant to TF-M. TF-M encourage responsible disclosure of
16vulnerabilities and try the best to inform users about all possible issues.
17
18The TF-M vulnerabilities are disclosed as Security Advisories, all of which are
Nicola Mazzucato0feca422024-09-18 16:40:49 +010019listed in the `Security Advisories`_ section.
Anton Komlevf7a44042023-01-26 14:50:22 +000020
21Found a Security Issue?
22-----------------------
23
24Although TF-M try to keep secure, it can only do so with the help of the
25community of developers and security researchers.
26
27.. warning::
28 If any security vulnerability was found, please **do not**
29 report it in the `issue tracker`_ or on the `mailing list`_. Instead, please
Anton Komlevbd4582c2024-04-04 15:37:43 +010030 follow the `Security incident process`_.
Anton Komlevf7a44042023-01-26 14:50:22 +000031
32One of the goals of this process is to ensure providers of products that use
33TF-M have a chance to consider the implications of the vulnerability and its
34remedy before it is made public. As such, please follow the disclosure plan
35outlined in the `Security Incident Process`_. TF-M do the best to respond and
36fix any issues quickly.
37
38Afterwards, write-up all the findings about the TF-M source code is highly
39encouraged.
40
41Attribution
42-----------
43
44TF-M values researchers and community members who report vulnerabilities and
45TF-M policy is to credit the contributor's name in the published security advisory.
46
Anton Komlevbd4582c2024-04-04 15:37:43 +010047.. _issue tracker: https://github.com/TrustedFirmware-M/trusted-firmware-m/issues
Awadhy Mohammed3ba2d062023-03-02 10:43:07 +000048.. _mailing list: https://lists.trustedfirmware.org/mailman3/lists/tf-m.lists.trustedfirmware.org/
Anton Komlevbd4582c2024-04-04 15:37:43 +010049.. _Security incident process: https://trusted-firmware-docs.readthedocs.io/en/latest/security_center/incident_handling_process.html
Nicola Mazzucato0feca422024-09-18 16:40:49 +010050.. _Security Advisories: https://trustedfirmware-m.readthedocs.io/en/latest/security/security_advisories/index.html
Anton Komlevbd4582c2024-04-04 15:37:43 +010051
Summer Qinabf66982021-04-06 17:22:15 +080052
53--------------
54
Nicola Mazzucato0feca422024-09-18 16:40:49 +010055*Copyright (c) 2020-2024, Arm Limited. All rights reserved.*