Add SECURITY.md with a vulnerability disclosure policy - #121
Open
34zY wants to merge 1 commit into
Open
Conversation
Expanded the security policy to include detailed reporting procedures, response processes, and coordinated disclosure guidelines.
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.
Add SECURITY.md — vulnerability disclosure policy
What
Adds a
SECURITY.mdthat documents a private process for reporting securityvulnerabilities in this plugin.
Why
WP Simple SAML handles authentication (SAML SSO), so a clear, private channel
for security reports is valuable for both maintainers and users. This repo
currently has no
SECURITY.md. Beyond documentation, this also affectsGitHub's "Report a vulnerability" button: it appears reliably on the
Security tab once a security policy is present, so adding this file makes
private reporting easier to discover.
Notes for maintainers
Settings → Code security and analysis → Private vulnerability reporting.
hello@humanmade.com,shady@humanmade.com) aretaken from
composer.json/ README - please adjust to your preferredsecurity contact.
latest (master), since Ididn't see tagged releases. Please edit it to match y
Placement
Placed at the repository root; GitHub also recognizes `
you prefer to keep it there.