Skip to content

docs: add SECURITY.md vulnerability disclosure policy#87

Merged
remyluslosius merged 1 commit into
mainfrom
docs/security-policy
Jun 15, 2026
Merged

docs: add SECURITY.md vulnerability disclosure policy#87
remyluslosius merged 1 commit into
mainfrom
docs/security-policy

Conversation

@remyluslosius

Copy link
Copy Markdown
Contributor

What

Adds a SECURITY.md vulnerability disclosure policy at the repo root — the path GitHub surfaces in the Security tab. Closes the doc-level gap for CISA Secure by Design Pledge goal 5 (and advances goal 6).

Decisions (confirmed by founder)

  • Reporting channels: security@hanalyx.com (GPG-encryptable via KEYS) and GitHub private vulnerability reporting.
  • Acknowledgment SLA: within 3 business days.
  • CVE/CWE commitment: included — Hanalyx assigns CVE identifiers with CWE classification for confirmed Kensa vulnerabilities.

Also covers

Coordinated disclosure (90-day window), safe harbor for good-faith research, and explicit scope. Notable scope calls: the hosts an operator manages are out of scope (operator's systems, not a Kensa vuln), and the passwordless-sudo-only and air-gap/no-telemetry design decisions are intentional (report a path if you think one is exploitable).

Style

Written to docs/DEVELOPER_DOCUMENTATION_STYLE_GUIDE.md: sentence-case headings, active voice, second person for the reporter, "we" only for genuine team commitments, ISO 8601 dates, no "simply/just/please," evidence over assurances (links to KEYS and the install-guide verification steps). Self-checked clean for forbidden words and spaced em dashes.

⚠️ Operational prerequisites — NOT done by this PR

This PR is the policy. For it to be real, two things need a human:

  1. Stand up and monitor security@hanalyx.com. A VDP pointing at a dead inbox is worse than none.
  2. Enable GitHub private vulnerability reporting in repo Settings → Security → Private vulnerability reporting (the /security/advisories/new link 404s until then).

Also worth a careful read before merge: the safe-harbor and 90-day disclosure terms are real commitments — I drafted them to convention, but I'm not a lawyer; confirm they match Hanalyx's intent.

(The local docs/context/CISA_SECURE_BY_DESIGN_PLEDGE.md pledge map is updated to mark goal 5 addressed with these prerequisites pending — gitignored, not in this PR.)

🤖 Generated with Claude Code

Closes the doc-level gap for CISA Secure by Design Pledge goal 5
(vulnerability disclosure policy). Publishes a SECURITY.md at the repo
root — the path GitHub surfaces in the Security tab — covering:

- Reporting channels: security@hanalyx.com (GPG-encryptable via KEYS) +
  GitHub private vulnerability reporting.
- A 3-business-day acknowledgment commitment.
- Coordinated disclosure (90-day window), safe harbor for good-faith
  research, and in/out-of-scope definitions (notably: the hosts an
  operator manages are out of scope; the passwordless-sudo and
  air-gap design decisions are intentional).
- A CVE-with-CWE issuance commitment for confirmed Kensa vulnerabilities
  (advances pledge goal 6).

Written to docs/DEVELOPER_DOCUMENTATION_STYLE_GUIDE.md (sentence-case
headings, active voice, second person for the reporter, "we" only for
genuine team commitments, ISO 8601 dates, no "simply/just/please",
evidence over assurances — links to KEYS and the install-guide
verification steps).

Operational prerequisites NOT done by this commit (founder/ops action):
stand up and monitor security@hanalyx.com, and enable GitHub private
vulnerability reporting in repo Settings -> Security.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@remyluslosius remyluslosius merged commit 946cfed into main Jun 15, 2026
14 checks passed
@remyluslosius remyluslosius deleted the docs/security-policy branch June 15, 2026 04:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant