ACCESS CONTROL
Introduction to Access Control
• Access control is a theoretical yet operating system-related concept.
• It revolves around the question of who can access certain resources.
Fundamental Concepts
• Subject/Principal: Active entities such as users or processes.
• Object: Passive entities like files or resources.
• Access Operations: Include read, write, and others, varying across systems.
Authorization
• Access control decisions are essentially authorization decisions.
• To authorize access to an object implies determining who is permitted to access it.
Analogy for Access Control
• Imagine an office where certain documents can only be accessed by specific individuals.
• Implementation involves filing cabinets (objects) and keys (access rights) issued to
individuals (subjects).
Focus of Control
• Access control can focus on either the subject or the object.
• Multi-user operating systems typically manage objects (files), whereas application-oriented
systems, like database management systems (DBMSs), manage actions of subjects.
Elementary Access Operations
• Basic operations include:
o Observe: Reading or viewing an object.
o Alter: Modifying an object.
• Bell-LaPadula Model (BLP) establishes four access rights: execute, read, append (blind
write), and write.
UNIX Access Control
• In UNIX, access control relies on three operations:
o Read: Accessing file information.
o Write: Modifying file contents.
o Execute: Running a file.
• Access roles differ when applied to directories compared to files.
Windows NT Access Control
• Permissions can include more operations than UNIX, such as:
o Delete: Removing files
o Change Permission: Modifying permissions and ownership.
• Grant/Revoke versus Assert/Deny for access manipulation.
Ownership in Access Control
• Ownership impacts access control rules; typically, the creator of an object becomes its
owner.
Policy Setting
• Resource owners dictate access policies (discretionary), while system-wide policies
determine access (mandatory).
Access Control Structures
• Effective access control structures must:
o Express desired access control policy.
o Allow verification that policies are correctly implemented.
• Individual access rights can become complex with numerous subjects and objects,
necessitating intermediate control levels.
Access Control Matrix
• Denoted as M where M = (Mso)s∈S, o∈O, it specifies operations subjects can perform on
objects.
• Management of large matrices (thousands of files/users) is challenging and often
inefficient.
Capabilities and Access Control Lists (ACLs)
• Capabilities: Rights are stored with subjects (rows of the access matrix).
• ACLs: Rights linked to objects (columns of the access matrix), often involving groups of
users.
Aggregation Techniques
• Utilize concepts like groups, roles, and procedures to manage access efficiently.
Role-Based Access Control (RBAC)
• Roles are assigned to subjects which entail certain permissions and access methods
(procedures) for data types.
• Example roles may include Teller, Clerk, Administrator in a banking system.
Security Labels and Partial Orderings
• Use of security labels to manage access control based on security levels, employing a
structure known as partial ordering.
• Properties of partial ordering include reflexivity, transitivity, and antisymmetry.
Bell-LaPadula Model
• A key access control model focusing on confidentiality through information flow policies,
where read/write assessments depend on security labels.
o Read Access: Granted if the subject's label is equal to or higher than that of the
object.
o Write Access: Granted if the subject’s label is lower than that of the object.
Security Theorem in BLP
• A state is secure if all access tuples (subject, object, operation) comply with the BLP
properties.
• Ensures that transitioning from one state to another maintains security.
Harrison-Ruzzo-Ullman Model
• Extends BLP to include operations for modifying access rights and encompasses a model to
manipulate the access matrix, involving operations like create and delete.
Access Control - Note Reviewer
Key Terms and Definitions
1. Access Control - A security technique that regulates who or what can view or use
resources in a computing environment.
2. Authentication - The process of verifying the identity of a user, system, or device.
3. Authorization - The process of granting or denying access to resources based on a user's
identity.
4. Access Control List (ACL) - A list that defines permissions associated with specific users or
system processes.
5. Role-Based Access Control (RBAC) - A security model that assigns permissions to users
based on their role within an organization.
6. Mandatory Access Control (MAC) - A strict security model where access permissions are
predefined and controlled by a central authority.
7. Discretionary Access Control (DAC) - A model where the resource owner determines
access permissions.
8. Multi-Factor Authentication (MFA) - An authentication method requiring two or more
verification factors to gain access.
9. Single Sign-On (SSO) - A user authentication process that allows access to multiple
applications with a single set of credentials.
10. Principle of Least Privilege (PoLP) - A security concept where users are given the minimum
levels of access necessary to perform their tasks.
11. Separation of Duties (SoD) - A security principle that prevents a single individual from
having control over all aspects of a critical process.
12. Access Control Policy - A set of rules that define how access to resources is managed and
enforced.
13. Identity and Access Management (IAM) - A framework for ensuring that the right
individuals have access to the right resources at the right time.
14. Biometric Authentication - Security authentication based on unique biological
characteristics like fingerprints, retina scans, or facial recognition.
15. Token-Based Authentication - An authentication method that uses a cryptographic token
for user identity verification.
16. Federated Identity Management (FIM) - A system that allows users to access multiple
services using a single identity across different organizations.
17. Zero Trust Model - A security framework that assumes no entity should be trusted by
default, even inside the network.
18. Time-Based Access Control - Restricts access based on specific time windows.
19. Attribute-Based Access Control (ABAC) - A dynamic security model that evaluates
attributes (e.g., department, location, device) to grant access.
20. Access Control Models - Frameworks that dictate how access permissions are granted
and enforced.
Important Concepts to Remember
• Types of Access Control Models:
o Mandatory Access Control (MAC): Government and military use this strict model.
o Discretionary Access Control (DAC): Common in commercial systems; flexible
but risky.
o Role-Based Access Control (RBAC): Assigns permissions based on job roles.
o Attribute-Based Access Control (ABAC): Grants access based on user,
environment, and resource attributes.
• Key Differences:
o MAC vs. DAC: MAC is rigid and centrally controlled, whereas DAC gives resource
owners more flexibility.
o RBAC vs. ABAC: RBAC is predefined based on roles, while ABAC is more dynamic
and context-aware.
• Authentication vs. Authorization:
o Authentication verifies "who you are."
o Authorization defines "what you can do."
• Access Control Mechanisms:
o Physical Controls: Security guards, keycards, biometric scanners.
o Administrative Controls: Policies, training, audits.
o Technical Controls: Firewalls, encryption, access control lists.
• Best Practices:
o Implement Multi-Factor Authentication (MFA) to strengthen authentication.
o Apply the Principle of Least Privilege (PoLP) to minimize security risks.
o Enforce Separation of Duties (SoD) to prevent fraud or unauthorized changes.
o Regularly review and update Access Control Policies to stay compliant.
o Use Federated Identity Management (FIM) for seamless user authentication
across multiple systems.
• Threats to Access Control:
o Insider Threats: Employees misusing access privileges.
o Brute Force Attacks: Automated attempts to guess login credentials.
o Phishing Attacks: Deceptive emails or messages tricking users into revealing
credentials.
o Man-in-the-Middle (MitM) Attacks: Attackers intercept communication to gain
unauthorized access.
• Zero Trust Model Principles:
o Verify every request, regardless of the source.
o Implement least privilege access.
o Continuously monitor access patterns and behaviors.