forked from zephyrproject-rtos/zephyr
-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
scripts: zephyr_module: Add URL, version to SPDX
Improve the SPDX with the current values: - URL: extracted from `git remote`. If more than one remote, URL is not set. - Version: extracted from `git rev-parse` (commit id). - PURL and CPE for Zephyr: generated from URL and version. For zephyr, the tag is extracted, if present, and replace the commit id for the version field. Since official modules does not have tags, tags are not yet extracted for modules. To track vulnerabilities from modules dependencies, a new SBOM, `modules-deps.spdx` was created. It contains the `external-references` provided by the modules. It allows to easily track vulnerabilities from these external dependencies. Signed-off-by: Thomas Gagneret <[email protected]> (cherry picked from commit 0d05318)
- Loading branch information
1 parent
1fd105b
commit 45bc34c
Showing
8 changed files
with
406 additions
and
79 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -569,6 +569,45 @@ Build files located in a ``MODULE_EXT_ROOT`` can be described as: | |
This allows control of the build inclusion to be described externally to the | ||
Zephyr module. | ||
|
||
.. _modules-vulnerability-monitoring: | ||
|
||
Vulnerability monitoring | ||
======================== | ||
|
||
The module description file :file:`zephyr/module.yml` can be used to improve vulnerability monitoring. | ||
|
||
If your module needs to track vulnerabilities using an external reference | ||
(e.g your module is forked from another repository), you can use the ``security`` section. | ||
It contains the field ``external-references`` that contains a list of references that needs to | ||
be monitored for your module. The supported formats are: | ||
|
||
- CPE (Common Platform Enumeration) | ||
- PURL (Package URL) | ||
|
||
.. code-block:: yaml | ||
security: | ||
external-references: | ||
- <module-related-cpe> | ||
- <an-other-module-related-cpe> | ||
- <module-related-purl> | ||
A real life example for `mbedTLS` module could look like this: | ||
|
||
.. code-block:: yaml | ||
security: | ||
external-references: | ||
- cpe:2.3:a:arm:mbed_tls:3.5.2:*:*:*:*:*:*:* | ||
- pkg:github/Mbed-TLS/[email protected] | ||
.. note:: | ||
CPE field must follow the CPE 2.3 schema provided by `NVD | ||
<https://csrc.nist.gov/projects/security-content-automation-protocol/specifications/cpe>`_. | ||
PURL field must follow the PURL specification provided by `Github | ||
<https://github.com/package-url/purl-spec/blob/master/PURL-SPECIFICATION.rst>`_. | ||
|
||
|
||
Build system integration | ||
======================== | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.