GitLab Cloud Access Security Broker (CASB) integration with Microsoft
Release notes
A large SaaS customer is actively onboarding their most important SaaS applications to Microsoft Defender for Cloud Apps CASB as part of their cloud security strategy. Customer has "been hounding Microsoft to create a connector for GitLab ever since they started using it. A new strategy at MS is to publish guidance so that vendors can create the connector themselves."
Creating a CASB connector for GitLab would be extremely valuable to this customer as it will help them gain centralized visibility and security controls they require for their SaaS tools. Having the connector for GitLab product would be valuable to other customers as well for the same reasons.
Problem to solve
As a cyber security architect, having the CASB connector in GitLab will create a centralized view and security control required for SaaS products in large enterprises.
Intended users
User experience goal
Users will be able to connect GitLab to MDCA CASB
Proposal
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
This 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.