docs: add SECURITY.md disclosure policy#369
Open
Adiz4415 wants to merge 1 commit into
Open
Conversation
Adds a SECURITY.md at the repo root describing how to report security vulnerabilities (private channels: GitHub Private Vulnerability Reporting, GitHub Security Advisories, and a placeholder security@geevapp.com inbox), recognition timelines (5bd ack, 10bd triage, 90-day coordination), Safe Harbor, GitHub-side hardening checklist, and a high-impact surface map covering SEP-10 wallet challenge handling, JWT / NextAuth sessions, wallet signing, Prisma SQL injection paths, npm / pnpm supply chain, and Soroban contract surfaces. No code, schema, or production behavior changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a
SECURITY.mdat the repo root describing how to report security vulnerabilities responsibly and listing the high-impact surfaces we monitor.Reporting channels (in preference order):
security@geevapp.com(placeholder pending dedicated mailbox + PGP key)Timelines: 5 business days ack → 10 business days triage → 90-day coordinated disclosure (negotiable for complex issues).
Surfaces covered: SEP-10 challenge handling (replay protection, sequence hygiene, server-account isolation), JWT / NextAuth sessions, wallet signing (no server-side keys, no pre-built XDR), Prisma SQL injection paths (
$queryRawparameterized, Zod-validated input, escapedLIKEpatterns), npm / pnpm supply chain (--frozen-lockfile, audit, onlyBuiltDependencies), Soroban contract surfaces (admin gating, status one-way, re-entrancy, governance-flag auto-suspend).Safe Harbor clause + GitHub-side hardening checklist (Dependabot alerts, secret scanning + push protection, CodeQL).
No code, schema, or production behavior changes. Suggest a follow-up to enable Private Vulnerability Reporting, Dependabot, and Secret Scanning under repo Settings.