Blog Post: How the GitLab Red Team Automates C2 Testing and Automation
Triage (REQUIRED)
Please note that there is a different process for when you want to announce something via the blog. Please see announcement requests in the handbook and open an announcement request issue instead of a blog post issue.
Proposal
This blog post is a technical description of how the GitLab Red Team performs testing and automation (with GitLab) for some common red team tasks. I've written a first draft which is currently only available internally. It's almost ready to be moved to a public MR, it just needs one more set of reviews.
At that point, I'll move it to a public MR and would love help getting it ready to go. This is my first blog proposal, so I'm open to any and all feedback so I can improve my work.
Thanks!
Checklist
-
Does this align with a time-sensitive release, campaign or announcement? Please add link to pertinent info such as eBook landing page -
If wide-spread customer impacting or sensitive, mention @lboughner
to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue -
If the post is about one of GitLab's Technology Partners, including integration partners, mention @pattycheung
and@nbadiey
, apply the Partner Marketing label, and see the blog handbook for more on third-party posts -
If the post is about one of GitLab's customers, mention @nicolecsmith
, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts -
Indicate if this post requires additional approval from internal or external parties before publishing (please tag needed sign off DRIs as necessary) -
Please upload any images to the MR before tagging the editorial team.
Questions?
-
Please tag @Sgittlen with any questions/concerns/confusion.