Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
64 changes: 63 additions & 1 deletion security-guidelines/security-guidelines.md
Original file line number Diff line number Diff line change
@@ -1 +1,63 @@
# NeoNephos Security Guidelines
# NeoNephos Security Policy Template

This document provides a default security policy for NeoNephos Foundation projects. Each project organization should place a `SECURITY.md` file in its `.github` repository (or in individual repositories) based on this template.

Replace all `{{ PLACEHOLDER }}` values with your organization-specific details before publishing.

---

# {{ PROJECT_NAME }} Security Policy

The {{ PROJECT_NAME }} project takes the security of our software seriously, including all source code repositories managed through the [{{ ORG_NAME }}](https://github.com/{{ ORG_NAME }}) GitHub organization.

If you believe you have found a security vulnerability in any {{ ORG_NAME }} repository, please report it to us as described below.

## Reporting Security Issues

**Please do not report security vulnerabilities through public GitHub issues.**

Instead, please use one of the following channels:

- **GitHub Security Advisories** — navigate to the **Security** tab of the affected repository and select **"Report a vulnerability"** to privately report an advisory.
- **Email**: [{{ SECURITY_EMAIL }}](mailto:{{ SECURITY_EMAIL }})

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

- The repository name or URL
- Type of issue (buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of the source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any particular configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue

This information will help us triage your report more quickly.

## Preferred Languages

We prefer all communications to be in English.

## Disclosure Policy

We follow the principle of [Coordinated Vulnerability Disclosure](https://en.wikipedia.org/wiki/Coordinated_vulnerability_disclosure). We ask that you:

- Allow us a reasonable time to investigate and address the issue before making any information public.
- Make a good faith effort to avoid privacy violations, data destruction, and disruption of services.
- Do not exploit the vulnerability beyond what is necessary to verify it.

We commit to:

- Acknowledging receipt of your vulnerability report.
- Providing an estimated timeline for a fix.
- Notifying you when the vulnerability is resolved.

---

## Placeholders Reference

| Placeholder | Description | Example |
|---|---|---|
| `{{ PROJECT_NAME }}` | Human-readable project name | Platform Mesh |
| `{{ ORG_NAME }}` | GitHub organization name | platform-mesh |
| `{{ SECURITY_EMAIL }}` | Security contact email | platform-mesh-security@lists.neonephos.org |