Skip to content

Add SECURITY.md vulnerability reporting policy#420

Open
kallal79 wants to merge 3 commits into
rubysec:masterfrom
kallal79:issue-309-security-policy-clean
Open

Add SECURITY.md vulnerability reporting policy#420
kallal79 wants to merge 3 commits into
rubysec:masterfrom
kallal79:issue-309-security-policy-clean

Conversation

@kallal79
Copy link
Copy Markdown
Contributor

@kallal79 kallal79 commented Apr 3, 2026

Implement issue #309 by adding a dedicated security policy for bundler-audit.

Changes:

  • Add SECURITY.md with private vulnerability reporting instructions.

  • Document email reporting channel and disclosure expectations.

  • Add spec/security_policy_spec.rb to verify policy file presence and core guidance.

This commit intentionally contains only security-policy related files.

Implement issue rubysec#309 by adding a dedicated security policy for bundler-audit.

Changes:

- Add SECURITY.md with private vulnerability reporting instructions.

- Document email reporting channel and disclosure expectations.

- Add spec/security_policy_spec.rb to verify policy file presence and core guidance.

This commit intentionally contains only security-policy related files.
Comment thread SECURITY.md Outdated

## Reporting A Vulnerability

- Email: postmodern.mod3@gmail.com
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I assume we need to change the email now. Any idea where to point now? @jasnow what about your contact?

Copy link
Copy Markdown
Member

@jasnow jasnow May 31, 2026

Choose a reason for hiding this comment

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

Opened this yesterday for security@rubysec.com:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'd like to propose that we use a contact address that is itself a resource with shared ownership (e.g., a private Google group where we can manage membership and permissions), presuming we gain control of gem publishing.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

resource with shared ownership (e.g., a private Google group where we can manage
membership and permissions), presuming we gain control of gem publishing.
My previous thoughts are in ISS #428 but I can support @flavorjones' approach too.

Comment thread spec/security_policy_spec.rb Outdated

it 'contains a security contact channel' do
expect(content).to include('postmodern.mod3@gmail.com')
expect(content).to include('security@rubysec.com')
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do you own the security@rubysec.com email? I don't.

Comment thread SECURITY.md Outdated
## Reporting A Vulnerability

- Email: postmodern.mod3@gmail.com
- Email: security@rubysec.com
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Do you own the security@rubysec.com email? I don't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Ready to Review Ready to Review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants