CompTIA SY0-701: Identity and Access Control
Access control begins before login and continues after a person or workload should no longer have access. Consider a contractor whose directory account is disabled while an application session, API key, or local service identity remains valid. Authentication worked when access was issued, but the offboarding process failed to revoke the full path. The same lifecycle applies to provisioning, group membership, privileged elevation, federation, and periodic access reviews. This article explains how identity, authorization, sessions, and deprovisioning fit together, including the evidence administrators should check before treating an access removal as complete.
On this page
- Treat identity as a lifecycle, not a login screen
- Choose authentication methods for the risk
- Use federation and single sign-on deliberately
- Separate authentication from authorization
- Protect privileged access as a separate risk
- Use access reviews to detect entitlement drift
- Deprovision the whole access path
- Prove contractor offboarding across sessions and nonhuman credentials
- Confirm that access is revoked across the identity lifecycle
Treat identity as a lifecycle, not a login screen
An identity system begins before authentication and continues after access is granted. A person, device, service, or workload has to be identified, enrolled, issued credentials, assigned permissions, monitored, changed when roles change, and eventually removed. Strong authentication cannot repair weak provisioning. If the wrong person was enrolled, MFA protects the wrong identity. If an account receives excessive privilege, successful MFA only proves who is using the excessive privilege.
Modern identity programs separate proofing, authentication, federation, authorization, review, and deprovisioning into different decisions. Each stage answers a different question and can fail independently; treating them as one sign-in event can obscure the actual control failure. Zero trust places identity inside a broader access decision. The subject still needs appropriate authorization, device or workload context, and resource policy after authentication succeeds.
Authoritative enrollment and minimum initial access. Identity proofing establishes confidence that the person or entity being enrolled is who it claims to be. Employees may be tied to authoritative HR records, customers to approved verification processes, devices to enrollment systems, and workloads to platform-controlled identity mechanisms. Provisioning should start from an authoritative source and assign only the access needed for the initial role. Informal account creation from an email or chat request is weaker than a controlled workflow connecting identity, approval, role, and expiration conditions.
Use unique identities instead of shared accounts wherever accountability matters. Shared administrative credentials make it difficult to determine who changed a system and complicate revocation when one person’s role changes. Identity data needs hygiene too. Duplicate accounts, orphaned accounts, stale groups, inconsistent names, and unmanaged local identities all make later authorization and investigation harder.
Choose authentication methods for the risk
Authentication proves possession or control of one or more authenticators. CompTIA Security+ SY0-701 candidates should understand factors such as something you know, have, or are, but real security depends on implementation and recovery. Multifactor authentication uses independent factors rather than two prompts from the same category. MFA reduces password-only compromise, but methods differ in resistance to phishing, replay, social engineering, and device compromise. Authenticator lifecycle matters. Enrollment, replacement, revocation, and lost-device handling can become weaker paths than normal login.
Use stronger authentication for higher-risk actions. Routine low-sensitivity access may not need the same assurance as privileged administration, sensitive data access, or credential recovery.
Recovery is an alternate authentication path. Attackers often target recovery because it can bypass stronger controls used during normal sign-in. A password-reset process based on easily researched information or an informal help-desk conversation can undermine an otherwise strong authenticator. Recovery should verify identity at an assurance level appropriate to the account, record who approved the recovery, and revoke compromised or replaced authenticators. High-value privileged accounts may justify additional approval.
Do not leave old authenticators active after recovery. Remove lost device registrations, revoke tokens where appropriate, rotate exposed secrets, and review recent sessions for evidence of misuse. Recovery events are security-relevant telemetry. Unexpected recovery can be an early sign of account takeover.
Use federation and single sign-on deliberately
Federation allows one identity system to assert information to another service, while single sign-on reduces separate authentication experiences. These approaches can improve usability, centralize lifecycle control, and reduce unmanaged passwords. They also create concentration. If many applications trust one identity provider, compromise or outage can affect many services. Strong administrative controls, resilient recovery, monitored changes, and secure federation configuration therefore matter. Assertions and tokens should be scoped appropriately. Long-lived or broadly reusable tokens increase exposure after theft. Audience, expiration, signing, claims, and session behavior affect the relying service’s decision. Federation is not authorization. A service can trust the identity provider and still need its own resource policy.
Separate authentication from authorization
Authentication asks who or what is making the request. Authorization asks what that subject may do after identity is established. Role-based access control groups permissions around job or system roles. Attribute-based access can use subject, resource, action, and environmental attributes. Rule-based, discretionary, and mandatory models reflect different policy assumptions. The exam-relevant skill is choosing the model and scope that fit the scenario rather than memorizing acronyms alone.
Least privilege should shape authorization regardless of model. Give a subject the access required for the role, resource, action, and duration involved. Role changes should remove old entitlements as well as add new ones. Otherwise privilege accumulates silently.
Protect privileged access as a separate risk
A privileged account can affect identity policy, audit settings, key material and live workloads across several trust boundaries. Giving that identity the same daily-browsing and collaboration exposure as an ordinary user account raises the probability and impact of compromise. Use separate administrative identities where practical, strong authentication, narrow role assignment, just-in-time elevation, approval for sensitive operations, and monitoring of privilege use. Privileged access management can broker credentials, manage elevation, record sessions, rotate secrets, and enforce workflows. The product matters less than the control goals: reduce standing privilege, make use attributable, and remove access when no longer justified.
Administrative paths deserve architectural protection too. A privileged identity used from an unmanaged device can remain risky even with a strong password.
Nonhuman identities also require ownership and offboarding. Modern environments contain application accounts, API credentials, service principals, device certificates, automation tokens, CI/CD identities, and cloud workload roles. These identities need owners, narrow permissions, controlled credential storage, rotation or lifecycle processes, and monitoring. A service account with an unknown owner and a non-expiring secret can survive long after its application. Prefer platform-managed or short-lived workload credentials over embedded static secrets where supported. Reduce reusable credentials and make authorization specific to the task. The security logging process is more useful when nonhuman activity can be attributed to an owned system.
Use access reviews to detect entitlement drift
Permissions accumulate over time. Projects end, users move teams, contractors change scope, temporary access becomes permanent, and groups inherit new permissions. Periodic access review helps identify these mismatches. A useful review provides enough context to decide: identity, entitlement, role, resource, owner, and business reason. Asking managers to approve cryptic group names produces weak evidence. High-risk privileges deserve more frequent or event-driven review. Privileged roles, external accounts, service identities, and sensitive-data access should not wait for an annual campaign when the environment changes faster than that.
Findings should lead to removal, correction, or an explicit exception. Metrics such as stale privileged accounts and overdue reviews can expose lifecycle weakness.
Look for changes to authenticators and privileges, not only login counts.
Identity monitoring should look beyond failed passwords. New authenticator enrollment, unusual token issuance, privileged-role changes, dormant accounts becoming active, recovery events, and unexpected service-account use can all deserve attention. Baselines help analysts recognize behavior unusual for a specific account or peer group. An administrator using a privileged tool can be normal, while the same action from an ordinary user may be suspicious.
Identity telemetry should connect to asset and application context. A sign-in becomes more meaningful when defenders know what resource was accessed and what authority the identity received. Monitoring also measures program health. Rising orphaned-account counts or repeated emergency access can indicate governance problems rather than isolated mistakes.
Deprovision the whole access path
Disabling one directory account does not always remove all access. Active sessions, refresh tokens, API keys, local accounts, cached credentials, SSH keys, certificates, application-specific roles, shared secrets, and physical access can continue. Joiner, mover, and leaver processes should identify the full set of access created during the relationship. Role changes need removal as well as addition. Temporary access should expire automatically. High-risk departures may require rapid session revocation, credential rotation, device recovery, and review of recent privileged activity. Ordinary departures still need a reliable workflow. Deprovisioning should be tested. A process that disables the primary directory identity but leaves SaaS sessions active is incomplete.
Prove contractor offboarding across sessions and nonhuman credentials
A contractor finishes an analytics engagement at 17:00. HR closes the engagement and the identity team disables the directory account, but the contractor used single sign-on to a reporting application and created an API token for nightly exports. A successful directory-disable event is insufficient evidence that data access ended. Inventory the contractor’s group memberships, application roles, active sessions, API tokens, device registrations, delegated service identities, cloud subscriptions and shared workspaces. Assign each revocation to the system that can actually enforce it.
The control owner should perform a negative test with a previously authenticated browser session and a representative API token. Verify that both can no longer retrieve a protected report after the authorized termination point. Record whether revocation propagates immediately, at the next token refresh, or according to a documented short session lifetime; do not pretend that one global sign-out can revoke an unrelated application secret. For tokens and keys that cannot be attributed to an individual, rotate them according to system ownership and inspect the recent export log for unexplained activity.
Preserve a narrowly scoped emergency access route for business recovery, but make it a new, attributable authorization decision rather than reusing the contractor’s identity. Close the offboarding record only when each application owner supplies proof of access removal or an explicitly approved, expiring exception. This test links identity proofing, federation, session control, least privilege and auditing to one measurable outcome.
Confirm that access is revoked across the identity lifecycle
- Separate lifecycle stages. Proofing, authentication, authorization, review, and deprovisioning solve different problems.
- Protect recovery. Account recovery should not bypass normal assurance.
- Apply least privilege. Match access to role, resource, action, and duration.
- Protect privileged identities. Reduce standing administrator access.
- Govern nonhuman identities. Service accounts and workloads need owners.
- Review and monitor. Detect entitlement drift and abnormal behavior.
- Deprovision broadly. Remove sessions, tokens, keys, and application roles.
An effective access-control program governs the full identity lifecycle: proofing, role assignment, federation, session use, offboarding and verifiable access removal—not merely the first successful login.