Skip to content
ShatterpointSecurityPublic

About

Shatterpoint Security, organization profile

Security policy

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

16 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 

Repository files navigation

Security Policy

Reporting a vulnerability

ShatterPoint Security takes reports about its own code and sites seriously, and good faith reports are welcome.

  • Report privately. On the repository where you found the issue, use GitHub's private vulnerability reporting (the Security tab, "Report a vulnerability"). Please do not open a public issue for a vulnerability.
  • For the firm website, and for anything that does not live in a repository here, the contact in our security.txt is the route: https://shatterpointsecurity.github.io/.well-known/security.txt
  • Say what you found, where it is, and how to reproduce it. Reports with reproduction steps are verified fastest. That is the same evidence standard we hold our own published advisories to.

How reports are handled

Every report is read. Confirmed findings are fixed, and disclosure is coordinated with the reporter, who is credited where they wish to be. Our own research is published as advisories with deterministic reproduction steps, and reports made to us are measured by the same standard.

Scope

This policy covers the repositories under this organisation and the firm website. It does not authorise testing of GitHub's own infrastructure, of client systems, or of any third party system. Report platform issues to GitHub through its own programme.

About

Shatterpoint Security, organization profile

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors