GUIDE · IDENTITY AND ACCESS

Identity and access management (IAM): a guide for businesses

This guide explains what managing identities and access means in a business, which components are involved and the order in which to bring them under control. By the end you will be able to tell identity, authentication and authorisation apart, understand where the greatest risks concentrate and choose which topic to explore first.

Updated october 2026
8 min read
Altovar Technical Editorial Team

1. What identity and access management is

IAM stands for Identity and Access Management. It is the set of processes and tools that establish who a person or system is, how they are recognised, which resources they can reach, with which permissions and for how long. In a business every employee, supplier, application and device that uses data or services has an identity, and every identity has permissions. When these things are not governed, access accumulates that nobody remembers having granted.

The discipline is not only about technology. An identity system can be installed correctly and still be ineffective if there are no rules on who approves an access, who revokes it when someone changes role and who checks the situation periodically. For this reason it is better to think of IAM as a set of organisational decisions supported by tools, not as a product to buy once.

2. The components: identity, authentication, authorisation

Three concepts must be kept separate. Identity is the digital representation of a subject: an account, with a username and attributes such as department, site or role. Authentication is the verification that whoever presents themselves really is that subject, typically with a password, a second factor or a hardware key. Authorisation is the decision about what that identity may do once it has been recognised.

Confusing these levels leads to frequent errors. If the password is strong but the account remains active for people who have left the company, authentication works and the identity is wrong. If permissions are granted to very broad groups for convenience, access is formally correct but disproportionate. When you evaluate a supplier, ask at which of these points it intervenes and how it integrates with the others.

3. Where it applies in practice

IAM touches almost everything: email, the management system, the file server, remote access, the supplier portal, the corporate Wi-Fi and the cloud administration consoles. Every system has its own way of managing accounts, and there are often several already, created over time and not always aligned with each other. The first practical step is to inventory the systems that hold data or allow processes to be changed, noting who uses them.

A central directory, meaning a service that keeps the official list of users, is often the starting point. From there applications can be connected through single sign-on or standard protocols, so that the lifecycle of an account is governed in one place. Not all applications support this integration. For those that do not, a documented manual procedure and more frequent checks are needed.

  • Email and collaboration tools
  • Management system and business applications
  • File servers and shared archives
  • Remote access and virtual private network
  • Cloud and infrastructure administration consoles

4. The user lifecycle

Every identity goes through three moments: joining, changing and leaving. In industry jargon these are called joiner, mover and leaver. They are the points where most incorrect access arises. A change of role tends to add permissions without removing the old ones, and a person's departure is reported late or not at all.

The ideal process starts from an authoritative source, such as the HR office or the manager requesting the new joiner's access, and assigns access based on role. Every additional permission requires a recorded approval. When someone leaves, the account should be disabled the same day, with devices and tokens revoked. The precise rules depend on the organisation: write them down and make sure those who apply them know them.

5. Privileged access and non-human identities

Privileged accounts are those that can change configurations, create users, read all data or switch off controls. There are few of them, but their impact is high. They should be separated from ordinary accounts: anyone who administers a system should have a personal identity for everyday use and a separate one for administrative operations, used only when needed. Privileged sessions deserve recording and approval.

Non-human identities are service accounts, applications, scripts and integrations between systems. They often have a password written in a configuration file, never expire and nobody knows who owns them. They are a frequent weak point. Every non-human identity should have an owner, a documented purpose and secrets kept in a dedicated secrets store, not in plain text.

6. Strong authentication and single sign-on

Good authentication combines several factors, such as a password and a confirmation on a device or a physical key. Multi-factor authentication is the step with the best balance between effort and risk reduction for most businesses, and it is covered in a dedicated guide. Alongside it, single sign-on, known as SSO, lets you enter several applications with a single login, reducing the number of passwords to manage and simplifying revocation.

Single sign-on carries one specific risk: if the central identity is compromised, every connected application is too. For this reason the directory must be protected more carefully than any other system, with limited privileges, monitoring of changes and tested recovery procedures. Ask your supplier how sign-ins are logged and how the case where the central identity is unavailable is handled.

7. Common mistakes to avoid

The first mistake is starting with the tools without having a list of who needs access to what. The second is treating the review of permissions as an extraordinary activity, to be done only during an external audit. The third is leaving accounts shared among several people, which makes it impossible to know who did what. The fourth is failing to plan an emergency procedure, and ending up granting broad permissions in a hurry without ever taking them back.

Another frequent mistake is measuring the project only by the number of integrated applications. What matters more is how many accesses are revoked correctly when needed, and how long a legitimate grant takes. If the process is so slow that people work around the rules, the system needs to be redesigned, not reinforced with more rules.

8. Topics to explore and where to start

This guide is an overview and each topic touched on here deserves further reading. The first to read is multi-factor authentication, because it is the control with the fastest effect. Straight after, read the guide on the user lifecycle, which defines the joining, changing and leaving rules that everything else depends on.

The other questions that deepen the subject concern passwordless access keys, single sign-on for applications, protection of privileged accounts, periodic review of permissions, choosing a business password manager, hardening the directory and managing application secrets. If you are starting from scratch, tackle them in this order: first the rules, then the tools.

9. How to start

This week, prepare a list of the systems that hold business data and, for each one, write down who administers it and who accesses it. No software is needed: a shared sheet is enough for a first version. Then choose the system with the most privileged access and check who can use it today.

Take this list to your supplier or security consultant and ask which parts of the management they can cover and which remain your responsibility. With that answer you will know where to focus the first intervention.

Frequently Asked Questions

Are IAM and a central directory the same thing?

No. The central directory is one of the most widely used systems for holding identities and permissions, but IAM is the broader discipline that includes it. A business can have a directory and still lack IAM processes if the rules for assigning, reviewing and revoking access are not defined. What matters is having an authoritative starting point and clear rules on who may change it.

Who should be responsible for IAM in a business?

Responsibility is usually shared. The IT department manages the tools, the head of each area approves access for their team, the HR office reports joiners and leavers, and whoever handles security or compliance checks that the rules are followed. In small businesses one person may cover several roles, but approvals should stay separate from technical operations.

Do I need dedicated software to get started?

Not necessarily. For the first phase an inventory of systems, a list of roles and a written procedure for joining, changing and leaving are enough. Tools become useful when the number of applications or people makes manual work hard to control. Ask a supplier to help you with the analysis first, so that you choose a tool based on the processes you really have.

How long does an IAM project take?

It depends on the scope: the number of systems, the quality of the user data and the availability of the people who must approve the rules. A project limited to one directory and a few applications closes much sooner than one involving the whole organisation. Be wary of anyone who promises precise timescales without first examining your environment.

How does IAM relate to GDPR and NIS2?

Both regulations require data and systems to be protected with measures proportionate to the risk, and access control is one of those measures. Limit who can read or change personal data and critical systems. However, no single tool makes you compliant automatically: an assessment carried out with a consultant who knows your sector and your situation is needed.

Where do I start if I have many different applications?

Start with the applications that contain the most sensitive data or have privileged accounts. For each one, note who has access, for how long and with which permissions. This list tells you where to focus the first interventions, such as enabling multi-factor authentication and reviewing permissions, without having to fix everything at once.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →