silverstripe / silverstripe/developer-docs

Update security process regarding who gets acknowledgement for finding vulnerabilities

Open
#496 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type/docs
Dominant language
No language data
Stars
7
Forks
74
Avg merge
1d 14m
Merged PRs (30d)
6

Description

The [https://docs.silverstripe.org/en/5/contributing/managing_security_issues/](security issue/release process) mentions giving acknowledgement to the reporter - but in some scenarios the reporter isn't the correct person to acknowledge, necessarily.

Acceptance criteria

  • Doc is updated to reflect these scenarios:
    • The reporter is a digital agency or owner of a website who hired a third-party to perform a penetration test. The third party found a vulnerability.
      • In this case the agency and third-party should both be asked if they want to be given acknowledgement
    • The reporter is a staff member at Silverstripe, and they're reporting on behalf of a client who hired a third-party to perform a penetration test. The third party found a vulnerability.
      • In this case the client and third-party should both be asked if they want to be given acknowledgement

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the managing security issues page linked in the issue. Review the acknowledgement guidance and update it to cover agency or client reporters, Silverstripe staff reporting for a client, and third-party penetration testers. Done means both relevant parties are asked whether they want acknowledgement in each scenario.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.