Skip to content

Security page: say how a vulnerability report is handled - #2600

Merged
mjbraun merged 1 commit into
mainfrom
security-disclosure-section
Oct 23, 2026
Merged

mjbraun merged 1 commit into
mainfrom
security-disclosure-section

Conversation

@mjbraun

@mjbraun mjbraun commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

This page is the Policy URL in fly.io's security.txt, and vendor security programs read it to see whether reports get handled. It only said where to email. Now it says what to include, what not to do, a 3 business day acknowledgment, no bounty, no public credit, and asks for a fix window before publication.

Summary of changes

Preview

Related Fly.io community and GitHub links

Notes

This page is the Policy URL in fly.io's security.txt, and vendor security
programs read it to see whether reports get handled. It only said where
to email. Now it says what to include, what not to do, a 3 business day
acknowledgment, no bounty, no public credit, and asks for a fix window
before publication.
@mintlify

mintlify Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
fly-io 🟢 Ready View Preview Oct 23, 2026, 10:52 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@mjbraun
mjbraun merged commit bb565d0 into main Oct 23, 2026
2 checks passed
@mjbraun
mjbraun deleted the security-disclosure-section branch October 23, 2026 23:01

This branch was successfully deployed

1 active deployment
staging — e90ad711 Deployed Oct 23, 2026 by mintlify[bot]
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