Key Takeaways
- IAM answers two questions: Who is the person, and what are they allowed to access?
- Core building blocks are identity providers, Single Sign-On, provisioning, and role models such as RBAC.
- IAM covers the entire lifecycle: onboarding, role changes, and offboarding.
- Germany's BSI covers IAM in IT-Grundschutz module ORP.4 Identity and Access Management.
What building blocks belong to Identity and Access Management?
IAM consists of several building blocks, each covering part of access control:
- Identity provider: verifies identity at login.
- Single Sign-On: one login for many applications.
- Provisioning and deprovisioning: creating and removing accounts, e.g., via SCIM.
- Role models and least privilege: granting permissions according to job function.
- Access reviews: regularly checking whether permissions are still needed.
Why is IAM important for small and medium-sized businesses?
IAM prevents access rights from growing unchecked and remaining open after departures. Companies with 20 to 150 employees often use dozens of SaaS applications but rarely have a dedicated IAM team. Without a central view, nobody knows exactly who has access to what. This complicates audits, GDPR compliance documentation, and customer information security questionnaires.
How do small businesses get started with IAM?
Small businesses start with a central identity and a defined process for onboarding and offboarding.
- Use Google Workspace or Microsoft Entra ID as the primary identity.
- Connect key applications via Single Sign-On.
- Assign a responsible owner for every application.
- Handle onboarding and offboarding with a task list and documentation.
Example: Identity and Access Management (IAM) in practice
Example: A mechanical engineering supplier with 120 employees introduces IAM step by step. Microsoft Entra ID becomes the primary identity, and 18 of 32 applications run via Single Sign-On. Each of the remaining 14 applications has a designated owner. Four roles such as Sales or Accounting bundle standard permissions, and managers review their team's access every six months.
Identity and Access Management (IAM) vs. Identity Provider (IdP)
| Aspect | Identity and Access Management (IAM) | Identity Provider (IdP) |
|---|---|---|
| Nature | Discipline of processes, policies, and systems | Individual system or service |
| Task | Govern identities and access across the entire lifecycle | Verify identity at login |
| Examples | Role model, access review, onboarding and offboarding | Microsoft Entra ID, Google Workspace, Okta |
| Responsibility | Management, HR, IT, and business departments | IT or administrator |
IAM is the overall discipline of governing identities and access, whereas an identity provider is one of the technical systems used to implement it.
How does Sovaro help with Identity and Access Management (IAM)?
Sovaro is not an IAM system, identity provider, or SSO service. Sovaro complements IAM organizationally: new hires and departures from Personio, Google Workspace, or Microsoft Entra trigger workflows with tasks for HR, IT, managers, and tool admins. Apps are detected via the agent and browser extension, even without SSO, and linked to the person.