Update SECURITY.md

[4og]

Eclipse Foundation has updated the secutity policy; therefore, we need to update it in S-CORE.

See https://www.eclipse.org/lists/eclipse.org-committers/msg01582.html

I modified the link for Github vulnerability reporting to point to the official how-to page, because this generic SECURITY.md gets applied to all S-CORE repositories, and the private reporting work per repository only.

[masc2023]

Did parallel the same, propose that here

Security Policy

This Eclipse Foundation Project adheres to the Eclipse Foundation Vulnerability Reporting Policy.

How To Report a Vulnerability

If you think you have found a vulnerability in this repository, please report it to us through coordinated disclosure.

Please do not report security vulnerabilities through public issues, discussions, or change requests.

Instead, report it using one of the following ways:

• Create a confidential issue in the Eclipse Foundation Vulnerability Reporting Tracker
• Report a vulnerability directly via private vulnerability reporting on GitHub

You can find more information about reporting and disclosure at the Eclipse Foundation Security page or
the {need}Platform Vulnerability Management Plan<doc__platform_vulnerability_mgt_plan>.

Please include as much of the information listed below as you can to help us better understand and resolve the issue:

• The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
• Affected version(s)
• Impact of the issue, including how an attacker might exploit the issue
• Step-by-step instructions to reproduce the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Full paths of source file(s) related to the manifestation of the issue
• Configuration required to reproduce the issue
• Log files that are related to this issue (if possible)
• Proof-of-concept or exploit code (if possible)

This information will help us triage your report more quickly.

Supported Versions

Supported versions are:

• Version 0.8

[4og]

The main question is do we want users to report all vulnerabilities via score repo or we allow to report to a repo where the issue is coccured?

[4og]

@masc2023, The https://eclipse-score.github.io/score/main/platform_management_plan/vulnerability_management.html also contradicts with this markdown. Here we write

Please do not report security vulnerabilities through public issues

but the management plan says:

GitHub issue tracking with appropriate labels (security, vulnerability) following S-CORE Problem Resolution process (Problem Resolution Plan (doc__platform_problem_resolution_plan))

[masc2023]

@masc2023, The https://eclipse-score.github.io/score/main/platform_management_plan/vulnerability_management.html also contradicts with this markdown. Here we write

Please do not report security vulnerabilities through public issues

but the management plan says:

GitHub issue tracking with appropriate labels (security, vulnerability) following S-CORE Problem Resolution process (Problem Resolution Plan (doc__platform_problem_resolution_plan))

It is tomorrow on the agenda of the process community to discuss, needs update. By the way vulnerabilities found during development, can just be resolved as stated, not need to file it.

[masc2023]

The main question is do we want users to report all vulnerabilities via score repo or we allow to report to a repo where the issue is coccured?

I would say both is possible, but may easier to report it just in S-CORE, if sub-folder are not known and easier from managing point of you, @anmittag may to be discussed next week in our community meeting

[4og]

By the way vulnerabilities found during development, can just be resolved as stated, not need to file it.

We should be careful with this. If it's a potentially exploitable vulnerability, it's better to avoid disclosing it publicly in a github issue before the fix is available and before the most affected users are informed and have a chance to update.