Skip to content

Remove Teampaper Snap

Adam Huss requested to merge adamhuss-master-patch-20576 into master

Why is this change being made?

Teampaper Snap is listed on the Tools/Tips handbook page, however it goes against our acceptable use policy "Given the potential sensitivity of the data contained in screenshot images, the use of tools that capture and share screenshots to hosted sites online is prohibited without the explicit approval of the Security and Legal Departments. Screenshots should be stored locally or within Google drive folders associated with your GitLab.com account. Access to these drives and files should be managed in accordance with our Access Control policy, and handled according to our Data Classification Policy. Tools such as Lightshot, where upload functionality cannot be disabled and could result in inadvertant uploads, should not be used." I searched through our Third Party Risk Review board as well as ZenGRC and was unable to find any ad-hoc or normal review for this app. A quick look at the site shows they are using AWS to house screenshots, links and information which means these screenshots are not stored locally or within G-Drive folders. This has not been reviewed by legal or Security and until that happens, should not be listed in our Handbook.

Author Checklist

  • Provided a concise title for the 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.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 in 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.
  • 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.
Edited by Peter Kaldis

Merge request reports