Unit 4.pptx
Unit 4.pptx
Authentication and
Access Control
There is a growing demand for different types of user
authentication technologies for both online and in physical
systems. The motivation to authenticate users ranges from
access control reasons to business development purposes
like adding e-commerce elements.
► An Access Control Model is a framework that defines how users are granted or
restricted access to resources based on policies, rules, roles, or attributes. It ensures
that only authorized users can perform specific actions on a system.
Access control models are used to:
1. Enhance Security – Prevent unauthorized access to sensitive data and systems.
2. Protect Confidentiality & Integrity – Ensure data is accessed only by authorized
individuals.
3. Regulate User Permissions – Assign permissions based on roles, rules, or attributes.
4. Meet Compliance Requirements – Enforce security policies in organizations (e.g.,
GDPR, HIPAA).
5. Reduce Insider Threats – Limit access based on necessity (Principle of Least
Privilege).
This is the access control process:
► identifying a person doing a specific job
► authenticating them by looking at their identification
► granting a person only the key to the door or computer that they need access to
and nothing more
► Reliable security — With permissions granted on a need-to-know basis, admins can be assured
that staff are only able to access locations and resources essential to their roles.
► Simple management — Configuring and adjusting permissions can be reduced to a small
number of roles, requiring less administrative resources to manage large workforces.
► Easily issued credentials — When new employees are hired, or existing staff are promoted,
relevant credentials can be issued immediately without needing to create new profiles.
► Company-wide consistency — Organizations that operate across multiple sites can ensure that
the same role carries identical permissions across the business.
► Some potential drawbacks to the use of RBAC systems include:
► Inflexibility — As role-based permissions are designed to address large numbers of staff with one
policy, credentials cannot be customized to fit individual or dynamic use cases.
► Requires organizational structure — For RBAC models to be effective, there must be a clearly
defined hierarchy, which isn’t always present in start-ups and scaling businesses
Best practices
Pros:
✔ Easy to implement and manage.
✔ Flexible access control for users.
✔ Suitable for non-restrictive environments.
Cons:
✖ Higher risk of unauthorized access.
✖ Prone to privilege escalation attacks.
✖ Hard to enforce strict security policies.
Best Practices
Now that we have understood the working of the RADIUS protocol let’s also understand the advantages of the
RADIUS protocol:
• The RADIUS protocol is known to be highly scalable which means that it can support large networks which have
many devices and many users.
Disadvantages of RADIUS Protocol
Now that we have looked at some of the benefits or advantages of using the RADIUS protocol
let’s also look at some of the disadvantages which we may face if we are going to use the
RADIUS protocol:
• The RADIUS protocol uses udp which makes it less reliable than TACACS+
• The RADIUS protocol only encrypts the password which means that it cannot protect other
data such as the usernames.
• This protocol is very vulnerable to other types of attacks such as spoofing as well as
dictionary attacks.
TACACS+ Protocol
The full form of the TACACS+ stands for terminal access controller access control server, it is a
protocol which has similarities to the RADIUS protocol, which means that it is a security
protocol and it is also used in the AAA framework, it is used to to provide centralized
authorization to various types of users who need to gain access of the network.
► The Cisco company has developed the protocol for AAA framework which means that it can be
used between the Cisco device and Cisco ACS server, This protocol uses tcp as transmission
protocol and it uses the TCP port 49.
The client of the TACACS+ protocol is called the network access device (NAD) it is also called
network access server (NAS) the network access device contacts the TACACS+ server in order to
obtain prompt of the username and it does this using the CONTINUE message.
► After this the user simply enters a user name and then the network access device makes a
contact to the protocol server again in order to obtain the password prompt after this the user
simply enters the password and then the password is sent to the protocol’s server.
Advantages of TACACS+ Protocol
Now that we have understood the basics about this protocol, let’s look at some of the advantages
that this protocol offers:
• It provides better control then the RADIUS protocol because it allows the network administrator
to easily define what commands a user can run.
• All the AAA packets are more encrypted rather than just being passwords.
• TACACS+ protocol uses the TCP connection instead of the UDP connection and the TCP
guarantees the communication between both the client and the server.
• As we discussed that it is a cisco proprietary which means that it can only be used in the Cisco
devices.
• This protocol has less support for the accounting as compared to RADIUS.
Kerberos
•The user sends the TGT to the Ticket Granting Server (TGS) and asks for access to a specific
service.
Access Service
•The user presents the Service Ticket to the Service Server (SS).
•If valid, access is granted.
Advantages of Kerberos
• No password sent over network – reduces the risk of password theft.
• Single Sign-On (SSO) – login once to access multiple services.
• Strong security – based on symmetric encryption and time-based tickets.
• Mutual authentication – both user and server verify each other.
Disadvantages of Kerberos
• Complex setup – requires careful configuration of time, encryption keys, and
tickets.
• Time-sensitive – all devices must be time-synchronized (clock skew can cause
failures).
• Single point of failure – if the Key Distribution Center (KDC) is down, authentication
fails.
• Initial trust required – users and services must initially trust the KDC.