Skip to content

docs: clarify security boundaries - #4953

Open
sivajisj wants to merge 1 commit into
otter-sec:masterfrom
sivajisj:docs/clarify-security-boundaries
Open

docs: clarify security boundaries#4953
sivajisj wants to merge 1 commit into
otter-sec:masterfrom
sivajisj:docs/clarify-security-boundaries

Conversation

@sivajisj

Copy link
Copy Markdown

Summary

Clarifies the distinction between Anchor security boundaries and
defense-in-depth / anti-footgun protections in the security policy.

This makes it clearer which types of issues may represent a security
boundary violation and helps reporters determine the appropriate
reporting path.

Changes

  • Define what constitutes a security-boundary issue.
  • Identify examples of fundamental Anchor security properties.
  • Clarify that not every Anchor safety check represents a security boundary.
  • Explain how uncertain security reports should be handled.

Branch Target

This change is documentation-only and does not contain breaking changes,
so it targets the current master branch.

Closes #4857

@vercel

vercel Bot commented Aug 21, 2026

Copy link
Copy Markdown

@sivajisj is attempting to deploy a commit to the OtterSec Team on Vercel.

A member of the Team first needs to authorize it.

@sivajisj
sivajisj force-pushed the docs/clarify-security-boundaries branch from 7e1022c to a0c9996 Compare August 21, 2026 06:45
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.

tracking: Clarify security boundaries in our security policy

1 participant