Skip to content

docs(readme): document the secure-404 cross-tenant pattern (#356)#357

Merged
CryptoJones merged 1 commit into
masterfrom
docs/readme-secure-404-pattern
May 19, 2026
Merged

docs(readme): document the secure-404 cross-tenant pattern (#356)#357
CryptoJones merged 1 commit into
masterfrom
docs/readme-secure-404-pattern

Conversation

@CryptoJones
Copy link
Copy Markdown
Owner

Closes #356.

Summary

Adds a "Secure-404 on cross-tenant access" subsection to the README's HTTP-conventions block. Documents that single-row GET/PATCH/DELETE endpoints collapse "exists but not yours" into 404 — same outcome an enumeration attacker sees for non-existent IDs.

Test plan

  • npm run lint && npm test — 794 passing (docs-only).

Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/

The codebase collapses "exists but not yours" into 404 across every
single-row GET / PATCH / DELETE endpoint so a scoped caller can't
enumerate another tenant's ID range by status code. The pattern
landed across 11 entities (#174, #188, #192, #196, #200, #204,
#210, #214, #218, #222, etc.) but the README never mentioned the
behavior — operators reading the doc table would reasonably
expect 403 on a cross-tenant probe and be surprised by 404.

Add a short subsection in the HTTP-conventions block that explains
the choice, links the behavior to the same getCompanyId scope
check used for 403 paths on other surfaces, and notes that master
keys still see all rows.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@CryptoJones CryptoJones merged commit 56b1e31 into master May 19, 2026
3 checks passed
@CryptoJones CryptoJones deleted the docs/readme-secure-404-pattern branch May 19, 2026 19:37
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.

README: secure-404 cross-tenant pattern is undocumented

1 participant