Start correctly
Does someone receive exactly what fits their role, department and contract on day one?
IDENTITY & ACCESS MANAGEMENT
From JML process to identity control.
A completed request does not prove that access is actually correct. SAS connects policy, records and technical access across the full identity lifecycle.
IDENTITY LIFECYCLE
Every change is a new control point.
The same three realities need to match again after every lifecycle event.
Change without accumulation
Are old rights revoked as carefully as new rights are granted?
Deliberate and time-bound
Are reason, owner, approval and end date demonstrably recorded?
Close completely
Have accounts, groups, licences and assets actually been closed or recovered?
THREE REALITIES AT EACH EVENT
Do not just execute. Verify the result afterwards.
What belongs to the profile?
Role, standard package, exceptions, approvals and end dates.
What is recorded?
Request, tasks, assets, applications, decisions and owners.
What exists technically?
Accounts, groups, roles, licences and actual access in target systems.
THE IDENTITY PROCESS
From event to controlled reality.
SAS makes HR, service management, identity and applications work together and reads the result back.
HR event→Profile→Approve & record→Execute→Read back→Compare & recover
TEMPORARY PRIVILEGES
Temporary really becomes temporary.
Temporary access is an exception within policy: known, approved, time-bound and demonstrably recorded. After the end date, SAS verifies that access was actually revoked.
Request→Approve→Grant→Revoke→Verify
PRACTICAL STARTING POINTS
The HR source remains. SAS closes the loop.
START SMALL
Plan an IAM control scan