Skip to content

Add SECURITY.md and CODEOWNERS #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
koishore merged 1 commit into from
Jun 7, 2026
Merged

Add SECURITY.md and CODEOWNERS #4

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 3 additions & 0 deletions .github/CODEOWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# delego specification — the spec lead reviews all changes to the protocol.
# Enforced via branch protection (require review from Code Owners).
* @koishore
43 changes: 43 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
# Security Policy

This repository is the **specification** for delego — a deterministic
authorization & audit protocol for AI-agent actions. The security-relevant
artifact here is the *protocol itself*: a normative clause that permits an action
it should forbid is a vulnerability, even when an implementation follows it
faithfully.

## Reporting a vulnerability

**Please do not open a public issue for security vulnerabilities.**

Report privately via GitHub's
[private vulnerability reporting](https://github.com/Delego-Dev/specification/security/advisories/new),
or email **koishore@gmail.com**. Include the affected section of [`spec.md`](spec.md)
(or the conformance vector), why it weakens a guarantee, and a concrete scenario.
We aim to acknowledge within 72 hours.

## In scope

Weaknesses in the protocol as specified, for example:

- A normative rule whose plain reading authorizes an action the model should
deny — e.g. a gap in the **forbidden → rules → default** order, or a
fail-open constraint.
- A way for an approval bound to one action to release a *different* action — a
break in the confused-deputy / action-fingerprint binding as specified.
- An audit-chain construction the spec mandates that does **not** detect a class
of tampering it claims to (beyond the documented tail-truncation limit).
- A conformance vector in [`ctk/`](ctk/) that is wrong or contradicts the prose.

## Out of scope

- Bugs in a particular *implementation* — report those against that project
(e.g. the reference implementation,
[delego](https://github.com/Delego-Dev/delego/security)).
- Documented design boundaries (see the threat-model section of the spec); a
bypass *within* those boundaries is in scope.

## Supported versions

The spec is pre-1.0 and versioned in tiers (0.1 / 0.2 / 0.3-draft). Security
corrections target the latest published tier.
Loading