Skip to main content

IAM (identity and access management)

IAM (Identity and Access Management) covers the rules and tools that decide who can sign in to what, with which rights, and that remove those rights at the right time.

Updated on 14 November 2026

Definition of IAM

IAM (Identity and Access Management) covers the rules and tools that answer three questions: who the user is, what they are allowed to access, and until when. It covers the account directory, authentication (password, two-factor, single sign-on), rights, and their removal when an employee leaves.

A real-world example

An employee leaves the company on a Friday. With well-run IAM, her account is disabled that same evening: no more access to email, files or applications. Without IAM, her account stays active for weeks, and her laptop, found in a drawer, still has her sessions open.

IAM manages the account. For the laptop, you also need to know where it is, what condition it is in, and prepare it for the next person: that is where LongLife comes in, with the device page, its history and the reassignment decision.

The building blocks of IAM

Building blockRoleExample
DirectoryList of identitiesActive Directory, Microsoft Entra ID
AuthenticationProve who you arePassword + two-factor authentication app
AuthorisationGrant the right permissionsAccess to the accounting folder for the accounting department
LifecycleCreate, modify, removeAccount disabled when the employee leaves
AuditKeep a recordLog of sign-ins and sensitive actions

Check the rights on a device

Local administrator rights are a frequent weak point. On each device, check who belongs to the local Administrators group (its name changes with the Windows language): only IT accounts should appear there, not everyday user accounts.

What LongLife brings around IAM

LongLife is not a directory: it takes care of what IAM does not see, the device itself.

  • The security posture of each device: antivirus, firewall, BitLocker, User Account Control (UAC) and updates, checked continuously. A well-protected account on a poorly protected device remains exposed.
  • The device lifecycle: arrival, reassignment, departure, with the device's history in its health log.
  • Its own access, protected by mandatory two-factor authentication, stronger confirmation for sensitive actions, and an exportable audit log.

The free plan covers up to 15 devices. Book a meeting to talk about it, and read also our definition of the attack surface.

Sources

Frequently asked questions

What does IAM stand for?

IAM stands for Identity and Access Management. It covers account creation, authentication, the rights granted to each person and their removal when someone leaves.

What are the basic principles of IAM?

One account per person, as few rights as possible (principle of least privilege), strong authentication (two factors), and immediate revocation of access when an employee leaves.

Are administrator rights on devices a problem?

Yes. A user who is administrator of their device can install any software, disable protections and, in an attack, hand elevated rights to the attacker. These rights should be limited to the people who need them.

Is LongLife an IAM tool?

No, LongLife focuses on workstations: their condition, their security and their lifecycle. It complements IAM by showing devices whose protection is weakened, and protects its own access with two-factor authentication.

Read also

See the real state of your fleet

LongLife measures the health of your Windows devices every day and recommends keeping, upgrading or replacing them, with the cost and CO₂e of each option.