Skip to content

Add security.txt (RFC 9116) for vulnerability disclosure#85

Open
cassiocassio wants to merge 1 commit intomainfrom
security-txt
Open

Add security.txt (RFC 9116) for vulnerability disclosure#85
cassiocassio wants to merge 1 commit intomainfrom
security-txt

Conversation

@cassiocassio
Copy link
Copy Markdown
Owner

Summary

  • Adds /.well-known/security.txt per RFC 9116 so security researchers can find reporting instructions from bristlenose.app without locating the GitHub repo
  • Points to existing SECURITY.md policy and security@bristlenose.app
  • .htaccess redirect from /security.txt for older scanners
  • Expires 16 Oct 2026 (6-month review cycle, aligns with launch window)

Test plan

  • Deploy via /deploy-website
  • curl -sI https://bristlenose.app/.well-known/security.txt returns 200
  • curl -sI https://bristlenose.app/security.txt returns 301 → .well-known/security.txt

🤖 Generated with Claude Code

Copy link
Copy Markdown
Owner Author

@cassiocassio cassiocassio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ltm

Machine-readable disclosure file at /.well-known/security.txt so security
researchers hitting bristlenose.app can find reporting instructions without
needing to locate the GitHub repo. Points to existing SECURITY.md policy
and security@bristlenose.app. Expires 16 Oct 2026 (6-month review cycle).

Includes .htaccess redirect from /security.txt for older scanners.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
cassiocassio added a commit that referenced this pull request Apr 16, 2026
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.

1 participant