Chapter 9 · Reading 7 of 10
Identity proofing, federation and effective access
Security+ SY0-801 · Objectives 4.5
A contractor has a termination record, a disabled directory entry and an application session that still opens the dashboard. Ask three teams whether offboarding worked and you may receive three different answers. Each team is looking at a different step.
Follow a person from enrollment to termination
Identity proofing establishes an identity before issuing a credential. Authentication verifies control of an authenticator. Authorization evaluates permissions for a specific request. Accounting records what happened. Two passwords use one factor type. A device-bound passkey can provide phishing-resistant authentication, while the recovery channel may still permit a weaker path. Include recovery procedures, backup codes and emergency identities in access reviews.
A directory stores identities and groups. LDAP provides directory access. In federation, a relying service trusts an identity provider for specific assertions. SAML can carry signed authentication assertions. OAuth delegates scoped authorization, and OpenID Connect adds an identity layer. Validate issuer, intended audience, validity and signature in the applicable protocol. A token valid for a reporting service should confer no authority at an unrelated payroll service.
Evaluate effective permission at the resource
Role-based control groups permissions by job. Attribute-based rules can consider department, device posture or time. Mandatory policies can enforce labels centrally, while discretionary control lets an owner grant access within allowed bounds. Just-in-time elevation limits the period of privileged access. Review nested groups, local overrides and active sessions as well as the requested role. Give service identities named owners, specific permissions and monitored credential lifecycles.
For a departing contractor, stop new sign-ins, revoke sessions and refresh credentials where supported, remove local grants and check shared secrets the contractor could read. Verify a denied request at the actual application. Preserve audit records. For a role transfer, also test an allowed request in the new role so the access review protects continuity as well as confidentiality.
Review the account that nobody signs into
A nightly reporting job uses a service identity. Its original developer leaves, but the job continues to work. During recertification, ask who owns the business function, who may change its credentials and which resources it actually reads. The absence of interactive sign-ins is normal for this account. It tells a reviewer little about whether a broad export grant remains appropriate.
Design a rotation test with the service owner. Confirm the job can complete using the replacement credential, verify the old credential is disabled and watch the next scheduled run. An emergency identity needs a different review, including how access is authorized, used and monitored during a real outage. A single generic account checklist can miss the most important property of each identity type.
Test the promise made to the service owner
If the agreement says access ends when the contract ends, identify every place that can still say yes to a request. That includes local accounts, existing sessions, refresh credentials and permissions inherited through another group. Check shared material the individual could have copied, and decide whether rotation is necessary. A successful denial at the identity provider establishes that new sign-in is blocked. A denied request at the resource using a previously authorized session establishes something additional. Record both. Automating offboarding is easier once the team knows which independent outcomes it must verify.
Inspect the three records, then use the evidence to answer the question.
1. Directory
Contractor is removed from the directory group.
2. Identity provider
Identity provider refuses all new sign-ins.
3. Application
Local application session remains valid for four hours.
Apply the reading
Why does blocking new sign-ins leave a residual access question?
Compare your reasoning
A relying application may maintain its own session or cached permission until it expires or is revoked.