4759da8819
In addition to having security vulnerability fixes reported within each release note page, consolidate all of them in a new vulnerabilities document. This gives us two advantages: 1. The vulnerabilities can easily be referenced in a single place, which is useful for someone trying to cross reference against CVE lists, and 2. It allows a release to be made with just CVE numbers when issues are under embargo, and the details can be added to this vulnerabilities page. The release notes will be locked to a tag, and updates will not be visible. Signed-off-by: David Brown <david.brown@linaro.org>
18 lines
336 B
ReStructuredText
18 lines
336 B
ReStructuredText
.. _security_section:
|
|
|
|
Security
|
|
########
|
|
|
|
These documents describe the requirements, processes, and developer guidelines
|
|
for ensuring security is addressed within the Zephyr project.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
:glob:
|
|
|
|
security-overview.rst
|
|
secure-coding.rst
|
|
sensor-threat.rst
|
|
hardening-tool.rst
|
|
vulnerabilities.rst
|