Category Direction - Security Orchestration

1. You are here:
2. GitLab Direction
3. Product Stage Direction - Protect
4. Category Direction - Security Orchestration

Maintained by:

G

• Protect
  • Introduction and how you can help
  • Overview
    • Target Audience
  • Where we are Headed
    • What is our Vision (Long-term Roadmap)
    • What's Next & Why (Near-term Roadmap)
    • What is Not Planned Right Now
    • Maturity Plan
  • User success metrics
• Competitive Landscape
• Analyst Landscape

Protect

Introduction and how you can help

Thanks for visiting this category direction page on Security Orchestration in GitLab. This page belongs to the Container Security group of the Protect stage and is maintained by Sam White (swhite@gitlab.com).

This direction page is a work in progress, and everyone can contribute:

• Please comment and contribute in the linked issues and epics on this page. Sharing your feedback directly on GitLab.com is the best way to contribute to our strategy and vision.
• Please share feedback directly via email or on a video call. If you're a GitLab user and have direct knowledge of your need for container security, we'd especially love to hear from you.

Overview

Security Orchestration is an overlay category that provides policy and alert orchestration support for all the scanners and technologies used by GitLab's Secure and Protect stages. The goal is to provide a single, unified user experience that is consistent and intuitive.

Target Audience

1. Cameron (Compliance Manager)
2. Devon (DevOps Engineer)
3. Alex (Security Operations Engineer)
4. Delaney (Development Team Lead)

Where we are Headed

Although this category is new, our vision is broad. We plan to support both scan schedule and scan results policies for all of GitLab's scanners at the Instance, Group, and Project levels. In addition, we intend to add full support for two-step approvals and proper audit trails of any changes made. In the long-run, we intend to provide visibility into the impact (blast radius) a policy will have before it is deployed, add support for complex orchestration policies, and auto-suggest policies based on your unique environment and codebase.

Beyond policies, we also intend to add support for an Alert workflow that will allow users to be notified of events that require manual, human review to determine the next steps to take. This workflow will eventually support auto-suggested responses and recommended changes to policies to reduce false positives and automate responses whenever possible.

What is our Vision (Long-term Roadmap)

As this category is new, the long-term roadmap is still being defined.

What's Next & Why (Near-term Roadmap)

We are planning to start by adding support for managing DAST scan schedule policies at the project level. This initial work will allow us to build a framework that we can then extend to other scanners, and also extend to the group and instance levels.

What is Not Planned Right Now

To be determined

Maturity Plan

Planned to Minimal

User success metrics

We plan to measure the success of this category based on the total number of users that interact with the Policy and Alert pages in the GitLab UI.

Competitive Landscape

As this category is new, we are still completing our evaluation of the competitive landscape.

Analyst Landscape

As this category is new, we have not yet engaged analysts on this topic.