Please enable JavaScript.
Coggle requires JavaScript to display documents.
1 - Comparing Access Control Models - Coggle Diagram
1 - Comparing Access Control Models
Definitions
Permissions
Access granted to an object (e.g. read, write, delete, execute a file)
Rights
Ability to take an action on an object (e.g. modify the system time, restore backed-up data
Privileges
Combination of elevated rights and permissions (e.g. full privileges, granting the administrator full rights and permissions on the computer)
Authorization Mechanisms
Implicit deny
Access to an object is denied unless access has been explicitly granted to a subject
Access Control Matrix
Centralized table that includes subjects, objects, and assigned permissions, rights, and privileges
Capability list
Decentralized, distributed method of identifying permissions, rights, and privileges assigned to subjects using tokens or keys.
Constrained Interface
Restrict what users can do or see based on their privileges
Content-dependent Control
Restrict access to data based on the content within an object
Context-dependent Control
Require specific activity before granting users access (e.g. full purchase process completed before allowing payment)
Need to Know
Subjects are granted access only to what they need to know for their work tasks and job functions
Least Privilege
Subjects are granted only the privileges they need to perform their work tasks and job functions
Separation of Duties and Responsibilities
Sensitive functions are split into tasks performed by two or more employees
Access Control Models
Nondiscretionary Access Controls
Role-Based Access Control (RBAC)
Use of roles or groups
Variants: Task-Based Access Control (TBAC)
Attribute-Based Access Control (ABAC)
Use of rules that can include multiple attributes
ex: Allow managers to access the WAN using a mobile device
Mandatory Access Control (MAC) = Lattice-based model
Use of labels applied to both subjects and objects
US militiary example: top secret, secret, confidential, unclassified
Private sector example: confidential, private, sensitive and public
Implicit deny philosophy
Types of environments
Hierarchical environment
Clearance in one level grants the subject access to objects in that level as well as to all objects in lower levels but prohibits access to all objects in higher levels
Compartmentalized environement
No relationship between one security domain and another. Each represents a separate isolated compartment.
Hybrid environment
A subject must have the correct clearance and the need to know data within a specific compartment to gain access to the compartmentalized object
Risk-Based Access Control
Grant access after evaluating risk
Environment
Situation
Security policies
Rule-Based Access Control
Applies predefined global rules to all subjetcs
Ex: firewall uses rules that allow or block traffic to all users equally
Discretionary Access Control (DAC)
Every object has an owner and the owner can grant or deny access to any other subjects
Ex: ACLs