You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

SECURITY.md 2.4KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. <!--- https://www.eclipse.org/security/ --->
  2. _ISO 27005 defines vulnerability as:
  3. "A weakness of an asset or group of assets that can be exploited by one or more threats."_
  4. ## The Eclipse Security Team
  5. The Eclipse Security Team provides help and advice to Eclipse projects
  6. on vulnerability issues and is the first point of contact
  7. for handling security vulnerabilities.
  8. Members of the Security Team are committers on Eclipse Projects
  9. and members of the Eclipse Architecture Council.
  10. Contact the [Eclipse Security Team](mailto:security@eclipse.org).
  11. **Note that, as a matter of policy, the security team does not open attachments.**
  12. ## Reporting a Security Vulnerability
  13. Vulnerabilities can be reported either via email to the Eclipse Security Team
  14. or directly with a project via the Eclipse Foundation's Bugzilla instance.
  15. The general security mailing list address is security@eclipse.org.
  16. Members of the Eclipse Security Team will receive messages sent to this address.
  17. This address should be used only for reporting undisclosed vulnerabilities;
  18. regular issue reports and questions unrelated to vulnerabilities in Eclipse software
  19. will be ignored.
  20. Note that this email address is not encrypted.
  21. The community is also encouraged to report vulnerabilities using the
  22. [Eclipse Foundation's Bugzilla instance](https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Vulnerability%20Reports&keywords=security&groups=Security_Advisories).
  23. Note that you will require an Eclipse Foundation account to create an issue report,
  24. but by doing so you will be able to participate directly in the resolution of the issue.
  25. Issue reports related to vulnerabilities must be marked as "committers-only",
  26. either automatically by clicking the provided link, by the reporter,
  27. or by a committer during the triage process.
  28. Note that issues marked "committers-only" are visible to all Eclipse committers.
  29. By default, a "committers-only" issue is also accessible to the reporter
  30. and individuals explicitly indicated in the "cc" list.
  31. ## Disclosure
  32. Disclosure is initially limited to the reporter and all Eclipse Committers,
  33. but is expanded to include other individuals, and the general public.
  34. The timing and manner of disclosure is governed by the
  35. [Eclipse Security Policy](https://www.eclipse.org/security/policy.php).
  36. Publicly disclosed issues are listed on the
  37. [Disclosed Vulnerabilities Page](https://www.eclipse.org/security/known.php).