Overig · Overig
IAM as a basis for Zero Trust: How identity forms the heart of a Zero Trust architecture

Dylan Klümann · Project Manager · 6 min read
It's a typical Tuesday morning when an employee logs in from a coffee shop. She is working on a report for an important meeting. The connection is open, busy and anything but secure. Yet she gains immediate access to her applications. Everything feels smooth. Invisibly in the background, a security model runs that analyses every second who she is, where she comes from and what risk her request entails.
That security model is called Zero Trust.
And without IAM, Zero Trust simply doesn't work.
Zero Trust sounds strict, but it's about trust
Zero Trust is often seen as a complex concept. Some people think it's mainly about stricter security, extra checks and complicated techniques. But at its core, Zero Trust is surprisingly logical.
The principle is simple:
Don’t automatically trust anyone. Not a user, not a device, not a location.
Access must be continuously earned.
But it sounds heavier than it is.
Zero Trust is not about distrust. It's about smart trust. No longer blindly assuming someone is okay because they are within the enterprise network. But continuously checking if the identity is correct, the device is secure, and the context is logical.
And it always starts with one thing: the digital identity.
Why identities form the heart of Zero Trust
In traditional security, much trust was placed in networks. Whoever was within the office network was considered safe. But since hybrid working, cloud applications and mobile devices have become the norm, that model is completely outdated.
The network is no longer a boundary.
The identity is.
IAM ensures that every identity check is reliable. It forms the foundation on which Zero Trust makes its decisions. Without reliable identities, Zero Trust cannot determine who may gain access and what risks are involved.
IAM and Zero Trust are not separate disciplines.
They are inextricably linked.
A real-life story: when it almost went wrong
An organisation we spoke to had been working for years on strengthening their cybersecurity. Firewalls were improved, VPNs were expanded, and there were strict password rules. They thought they were well-prepared.
Until one evening a brute force attack took place on an employee’s external account. And that account had access to multiple cloud applications. Fortunately, the organisation discovered it in time, but it became painfully clear: the greatest risk was not in their network, but in their identities.
That evening the organisation decided to switch to a Zero Trust strategy with IAM as the foundation. With strong authentication, automated risk controls and continuous identity monitoring.
Since then, identity has been their first line of defence.
The three indispensable pillars of Zero Trust IAM
Zero Trust has many components, but IAM plays a central role in three essential pillars:
1. Continuous verification
IAM doesn't check only at login, but also during use. Risks are constantly changing. Location, device status, behaviour, time: everything can be a reason to verify again or allow smoothly.
2. Access based on least privilege
IAM ensures that employees get exactly what they need, no more. Do you work in Finance? Then you only get access to financial applications. Are you a manager? Then you have access to reports, but not to unnecessary data sources. This minimises damage when something goes wrong.
3. Contextual access
IAM recognises situations where risk is low and where it is high. Access from a known laptop at home feels different than access via an unknown device at an airport. IAM responds to this without bothering the user.
These pillars make Zero Trust not only secure but surprisingly user-friendly.
Zero Trust is not an extra layer of security, but a new way of thinking
Many organisations think Zero Trust is primarily about new tools. But Zero Trust is primarily an identity-driven mindset. It's a shift from “how do we protect our network” to “how do we ensure that only the right people, under the right circumstances, gain access to what they need”.
And the key lies with IAM.
With a mature IAM implementation, you give users safe access without fuss. It becomes the engine behind every Zero Trust decision. Without blocking. Without frustrating. Without extra steps if they are not necessary.
In fact: good IAM makes Zero Trust more pleasant for users. Employees experience fewer prompts, fewer login steps and fewer hurdles. Zero Trust becomes not an obstacle, but a reassurance.
The difference between reactive and proactive security
Without IAM, security is often reactive. A notification comes in, someone checks logs, IT intervenes. But with Zero Trust, it works exactly the opposite. Identity security responds before the problem can occur.
IAM detects, for example:
anomalous behaviour
unusual login locations
insecure devices
And immediately activates extra verification or automatically blocks access.
That is the difference between preventing a data leak and resolving a data leak.
Joinly's vision: Zero Trust starts with solid identities
At Joinly, we see that organisations often start with Zero Trust from technology. But in reality, it starts at the base: a reliable identity for every employee, on-site worker, temporary worker or partner. Only then does the rest follow.
We help organisations lay that foundation. With modern IAM solutions that automatically manage access, intelligently determine risk and continuously protect without irritation for users.
IAM makes Zero Trust feasible.
Joinly makes IAM simple.
Zero Trust is not futuristic. It is an architecture that makes a difference today. And with IAM as the basis, it becomes a strategy that increases security and enhances work enjoyment.
Explore more blogs

Segregation of Duties (SoD): wat het is en hoe je het afdwingt
Wat is segregation of duties (functiescheiding)? Uitleg, voorbeelden en waarom het vaak misgaat. Plus hoe je SoD-conflicten automatisch tegenhoudt.
Marcel van Beek · 4 min read

How do you apply AGDLP in a hybrid Entra/AD environment? (And why you shouldn't want to anymore)
Short answer: preferably not. AGDLP (Accounts → Global groups → Domain Local groups → Permissions) is a concept from the era of manual management. The entire nesting construction exists for one reason: to allow a human to assign permissions with as few mouse clicks as possible. As soon as an agent assigns group memberships directly based on HR data, this reason disappears and only the complexity remains. Moreover, in a hybrid environment, this complexity actively works against you, because Entra ID completely ignores nesting for licences and app assignment. In this article, you can read how AGDLP works and why it was once smart, where it breaks down in a hybrid environment, and what the modern alternative looks like: direct memberships, managed by automation.
Marcel van Beek · 5 min read

How do I set up role-based access control (RBAC) and least privilege for a municipality?
Start with the roles in your HR system and map them to roles, not to individual permissions per person. Group each role with precisely the access required for the job, adhering to the principle of least privilege. Manage these roles centrally and let an orchestration layer automatically assign and revoke them. This keeps access predictable, limited and demonstrable.
Mike Fraanje · 4 min read
See what Joinly can do for your organisation?
Start a free trial today or get in touch for advice on your HR and Microsoft environment.