Read a sample: 1. Finding Your Place in Identity and Access
On a busy Monday morning, an identity support analyst opens a queue of requests. One employee needs access to a scheduling application. Another cannot sign in after replacing a phone used for multifactor authentication. A manager has submitted a departure request that must be completed at an approved time.
None of these tasks looks like the dramatic version of cybersecurity often shown on a screen. There may be no attacker to chase and no malicious code to analyze. Yet each request involves an important question: who should be able to use which resources, and under what conditions?
Identity and access work helps organizations answer that question and carry out the resulting decisions. At the entry level, the work often combines customer service, careful administration, troubleshooting, and respect for established procedures. It can offer a practical route into cybersecurity for people who enjoy solving problems and paying attention to details.
It is also a field with boundaries. An entry-level analyst may carry out an approved access change without being the person who decides whether that access is appropriate. Learning to recognize that distinction is part of becoming effective in the role.
Organizations rely on accounts to give people access to computers, applications, files, and services. Those people may include employees, contractors, temporary workers, and others who need resources for a legitimate reason. Each person’s access can change as their relationship with the organization changes.
Identity and access management, often shortened to IAM, encompasses the practices and technologies used to manage digital identities and access. The work can begin when someone joins an organization, continue as they change responsibilities, and include removing access when it is no longer needed.
A useful way to picture the work is as a lifecycle:
- A new worker needs an account and approved access.
- The worker needs help signing in or using an authentication method.
- A change in responsibilities requires access to be added, adjusted, or reviewed.
- A departure or other authorized event requires access to be removed.
Not every organization assigns all of these tasks to one team. Some distribute them among a service desk, an identity operations team, application administrators, human resources, and security personnel. The tools and terminology also vary. The underlying purpose, however, is recognizable: help the right people obtain the access they need while following the organization’s requirements for authorization, verification, and recordkeeping.
This chapter gives you a map of the work. The next chapter will introduce the building blocks—identities, accounts, credentials, permissions, and groups—before later chapters walk through individual requests in greater detail.
A junior identity or access professional often works from a queue of tickets. A ticket is a record of a request or issue, usually containing the requester’s details, relevant approvals, actions taken, and the final outcome. The queue might include routine tasks that can be completed using a documented process as well as unusual cases that require help.
Review requests before acting. A request to “give Maya the same access as Jordan” may sound straightforward, but it leaves important questions unanswered. Which application is involved? What access does Maya need for her own work? Has the appropriate person approved it? A junior analyst may be expected to check the request against the organization’s process and ask for missing information rather than guess.
Create or update accounts. Once the required information and approvals are in place, an analyst might create an account, update an existing one, or add a person to an approved access group. The actual steps depend on the organization’s tools and the analyst’s permissions. Some requests may be completed through an automated system; others may require work in an administrative interface or a handoff to another team.
Help people authenticate. Authentication support concerns problems proving that a person can sign in. A user might be locked out, have trouble with a password reset, or need assistance enrolling a new authentication method. The analyst’s job is to help while using the approved process to verify the person’s identity. Being friendly and efficient matters, but a request does not become legitimate simply because the caller sounds convincing or is in a hurry.
Support access changes and reviews. A transfer or temporary assignment can create a need to compare current access with what has been approved. A junior employee might gather information, prepare a report, or carry out an authorized change. The decision about what access is appropriate may belong to a manager, application owner, or another designated reviewer.
Remove access when authorized. An analyst may disable an account or remove selected permissions as part of a departure or role change. Timing and coordination matter: a request may specify when the change should occur, and other systems or teams may be involved. The analyst should not assume that completing one step automatically handles every form of access.
Document and escalate. Good work leaves a useful record. A ticket note should make it possible for an authorized colleague to understand what was requested, what was verified or approved, what action occurred, and what remains unresolved. When a request is unclear, outside the analyst’s authority, or potentially suspicious, the next step may be to pause and involve the appropriate person.
These responsibilities are related, but they are not interchangeable. Resetting a password, approving access, creating an account, and investigating suspicious activity require different decisions and may belong to different roles. Job descriptions can blur those distinctions, so…