Skip to content

Commit 075ab42

Browse files
authored
Extend SECURITY.md with Arm Toolchain details (#424)
This extends the SECURITY.md inherited from the LLVM Project by adding details on how to report security issues for components not provided by LLVM Project. SECURITY.md file was added to the automerge ignore list in a separate PR.
1 parent 4a4077a commit 075ab42

File tree

1 file changed

+16
-5
lines changed

1 file changed

+16
-5
lines changed

SECURITY.md

Lines changed: 16 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
1-
# Reporting LLVM Security Issues
2-
3-
To report security issues in LLVM, please follow the steps outlined on the
4-
[LLVM Security Group](https://llvm.org/docs/Security.html#how-to-report-a-security-issue)
5-
page.
1+
# Reporting Arm Toolchain Security Issues
2+
3+
To report security issues in LLVM components of Arm Toolchain,
4+
please follow LLVM Project
5+
[security policy](https://github.com/llvm/llvm-project/blob/main/SECURITY.md).
6+
7+
To report security issues in any other components of Arm Toolchain,
8+
please use the _Report a vulnerability_ feature under the Security tab.
9+
10+
> Please refer to
11+
> [What is considered a security issue?](https://llvm.org/docs/Security.html#what-is-considered-a-security-issue)
12+
> in LLVM Project for an overview of which toolchain components are considered
13+
> security-sensitive.
14+
>
15+
> The `picolibc` and `newlib` standard C libraries are not part of the `llvm-project`,
16+
> however Arm Toolchain treats these in the same way as the `llvm-project` runtime libraries.

0 commit comments

Comments
 (0)