Join access requests to their fulfilment and review
Access Assurance Suite is an identity-governance and administration enquiry associated with Core Security. It connects access requests, approval, provisioning and review, but those stages need an agreed business policy. An automated connector should not decide entitlement merely because it can create an account.
Begin with authoritative identity information and the applications in scope. Map joiners, movers, leavers and contractors, including who approves each access change. Legacy Courion or Core terminology in an installed estate should be reconciled with the current product and component schedule before renewal or expansion.
Validate the lifecycle across supported applications
Confirm current suite modules, connectors and platform requirements. Choose a small application set for a pilot and test a complete request, approval and fulfilment cycle. Include denied access, a role change and removal of access when a user leaves. A directory status change is insufficient if the downstream account remains usable.
Review exceptions and reconciliation when an application is unavailable or a request cannot be fulfilled automatically. Handover should define roles, business ownership, connector configuration and the evidence retained for access review. Password-management or other optional functions should be identified in the entitlement list rather than assumed. Continuing application onboarding and identity administration require named owners after the project closes.
Evidence to request for this scope
- Identify authoritative identity attributes, application owners and approval roles.
- Confirm current modules and connector support for every initial target.
- Demonstrate request, rejection, provisioning, role change and effective removal with traceable records.