Added subdepartment to table. Added separate section for the report schema .

Why is this change being made?

Clarified page and added new draft section for DRI on report schema changes, which is a hot topic on the secure and threat management teams.

More details on the discussion that lead up to this change can be found here: https://docs.google.com/document/d/14PFFFPNdOml2rNPvnU-rBq4Oz41M9F3Z9krGiqj-H5c/edit

Author Checklist

• Correct MR template applied (e.g blog post)
• 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
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • 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 relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

For help with failing pipelines reach out in #mr-buddies in Slack

Reviewed the changes and are comfortable with them

• @david
• @derekferguson
• @lkerr
• @thiagocsf
• @matt_wilson
• @NicoleSchwartz
• @gonzoyumo
• @sethgitlab
• @stkerr
• @tmccaslin
• @tstadelhofer
• @twoodham
• @whaber