Scribd
Upload
38 views4 pages

AAA

Authentication, Authorization and Account

Uploaded by

Kome Mohamad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
38 views4 pages

AAA

Authentication, Authorization and Account

Uploaded by

Kome Mohamad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Hello everyone, and welcome to this lecture on **Authentication, Authorization, and

Accounting**, commonly known as AAA. These are the foundational components of


information security, ensuring that only authorized users can access resources and that
all actions are meticulously recorded. Whether it's a user accessing sensitive data or a
system interacting with another, AAA plays a vital role in securing information and
preventing unauthorized access.

### **Authentication**

**Authentication** is the process of verifying the identity of a user or system before


granting access to any resource. Think of it as the first line of defense in securing
sensitive data and systems.

So, how do we authenticate people and systems?

For individuals, the process is often straightforward. Authentication typically involves


verifying the identity of users trying to access a system or enter a physical space, such
as a building. Common methods include:

- **Knowledge-based authentication**: This is something the user knows, like a PIN


code for a phone or a password for a computer.
- **Possession-based authentication**: This involves something the user has, such as a
smart card or a mobile device, often used for push notifications.
- **Inherence-based authentication**: This relies on something the user is, such as
biometric data, fingerprints, facial recognition, or iris scans.

In the context of **multi-factor authentication (MFA)**, these methods are often


combined to provide an extra layer of security. MFA typically involves a combination of:
1. **Something you know** (e.g., password or PIN),
2. **Something you have** (e.g., smart card or mobile device), and
3. **Something you are** (e.g., biometric data like fingerprints or facial recognition).
For example, when a user logs into an online banking system, they may be required to
enter a password (something they know) and confirm a code sent to their mobile phone
(something they have).

### **System Authentication**

Authentication is not limited to people. **Systems** also need to be authenticated,


ensuring that only trusted systems can communicate with each other. In a cybersecurity
context, especially in the era of **Zero Trust Architecture**, no system or user is
inherently trusted. Every entity must authenticate itself before being granted access to
resources.

One common method for authenticating systems is through the use of **Public Key
Infrastructure (PKI)**. In an organization, systems are often issued certificates that are
used to authenticate them with other systems. For instance, **Mutual TLS** (Transport
Layer Security) ensures that both the client and server authenticate each other using
digital certificates issued by a trusted Certificate Authority (CA). This ensures secure
communication between systems, such as a web server and a database server,
protecting data during transmission.

### **Authorization**

Once authentication is complete, **authorization** comes into play. While authentication


confirms who you are, authorization determines what you are allowed to do. Just
because a user or system is authenticated does not mean they have free rein over all
resources.

For example, after entering a building, you might be authorized to access certain areas
but restricted from others, such as a server room or sensitive data areas. In
cybersecurity, authorization ensures that a user or system can access only the
resources they are permitted to use, and can perform only the allowed operations (e.g.,
read, write, or execute).

Various models are used to implement authorization:

- **Discretionary Access Control (DAC)**: The resource owner decides who can access
the resource and what permissions they have. For example, if you create a document,
you can decide who can view or edit it.
- **Mandatory Access Control (MAC)**: Access is controlled by a central authority
based on classifications or security clearances. For instance, only system
administrators may have permission to access certain files or enter a server room.
- **Role-Based Access Control (RBAC)**: Access is granted based on a user’s role
within an organization. For example, an HR manager might have access to employee
records, while a sales associate would only have access to customer data.
- **Attribute-Based Access Control (ABAC)**: Access decisions are based on attributes
such as user role, resource properties, and environmental conditions. For example, a
file might be accessible only to users in the Computer Science department, but
restricted for others.

### **Accounting**

Finally, **accounting** tracks and records user and system activities. This ensures that
all actions are logged, providing critical information for auditing, billing, monitoring, and
investigating security violations. Accounting allows organizations to:

- Track user activity (e.g., login times, file access).


- Monitor resource usage.
- Investigate security incidents (e.g., unauthorized access attempts).
- Perform audits to ensure compliance with security policies.
For instance, when a user swipes their access badge at a restricted door, the system
logs the attempt, even if the user is denied entry. This log can be reviewed by a system
administrator to identify potential security breaches or misuse.

In network environments, accounting servers track data such as session start and end
times, data transfer volumes, and changes to system configurations. These records can
later be used for auditing purposes, billing, or analyzing patterns to improve security.

---

**Conclusion**

In summary, the **AAA model**—Authentication, Authorization, and Accounting—forms


the backbone of effective cybersecurity. Each component plays a crucial role in ensuring
that only authorized users and systems can access resources, while tracking and
recording all activities for accountability.

Thank you for watching, and we’ll see you in the next video as we continue our
CompTIA Security+ training.

---

This version is more structured, uses formal language, and follows a logical flow
suitable for professional video presentations. It also provides clear transitions between
topics and emphasizes the practical applications of AAA in cybersecurity.

You might also like