Gitlab hero border pattern left svg Gitlab hero border pattern right svg

IAM.1.05 - Role Change: Access De-Provisioning Control Guidance

IAM.1.05 - Role Change: Access De-Provisioning

Control Statement

Upon notification of an reassignment or transfer, management reviews the GitLabber's access for appropriateness. Access that is no longer required is revoked and documented.

Context

The purpose of this control is to ensure there is a process in place to remove access to user accounts that is no longer necessary in the event of a role change. This control helps ensure that only authorized and active accounts can be accessed and used to prevent any unauthorized use or access of GitLab customer, GitLab teammember, and partner data. PeopleOperations would be responsible for advising of role change and new hiring manager of reviewing and de-provisioning any access that was no longer required.

Scope

This control applies to any system or service where user accounts can be provisioned.

Ownership

Additional control information and project tracking

Non-public information relating to this security control as well as links to the work associated with various phases of project work can be found in the Role Change: Access De-Provisioning control issue.

Policy Reference

Access Control Policy and Procedures

Framework Mapping