Chapter 9 · Reading 1 of 10
Reviewing privileges after a transfer
Security+ SY0-801 · Objectives 4.5
Mina finishes a temporary finance assignment on Friday and starts at the support desk on Monday. She can use the ticket queue exactly as intended. She can also still export payroll. The onboarding workflow succeeded twice, yet the institution has an access problem.
Identity proofing establishes who a person is before enrollment. Authentication verifies a credential, authorization decides what an authenticated identity may do and accounting records activity. Federation lets a service rely on identity assertions from a trusted issuer. Validate the issuer and intended recipient. OAuth delegates scoped access, while identity protocols built on it can provide sign-in.
Review effective permissions
Provision users from approved role definitions and check entitlements when they join, move or leave. Use a separate privileged identity and time-limited elevation for administration. Protect recovery and emergency accounts with monitoring and controlled access. For a service account, assign an owner and rotate its credentials without interrupting dependent jobs. Review effective permissions, including inherited group membership.
Follow a role change through the week
Begin with the approved responsibilities of the old and new jobs. List the rights required for each, then inspect the effective access in the actual application. An old directory group, a direct exception and a local role may all grant the same export. Removing one path can leave another in place. A manager approving a list of group names needs enough information to understand which business actions each group permits.
Arrange two checks using a synthetic identity with equivalent permissions. The support ticket transaction should succeed. A payroll export should be refused and recorded. Check existing sessions separately because the application may have cached its authorization decision. If a service owner grants temporary overlap during a handoff, record the reason, approver and expiry so the exception gets revisited.
Who owns a temporary permission?
Mina’s former supervisor asks for one additional week to reconcile a payroll discrepancy. Giving back the entire old role restores more access than the specific task requires. Ask what record she must see, which action she must take and how long the task will last. A narrowly scoped grant with documented expiry and a separate approver can support legitimate work while giving the reviewer a concrete end condition.
Test what happens when that end date arrives. A ticket reminder asks a person to act. A target application that expires the grant enforces a state change. Either approach needs evidence of completion. If payroll access persists after the intended date, record whether the issue is authorization policy, failed provisioning or an existing session. Those explanations lead to different fixes.
Identity is also evidence
When a suspicious export is reported, a display name alone will not distinguish Mina’s current session from a shared service identity. Preserve the issuer, stable identifier, target application and time of the decision. This information lets an investigator join the event to the right account history. Operations teams spend much of their time making these records usable before an incident forces someone to rely on them.
Inspect the three records, then use the evidence to answer the question.
1. Record A
Mina moved from finance to support
2. Record B
Support role requires ticket access
3. Record C
Old payroll-export entitlement remains assigned
Apply the reading
What evidence supports your decision in the entitlement overlap exercise?
Compare your reasoning
A role change can accumulate privileges. Verify removal in the target application and record the approval for retained access.