@@ -32,4 +32,16 @@ These are very short (1-2 weeks) and start with the identification of a relevant
[Atomic Testing](atomic-testing.md) is our first long-term Purple Team collaboration, enabling the easy re-run of these TTPs, much like unit tests do.
## Requesting a Purple Team Exercise
If you're another team within GitLab and have a Purple Team scenario you'd like us to work through, you can open an issue in our [Internal Issue Tracker](https://gitlab.com/gitlab-com/gl-security/security-operations/redteam/redteam-internal/red-team-operations/-/issues/new?description_template=purple-01-request-for-purple-team). Use the issue template called `purple-01-request-for-purple-team`, which will guide you through providing all the information we need to help.
Once you open the issue, the Red Team will review your request and ask follow-up questions as needed. When we have available capacity, we'll promote the issue to an Epic where all our work on the exercise will take place and assign it to the appropriate Milestone, allowing you to see progress in real-time.
The Red Team plans our operational load on a quarterly basis, so we'll need to weigh Purple Team requests against other ongoing initiatives. However, our goal is to satisfy external Purple Team requests as often as possible.
If your request is particularly time-sensitive, be sure to include that in the issue. You can also ping us in #security-help in Slack if you need our attention immediately.
## Additional Resources
See also [Red Team Resources](../_index.md#additional-resourcesfurther-reading)
