All Collections
Control Tests
Test: Production Code Changes Restricted
Test: Production Code Changes Restricted

Drata pulls a list of all of the authorized users with access to merge code to the default branch of a code repository in version control.

Ashley Hyman avatar
Written by Ashley Hyman
Updated over a week ago

ASSOCIATED DRATA CONTROL

This test is part of the Production Code Changes Restricted control that ensures only authorized company personnel can push or make changes to production code.

WHAT TO DO IF A TEST FAILS

If Drata finds users, with merge access to the default branch of your version control system repositories, that are not authorized by the company in Drata the test will fail. With a failed test you will receive a list of unauthorized users that have merge access rights.

To remediate a failed test, you will need to review the users within your version control system and ensure that these are authorized within Drata to write to default branches. This can be done by either enabling the respective flag for the user within Drata, confirming that the user should have merge access to the default branch, or revoking the user's access in the version control system.

STEPS TO REMEDIATE

  1. Log in to Drata as an Admin

  2. Ensure that the appropriate IDP, Infrastructure, and Version Control providers are connected.

  3. For Version Control accounts that have access to merge into the default branch, toggle the 'merge into default branch' flag in the 'Manage Version Control Accounts' page.

Did this answer your question?