Skip to main content
All CollectionsMonitoringTests
Test: MFA on Version Control System
Test: MFA on Version Control System

Drata connects to your companies' Version Control System and pulls all user accounts to determine if each has MFA enabled.

Updated over 3 months ago

ASSOCIATED DRATA CONTROL

This test is part of the MFA on Accounts control that ensures Multi-Factor Authentication (MFA) is being required for access to any sensitive systems or applications. Drata will verify that in order to log in to your version control tool a user needs to provide their ID, a password, and then either a One-Time Password (OTP) or certificate.

WHAT TO DO IF A TEST FAILS

If Drata finds that there are users in your version control tool that do not have MFA enabled the test will fail. With a failed test you will receive a list of users that do not have MFA enabled on their account.

STEPS FOR PASSING

To ensure a validated state when testing for MFA on the Version Control System, please follow the links below. In certain cases, the individual failing users will need to modify their account MFA implementation. Once each user has taken steps to modify their MFA settings, the next nightly user sync will pick up the changes and rerun the test to show the latest results.

AZURE DEVOPS REPOS

  • In order for Test 87 - MFA on Version Control System to pass for the Azure DevOps Repos connection, both of the following must be true:

    1. Microsoft 365 must be your connected IdP

    2. You must be enforcing MFA on Microsoft 365 via Conditional Access Policies or Security Defaults

HELPFUL RESOURCES

Did this answer your question?