We have a professionally managed AD environment. Do we still need HelloID?
Yes. We see that organizations often rely on their own AD environment for the original IAM functions, Authentication and Authorization. What it lacks is a full management solution that can automatically and on time assign the correct permissions to everyone in a large organization with hundreds of users and dozens of applications. HelloID provides that. AD delivers the technical components for Authentication and Authorization, while HelloID handles the integration and its management. In addition, our flexible Access Management module, with extensive Single Sign-On and Multifactor Authentication, often provides the necessary workarounds during migration and merger projects. It is also not always necessary for every user group to use a comprehensive Microsoft license, which is therefore more expensive. For those users, HelloID SSO and MFA Access Management, combined with a relatively low-cost E1 license, is often sufficient.
Does HelloID also support my security and privacy awareness initiatives?
Employee awareness is indeed a crucial component of information security. By automating the entire user lifecycle and leveraging our robust RBAC framework, we primarily focus on enforcing least privilege. This prevents employees from accessing data they do not need for their work. If desired, we also add such awareness measures for customers. For example, we can add HelloID Business Rules that require users to explicitly accept the organization's privacy guidelines before their access rights are activated. Until acceptance, users have access only to email and standard applications. For additional requests, the online approval process can also include an explicit check that the requester meets specific training requirements.
How does the RBAC framework support the least privilege requirement?
In the Role-Based Access Control (RBAC) framework, the access rights for each role are defined unambiguously, so people receive access strictly on a 'need-to-know' basis. When a person's role changes in the HR system, HelloID automatically checks which rights no longer apply and revokes them. It also checks which new access rights are required for the new role and automatically provisions them. This prevents unwanted privilege creep that often occurs with manual access management.
How do you organize access security during a reorganization?
The RBAC framework is ideal for this. With RBAC, we manage all roles and their associated access rights in a central place. During a reorganization, many changes can be implemented, from an RBAC perspective, such as adding roles and adjusting role-based access rights. If we first create the new roles and rights and only then link employees to those roles in the HR system, we can migrate in a controlled way to the new state while everyone retains access to their applications and data.
Can an organization-wide RBAC framework be applied?
No. In general that is not practical. In many organizations we can assemble a complete RBAC profile, with all required access rights, for a subset of roles, the so-called key roles. These are often clearly defined roles with bounded responsibilities. However, people can also hold multiple roles, and there are less clearly defined functions in, for example, staff departments. For those users, we assign the basic access rights through the RBAC model. Additional access must be requested through the service process. With HelloID we can automate such request processes as well. To prevent unnecessary rights from being granted, we can set up specific approval flows in which the relevant manager or managers must review and approve the request online. This preserves separation of duties, and we can also configure such rights to be granted only temporarily. This prevents unwanted privilege creep.