Authentication apps. Generate security codes via an outside party that grants access.
Biometrics. A user presents a fingerprint or eye scan to gain access to the system.
In some instances, systems require the successful verification of more than one factor before granting access. This multi-factor authentication (MFA) requirement is often deployed to increase security beyond what passwords alone can provide.
What Is Authorisation?
Authorisation in system security is the process of giving the user permission to access a specific resource or function. This term is often used interchangeably with access control or client privilege.
Giving someone permission to download a particular file on a server or providing individual users with administrative access to an application are good examples of authorisation.
In secure environments, authorisation must always follow authentication. Users should first prove that their identities are genuine before an organisation’s administrators grant them access to the requested resources.
Authentication vs. Authorisation
Despite the similar-sounding terms, authentication and authorisation are separate steps in the login process. Understanding the difference between the two is key to successfully implementing an IAM solution.
Let's use an analogy to outline the differences.
Consider a person walking up to a locked door to provide care to a pet while the family is away on vacation. That person needs:
Authentication, in the form of a key. The lock on the door only grants access to someone with the correct key in much the same way that a system only grants access to users who have the correct credentials.
Authorisation, in the form of permissions. Once inside, the person has the authorisation to access the kitchen and open the cupboard that holds the pet food. The person may not have permission to go into the bedroom for a quick nap.
Authentication and authorisation work together in this example. A pet sitter has the right to enter the house (authentication), and once there, they have access to certain areas (authorisation).
What does it do?
Grants or denies permissions
How does it work?
Through passwords, biometrics, one-time pins, or apps
Through settings maintained by security teams
Is it visible to the user?
It is changeable by the user?
How does data move?
Through ID tokens
Through access tokens
Systems implement these concepts in the same way, so it’s crucial that IAM administrators understand how to utilise both:
Authentication. Let every staff member access your workplace systems if they provide the right credentials in response to your chosen authentication requirements.
Authorisation. Grant permission to department-specific files, and reserve access to confidential data, such as financial information, as needed. Ensure that employees have access to the files they need to do their jobs.
Understand the difference between authentication and authorisation, and implement IAM solutions that have strong support for both. You will protect your organisation against data breaches and enable your workforce to be more productive.
Granting Permissions with Okta
Okta Lifecycle Management gives you an at-a-glance view of user permissions, meaning you can easily grant and revoke access to your systems and tools as needed. Meanwhile, Okta Adaptive MFA lets you safeguard your infrastructure behind your choice of authentication factors.
For example, make production orders accessible only to certain users who may then have to authenticate using both their company credentials and voice recognition.
The opportunities to streamline IAM in your organisation are endless. Find out how Okta can keep you, your employees, and your enterprise safe.
Want to know how else Okta can help with authentication and authorisation? Check out our page on Privileged Access Management.