Lines Matching full:security

3 Security Vulnerability Reporting
11 acknowledged and analyzed by the security response team within 1 week.
12 Each vulnerability will be entered into the Zephyr Project security
16 .. _GitHub: https://github.com/zephyrproject-rtos/zephyr/security
18 Security Issue Management
78 The security advisories created are kept private, due to the
79 sensitive nature of security reports.  The issues are only visible to
86 - others, as proposed and ratified by the Zephyr Security
94 The Zephyr Security Subcommittee shall review the reported
106 Security sensitive vulnerabilities shall be made public after an
120 The security subcommittee will maintain information mapping embargoed
121 CVEs to these PRs (this information is within the Github security
122 advisories), and produce regular reports of the state of security
125 Each issue that is considered a security vulnerability shall be
146 legitimate interest in knowing about security vulnerabilities during
151 Periodically, the security subcommittee will send information to this
159 - The Zephyr Project security advisory link (GitHub).
174 Backporting of Security Vulnerabilities
177 Each security issue fixed within zephyr shall be backported to the
194 Backports will be tracked on the security advisory.
199 Due to the sensitive nature of security vulnerabilities, it is
202 security vulnerabilities before the embargo period ends:
210 - The Project Security Incident Response (PSIRT) team will have full
216   additional security meetings to discuss vulnerabilities.