Document secure multi-person CoS intake via GitHub Issues - #7
Merged
Merged
Conversation
github-actions
Bot
added
the
documentation
cursor Bot
pushed a commit
that referenced
this pull request
Sep 16, 2026
Security-stamped model from PR #7 / COS_INTAKE: wake only on issue-assigned when the assigner is on the maintainer allowlist starting at cookieofcode. Assignees, label cos, and file/comment events do not wake. Issue bodies stay untrusted. Co-authored-by: Severin Pereto <cookieofcode@gmail.com>
Add a structured CoS request template, issue chooser link to private vulnerability reporting, SECURITY.md, and EaC notes that public issues are an untrusted community queue. CoS wakes only when a maintainer applies the cos label and assigns the issue. Co-authored-by: Severin Pereto <cookieofcode@gmail.com>
Correct the wake model: CoS fires only on issue-assigned when the assigner is cookieofcode (allowlist start). Assignees and label cos do not wake. Document routine torqvoice-cos-issue-triage, add CONTRIBUTING plus chooser warning, and state no plan/apply from untrusted issue text. Templates now ban secrets, Azure IDs, PII, kubeconfigs, and tfvars, and warn that screenshots can disclose workshop customer data. Co-authored-by: Severin Pereto <cookieofcode@gmail.com>
Keep contact_links. Note that Private vulnerability reporting is a product-owner GitHub settings step, not IaC. Co-authored-by: Severin Pereto <cookieofcode@gmail.com>
Reporters open a public Security contact request with zero vuln detail and mention cookieofcode. Maintainers create a draft Repository Security Advisory (no PVR toggle). Chooser CTA no longer points at /security/advisories/new. blank_issues_enabled is false. Co-authored-by: Severin Pereto <cookieofcode@gmail.com>
cursor
Bot
force-pushed
the
cursor/cos-issue-intake-d189
branch
from
September 16, 2026 07:38
08bb628 to
ab796ef
Compare
cookieofcode
marked this pull request as ready for review
September 16, 2026 07:52
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
2 participants
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.
Summary
Document how this public OSS repo takes product/bug/docs work through GitHub Issues for Chief of Staff triage, without treating issues as an ops or apply channel.
Folds Security PASS required and should-fix items, without depending on GitHub Private vulnerability reporting:
SECURITY.mdreporter path: public issue titledSecurity contact request, @mentioncookieofcode, zero vuln detail / PoC / secrets / screenshots of the bug. Maintainer path: create a draft Repository Security Advisory (admins can do this without a PVR toggle), invite the reporter or agree a private channel. No invented email. Optional later: a real address only if the product owner publishes one.SECURITY.md/ Security contact request (not/security/advisories/new).torqvoice-cos-issue-triagefires only onissue-assignedwhen the assigner is on the maintainer allowlist (start:cookieofcode). Assignees alone do not wake. Labelcosis human process only.terraform plan/ apply (or other provision) from issue text.CONTRIBUTING.mdplus issue chooser contact “Do not post secrets here” before submit; screenshot fields warn that workshop customer data in images is still disclosure..github/ISSUE_TEMPLATE/config.ymlsetsblank_issues_enabled: falseso submitters cannot skip templated warnings (contact_linkskept). Chooser security CTA is the Security contact request template, not PVR.No app code changes. No post-merge “enable PVR” ops step.
Why
Multi-person CoS intake on a public repository needs an explicit, safe path: structured requests, a contact-only security issue (no self-serve PVR), and a wake signal that cannot be forged by labeling or by becoming the assignee.