Skip to content

Commit bbe6c58

Browse files
authored
Fix dependency policy and add to SECURITY-INSIGHTS.yml (#4907)
## Description of the changes Adding security policy to SECURITY.md Adding a couple of sections to the SECURITY-INSIGHTS.yml to fix missing items. Next step is to check the CLOMonitor for other gaps - Need to build a threat model too. ## How was this change tested? Only text changes in this PR. ## Checklist - [X] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [X] I have signed all commits - [Not needed] I have added unit tests for the new functionality - [Not needed] I have run lint and test steps successfully --------- Signed-off-by: Jonah Kowall <[email protected]>
1 parent 86a1fc3 commit bbe6c58

File tree

4 files changed

+55
-2
lines changed

4 files changed

+55
-2
lines changed

SECURITY-INSIGHTS.yml

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,13 @@ distribution-points:
2626
- https://quay.io/organization/jaegertracing/
2727
security-artifacts:
2828
threat-model:
29-
threat-model-created: false
29+
threat-model-created: true
30+
evidence-url:
31+
- https://github.com/jaegertracing/jaeger/blob/main/THREAT-MODEL.md
32+
self-assessment:
33+
self-assessment-created: true
34+
evidence-url:
35+
- https://github.com/jaegertracing/jaeger/blob/main/SELF-ASSESMENT.md
3036
security-testing:
3137
- tool-type: sca
3238
tool-name: Dependabot
@@ -47,7 +53,12 @@ vulnerability-reporting:
4753
comment: |
4854
The first and best way to report a vulnerability is by using private security issues in GitHub or opening an issue on Github. We are also available on the CNCF Slack in the jaeger channel.
4955
dependencies:
56+
third-party-packages: true
57+
dependencies-lists:
58+
- https://github.com/jaegertracing/jaeger/blob/main/go.mod
5059
sbom:
5160
- sbom-file: https://github.com/jaegertracing/jaeger/releases/latest/download/jaeger-SBOM.spdx.json
5261
sbom-format: SPDX
53-
sbom-url: https://github.com/anchore/sbom-action
62+
sbom-url: https://github.com/anchore/sbom-action
63+
dependencies-lifecycle:
64+
policy-url: https://github.com/jaegertracing/jaeger/blob/main/SECURITY.md#security-patch-policy

SECURITY.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,25 @@ The Jaeger project provides community support only for last minor version: bug f
66

77
Security fixes are given priority and might be enough to cause a new version to be released.
88

9+
### Security Patch Policy
10+
11+
CVEs in Jaeger code will be patched in the newest Jaeger releases.
12+
13+
### Dependencies Lifecycle Policy
14+
15+
Dependencies are evaluated before being introduced to ensure they:
16+
17+
1) are actively maintained
18+
2) are maintained by trustworthy maintainers
19+
3) are licensed in a way not to impact the Jaeger license based on [the CNCF license allowlist](https://github.com/cncf/foundation/blob/main/allowed-third-party-license-policy.md).
20+
21+
These evaluations vary from dependency to dependencies.
22+
23+
Dependencies are also scheduled for removal if the project has been deprecated or if the project is no longer maintained. Additionally based on license changes we replace dependencies as necessary.
24+
25+
CVEs in dependencies will be patched for all supported versions if the CVE is applicable and is assessed by Snyk to be
26+
of high or critical severity. Automation generates a new dependabot scan daily and alerts are addressed.
27+
928
## Reporting a Vulnerability
1029

1130
_The following is a copy of the [Report a security issue](https://www.jaegertracing.io/report-security-issue/) page from our website. The website's version has precedence in case of conflicts._

SELF-ASSESMENT.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# Jaeger Self-Assessment
2+
3+
This is a placeholder document for the Jaeger project self-assessment. More details of what this will turn into can be found in the [TAG-Security documented standards.](https://github.com/cncf/tag-security/blob/main/assessments/guide/self-assessment.md)
4+
5+
## Table of Contents
6+
7+
* [Metadata](#metadata)
8+
* [Security links](#security-links)
9+
* [Overview](#overview)
10+
* [Actors](#actors)
11+
* [Actions](#actions)
12+
* [Background](#background)
13+
* [Goals](#goals)
14+
* [Non-goals](#non-goals)
15+
* [Self-assessment use](#self-assessment-use)
16+
* [Security functions and features](#security-functions-and-features)
17+
* [Project compliance](#project-compliance)
18+
* [Secure development practices](#secure-development-practices)
19+
* [Security issue resolution](#security-issue-resolution)
20+
* [Appendix](#appendix)## Table of Contents

THREAT-MODEL.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# Jaeger Threat Model
2+
3+
This is a placeholder for the Jaeger Threat Model. This will be based on [OSSF standards](https://github.com/ossf/security-insights-spec/tree/main/docs/threat-model) and examples of existing threat models. This is a significant chunk of work for Jaeger due to the diversity and complexity of all the supported components in deployment.

0 commit comments

Comments
 (0)