Skip to content

Update file hackerone-process.html.md to add precisions on 3rd party triage

Why is this change being made?

I think the handbook could benefit from those precisions on what is accepted on reports related to third party software. The precision existed on the HackerOne policy, but I believe it is beneficial to have those rules in the Handbook as well. Small discussion about this here: https://gitlab.slack.com/archives/CNZPN8BT3/p1674511006362909?thread_ts=1674506903.296539&cid=CNZPN8BT3

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports