You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/workflows/build-artifact/ARTIFACT_INVENTORY.template
+29-30Lines changed: 29 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -5,64 +5,63 @@ The following tables provide information about the container images and Helm cha
5
5
* pre-pull container images
6
6
* deploy into an air-gapped Kubernetes cluster
7
7
8
-
**Note:** For more information about deploying in an air-gapped environment, refer to
8
+
**Note:** For more information about deploying in an air-gapped environment, refer to
9
9
[Configure SAS Viya Monitoring for Kubernetes for an Air-Gapped Environment](https://documentation.sas.com/?cdcId=obsrvcdc&cdcVersion=v_003&docsetId=obsrvdply&docsetTarget=n0auhd4hutsf7xn169hfvriysz4e.htm#n0grd8g2pkfglin12bzm3g1oik2p).
10
10
11
11
## Table 1. Container Images
12
12
13
13
This table provides the fully qualified container-image names for the components of SAS Viya Monitoring for Kubernetes.
14
-
These names use the following format:
14
+
These names use the following format:
15
15
registry/repository/image_name:version
16
16
17
17
| Subsystem| Component | Fully Qualified Container-Image Name (registry/repository/image_name:version)|
# SAS® Viya® Monitoring for Kubernetes Security Policy
2
+
3
+
The project maintainers and community contributors take security issues seriously. We appreciate efforts to disclose potential issues responsibly and will acknowledge viable contributions. To aid in the investigation of reported vulnerabilities, please follow the [reporting guidelines](#reporting-guidelines) outlined below.
4
+
5
+
## Scope of Security Reports
6
+
7
+
### In Scope
8
+
The following components are directly maintained by this project and should be reported through our security reporting process:
9
+
10
+
* Custom deployment scripts and automation code
11
+
* Project-specific configuration files and templates
12
+
* Custom Kubernetes manifests and Helm charts
13
+
* Project documentation and guidance
14
+
* Any other artifacts created and maintained specifically by the SAS Viya Monitoring for Kubernetes project
15
+
16
+
### Out of Scope
17
+
This project deploys and configures various third-party open-source monitoring tools. For a complete inventory of third-party components used by this project, please refer to [ARTIFACT_INVENTORY.md](ARTIFACT_INVENTORY.md).
18
+
19
+
Vulnerabilities in these underlying components should be reported to their respective projects. For example:
20
+
21
+
* Grafana - Report via [Grafana Security](https://github.com/grafana/grafana/security)
22
+
* Prometheus - Report via [Prometheus Security](https://github.com/prometheus/prometheus/security)
23
+
* OpenSearch - Report via [OpenSearch Security](https://github.com/opensearch-project/OpenSearch/security)
24
+
25
+
Vulnerabilities identified through container image scanning should be reported directly to the project that maintains the container image. For example, if a scan of the OpenSearch container image reveals vulnerabilities, these should be reported to the OpenSearch project, not to SAS Viya Monitoring for Kubernetes.
26
+
27
+
If you're unsure whether a vulnerability belongs to our project's code or an underlying component, please submit the report through our process and we will help direct it to the appropriate team.
28
+
29
+
## Reporting Guidelines
30
+
31
+
To report a suspected security issue that is in scope for this project, use GitHub's private vulnerability reporting:
32
+
33
+
1. Click the `Security` tab
34
+
2. Click the `Report a vulnerability` button
35
+
36
+
Please provide the following information with your security report:
37
+
38
+
* Your name and affiliation (if applicable)
39
+
* Version/build-date of the SAS Viya Monitoring for Kubernetes project
40
+
* Detailed description of the security issue
41
+
* Steps to reproduce the issue
42
+
* Impact of the vulnerability
43
+
* Any known public information about this vulnerability (e.g., related CVE, security advisory)
44
+
* Whether the vulnerability exists in the latest version
45
+
* Suggested fixes or mitigations (if any)
46
+
47
+
## Recognition
48
+
49
+
Contributors who responsibly disclose security vulnerabilities will be acknowledged in our release notes (unless they prefer to remain anonymous).
50
+
51
+
## Additional Information
52
+
53
+
For general questions about the project's security, please open a regular GitHub issue. Do not include sensitive security-related details in public issues.
54
+
55
+
Note: This security policy may be updated from time to time. Please refer to the latest version in the repository.
0 commit comments