Migrating from an ACF2 UID based security policy to a Role-Based Access Control (RBAC) security policy is a daunting task for any z/OS environment.

A UID string typically represents a person’s place in the corporate hierarchy along with their job function. The UID string method can encounter problems when a person has multiple roles or when job functions evolve or change.

Role Based Access Control (RBAC) is a standard architecture for defining security policy.

RBAC security policy definitions have the promise of being more structured and understandable, resolving some of the challenges related to UID strings.

This architecture is also consistent with the Role Identification in z/OS for ACF2 2 security policy methodology of Windows, Linux and UNIX. Due to these as well as other factors, we are seeing more regulatory pressure to migrate to RBAC.

Vanguard has developed a validation access capability that leverages an automated process to reduce errors and increase the accuracy of converting the UID String migration to Role-Based Access.

Vanguard Role-Based Conversion (VRBC) intelligently measures user access before and after the migration to ensure success without affecting operations.

• Budget Friendly while validating access and improving operational efficiency
• Provides a variety of clear and concise reports for operations, audit and security requirements
• Efficiently designed and written programs migrate UID to Role-Based Access structure
• Leverages decades of z/OS experience and Professional Services support as required