The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Organization-wide security vulnerability, policy, and compliance management
The Govern stage extends your existing operation's practices to help organizations manage their security vulnerabilities, project dependencies, and compliance policies to reduce overall risk. Govern enables teams to identify risks by providing them with a high degree of visibility into their projects' dependencies, security findings, and user activities. This visibility is then coupled with management tools to respond to those risks. Lastly, policies can be used to automate compliance and to help secure the software supply chain.
The Govern stage provides the capabilities necessary to meet security and compliance requirements for organizations at any scale, from one project to tens of thousands of projects. This includes the ability to manage policies centrally, at scale, and have them apply to projects across the organization.
The Govern Stage is made up of five groups:
The existing team members for the Govern Stage can be found in the links below:
Security teams need centralized management for their security and compliance workflows. Features such as compliance labels, security policies, and the vulnerability and dependency lists need to allow for centralized management that applies across all of an organization's projects.
Govern capabilities will ensure that compliance regulations are strictly followed in a way that they cannot be bypassed without the proper approvals. This includes providing the necessary tools to audit, monitor, and manage the compliance controls that are enforced.
Govern capabilities will serve as a connection point for a seamless workflow spanning across the DevOps lifecycle. By enabling collaboration between types of users, Govern can help solidify the advantages GitLab has to offer as a single application. For example, these areas might include the following:
Govern capabilities will be pre-configured with reasonable defaults out-of-the-box whenever possible. When not possible, they will be easy to configure either through code or through a guided UI workflow that is friendly to users without coding knowledge. Regardless of how the capabilities are configured, they will be stored as code for ease of management.
For example, GitLab's security policy editor supports editing policies in both a rule mode and in yaml mode.
Building on those themes, some specific capabilities that we envision developing over the next 3 years include the following:
Compliance
Security Policies
Threat Insights
In addition to these areas specific to our individual groups, we also plan to expand our use of ML and AI across all of the Govern features.
Over the next 12 months, the Govern stage is focused on addressing critical needs for security and compliance teams. Some of the key initiatives include the following:
In addition to adding new features, we plan to improve the reliability of our features by increasing our test coverage. We maintain a prioritized list of these testing priorities.
We also regularly perform UX research and also maintain a prioritized list of these UX research priorities.
Although we will likely address many of these areas in the future (as described above in our 3 year strategy), we are not planning to make progress on the following initiatives in the next 12 months:
The following metrics are used to evaluate the success of the Govern stage:
Note: We do not yet have a single metric to track the success of the Govern stage as a whole. This is being tracked in this issue.
GitLab identifies who our DevSecOps application is built for utilizing the following categorization. We list our view of who we will support when in priority order.
To capitalize on the opportunities listed above, the Govern Stage has features that make it useful to the following personas today.
As we execute our 3 year strategy, our medium term (1-2 year) goal is to provide a single DevSecOps application that enables SecOps to work collaboratively with DevOps and development to mitigate vulnerabilities in production environments.
Govern is focused on providing governance and compliance features that span across the DevOps lifecycle. Govern’s tiering strategy aligns with the GitLab approach of selecting the tier based on who cares most about the feature. Because Executives generally care most about governance features, it is expected that most Govern features will land in the Ultimate tier.
This tier is the primary way to increase broad adoption of the Govern stage, as well as encouraging community contributions and improving security across the entire GitLab user base.
As a general rule of thumb, features will fall in the Free tier when they meet one or more of the following criteria:
This tier is not a significant part of Govern's pricing strategy; however, a few features features that primarily appeal to Directors rather than Executives may fall into the Premium tier. One example of this is our audit event functionality that is available in this tier.
This tier is the primary focus for the Govern stage as most Govern features enable executives to ensure that their organization meets compliance requirements and maintains an acceptable security posture.
As a general rule of thumb, features will fall in the Ultimate tier when they meet one or more of the following criteria:
There are a few product categories that are critical for success here; each one is intended to represent what you might find as an entire product out in the market. We want our single application to solve the important problems solved by other tools in this space - if you see an opportunity where we can deliver a specific solution that would be enough for you to switch over to GitLab, please reach out to the PM for this stage and let us know.
Each of these categories has a designated level of maturity; you can read more about our category maturity model to help you decide which categories you want to start using and when.
GitLab user lifecycle management. Includes provisioning users and their attributes. Does not include user profile, groups, projects, or sharing. This category is at the "viable" level of maturity.
Priority: high • Documentation • Direction
Authentication through all points of GitLab - UI, CLI, API. Does not include authentication within other stages of GitLab (for example, job tokens ). Also includes what the individual/process has access to once they authenticate, determined by their role. This category is at the "complete" level of maturity.
Track important events for review and compliance such as who performed certain actions and the time they happened. This category is at the "viable" level of maturity.
Priority: high • Documentation • Direction
Provide customers with the tools and features necessary to manage their compliance programs. This category is at the "viable" level of maturity.
Priority: high • Documentation • Direction
Unified security policy management capabilities across all of GitLab's scanners and security technologies. Apply policies to enforce scans and to require security approvals when vulnerabilities are found. This category is at the "viable" level of maturity.
Priority: medium • Documentation • Direction
View, triage, trend, track, and resolve vulnerabilities detected in your applications. This category is at the "viable" level of maturity.
Priority: high • Documentation • Direction
Track dependencies detected in your applications. This category is at the "viable" level of maturity.
Priority: high • Documentation • Direction
Track dependencies detected in your applications. This category is at the "viable" level of maturity.
Priority: high • Documentation • Direction
Insider Threat identifies attacks and high risk behaviors by correlating different data sources and observing behavioral patterns
We want to prevent malicious activity from occurring within GitLab Instances.
Release Evidence includes all the assurances and evidence collection that are necessary for you to trust the changes you're delivering. This category is at the "minimal" level of maturity.
admin_vulnerability from developers UltimateThere are a number of other issues that we've identified as being interesting that we are potentially thinking about, but do not currently have planned by setting a milestone for delivery. Some are good ideas we want to do, but don't yet know when; some we may never get around to, some may be replaced by another idea, and some are just waiting for that right spark of inspiration to turn them into something special.
Remember that at GitLab, everyone can contribute! This is one of our fundamental values and something we truly believe in, so if you have feedback on any of these items you're more than welcome to jump into the discussion. Our vision and product are truly something we build together!
Last Reviewed: 2023-05-24
Last Updated: 2023-05-24