Document fleetdm/security repo in handbook - #51144
Merged
Merged
Conversation
Security report intake moved from fleetdm/confidential to the dedicated private fleetdm/security repo. Update the engineering security report process and add a note to levels of confidentiality, with direct links to the standardized security report issue form. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
fleet-release
approved these changes
Aug 13, 2026
fleet-release
previously approved these changes
Aug 13, 2026
lukeheath
commented
Aug 13, 2026
fleet-release
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fleet now tracks application security reports (vulnerabilities, pen test findings, responsible disclosures) in the dedicated private fleetdm/security repo instead of fleetdm/confidential, so security work can be shared with outside security consultants without exposing broader confidential matters (customers, people ops, finance).
This PR updates the handbook to match:
security-labeled issues are automatically added to the :help-security project, and states the boundary rule: customer-identifying context stays in fleetdm/confidential and is linked, never copied.🤖 Generated with Claude Code