docs: add a security policy - #68
Merged
Merged
Conversation
Lead with the outcome ("not 400 findings") rather than the mechanism, and
close the intro on the follow-up conversation instead of restating it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Route vulnerability reports to security@argusappsec.com (or GitHub private vulnerability reporting) instead of the public issue tracker, and link it from the README. Scope is defined against the trust boundaries already recorded in the ADRs rather than as a generic list, since "what counts as a vulnerability in an agent that reads untrusted code" is not self-evident: exfiltration of SOUL/MEMORY/CONTEXT past grounding (ADR 0017), knowledge-base poisoning (ADR 0018), escaping the checkout (ADR 0019), role and webhook bypass (ADR 0002), and reaching command execution (ADR 0006). Review quality, upstream scanner CVEs, and anything already requiring Admin or host access (ADR 0007) are out of scope, with the exception that a bad default is ours. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 root
SECURITY.mdso vulnerability reports reachsecurity@argusappsec.com (or GitHub private vulnerability reporting) instead
of the public issue tracker. GitHub picks the file up from the repo root for
the Security tab and the "Report a vulnerability" flow. Linked from the README.
Scope is anchored to the ADRs
"What counts as a vulnerability in an agent that reads untrusted code and
writes into places other people read" is not self-evident, so the policy
defines it as crossing a trust boundary we already recorded rather than as a
generic checklist:
Severity on exfiltration scales with the audience (public repo = the internet,
private repo = your contributors), but the boundary holds either way: whoever
can open a PR is not automatically cleared for everything in the org knowledge.
Out of scope
Review quality (false positives, missed findings) is a methodology bug, not a
vulnerability. Upstream scanner and dependency CVEs go upstream, unless we pin
a known-exploitable version. Anything already requiring an Admin principal or
host access is trusted by design (ADR 0007). One deliberate exception: a bad
default is in scope even though misconfiguration isn't.
Also states a 90-day coordinated-disclosure window, credit for reporters, no
bug bounty, and safe harbour for good-faith research.
Note
The second commit is the pending README tagline copy-edit that was already in
the working tree, kept separate from the policy commit.
Private vulnerability reporting needs enabling under Settings -> Code security
before the advisory link resolves.