Module7 (1)
Module7 (1)
This
lesson covers the following topics:
• Access control
• Authentication, authorization, and accounting
• Access control policies
• Access control Models
Lesson Proper:
Access control is the ability to permit or deny the privileges that a user has when accessing resources on a
network or computer. Access control involves three entities:
Objects are passive entities that contain or receive information. These are the resources or assets
that need to be protected.
Subjects are active entities that request access to resources. Typically, subjects are users or
processes acting on behalf of users.
• The access control system includes policies, procedures, and technologies that are implemented to
control subjects' access to objects.
Access control rules or policies are the set of guidelines or criteria that determine the level of access subjects
have to objects. These rules are often defined by the organization’s security policy.
• Identification specifies the name used to identify the subject. Examples include a user name or a user
ID number.
• Authentication is the process of validating a subject's identity. It includes the identification process, the
user providing input to prove identity, and the system accepting that input as valid.
• Authorization is granting or denying an authenticated subject's access to an object based on the
subject's level of permissions or the actions allowed with the object.
• Auditing, also referred to as accounting, is maintaining a record of a subject's activity within the
information system.
An access control policy defines the steps and measures that are taken to control subjects' access to objects.
Access controls can be classified according to the function they perform:
• Preventive access controls deter intrusion or attacks. These include separation of duties and dual-
custody processes.
Preventive access controls are security measures designed to stop unauthorized access to systems,
data, or physical locations before any breach or damage occurs. These controls aim to reduce the
likelihood of a security incident by enforcing rules and restrictions proactively.
• Detective access controls search for details about the attack or the attacker. These include intrusion
detection systems.
Detective access controls are security measures that are designed to identify and alert when
unauthorized access or suspicious activity has already occurred or is happening. They do not stop the
activity, but they help in detecting incidents, gathering evidence, and triggering responses.
• Corrective access controls implement short-term repairs to restore basic functionality following an
attack.
Corrective access controls are security measures designed to respond to and fix issues after a
security incident or unauthorized access has been detected. Their main goal is to restore systems back to
normal, minimize damage, and prevent recurrence.
Deterrent access controls are security measures intended to discourage or deter potential attackers
or unauthorized users from attempting to access a system, area, or data. These controls don't actively
block access, but they serve as a psychological or visible warning that security measures are in place and
consequences will follow.
• Recovery access controls restore the system to normal operations after the attack and the short-term
stabilization period.
Recovery access controls are security measures designed to restore systems, data, and operations
after a major security incident, disaster, or failure. They go beyond just fixing the immediate issue (like
corrective controls) — their focus is on getting the system fully operational again, often after severe
disruptions.
Compensative (or Compensating) access controls are alternative security measures put in place to
satisfy the requirements of a primary control that cannot be implemented due to practical limitations, such
as cost, system compatibility, or organizational constraints.
These controls do not replace the original control but instead provide an equivalent level of security to
reduce risk.
Access control measures can also be classified based on how they restrict or control access:
• Administrative controls (also called managerial controls) are policies, procedures, and
guidelines created by management to influence how access to systems, data, and resources is
handled. They focus on people and processes, not technology or hardware.
They are policies that describe accepted practices. Examples include directive policies and employee
awareness training.
• Technical controls (also called logical controls) are security measures implemented through
hardware, software, or system configurations to protect digital resources and manage access.
These controls focus on automating security enforcement using technology. They are computer
mechanisms that restrict access. Examples include encryption, one-time passwords, access control
lists, and firewall rules.
• Physical controls are security measures designed to prevent unauthorized physical access to
facilities, equipment, or information. These controls are tangible protections that secure the physical
environment of an organization. These also restrict physical access. Examples include perimeter
security, site location, networking cables, and employee segregation.
On a computer network, a directory service is an example of a technical access control system that you use to
manage and enforce access control policies. Within the directory service:
Access control best practices take into consideration the following security principles and concepts:
Principle Description
Principle of least The principle of least privilege states that users or groups are given only the
privilege access they need to do their jobs and nothing more. Common methods of
controlling access include:
• Implicit deny denies access to users or groups who are not specifically
given access to a resource. Implicit deny is the weakest form of privilege
control.
• Explicit allow specifically identifies users or groups who have access.
Explicit allow is a moderate form of access control in which privilege has
been granted to a subject.
• Explicit deny identifies users or groups who are not allowed access.
Explicit deny is the strongest form of access control and overrules all
other privileges granted.
When assigning privileges, be aware that it is often easier to give a user more
access when the user needs it than to take away privileges that have already
been granted. Access recertification is the process of continually reviewing a
user's permissions and privileges to make sure the user has the correct level of
access.
Need to know Need to know describes the restriction of data that is highly sensitive and is
usually referenced in government and military context. Important facts about the
need to know include:
Separation of Separation of duties is the concept of having more than one person required to
duties complete a task. This is a preventive principle primarily designed to reduce
conflicts of interest. It also prevents insider attacks because no one person has
end-to-end control and no one person is irreplaceable. Important facts to know
about separation of duties include:
• System users should have the lowest level of rights and privileges
necessary to perform their work and should have those privileges only for
the shortest length of time possible.
Principle Description
Job rotation Job rotation is a technique where users are cross-trained in multiple job positions.
Responsibilities are regularly rotated between personnel. Job rotation:
Identification Identification is the act of claiming an identity, such as telling someone your
name. Important facts to know about identification include:
Multi-Factor Multi-Factor Authentication is the process of using more than one way to verify
Authentication identity. In the computer world, Multi-Factor Authentication is achieved by
requiring two or more methods that only the user can provide. Five categories of
computer system authentication include:
Organizations should follow strict guidelines when an employee transitions out of a position or into a new
position.
Creeping privileges occur when a user's job position changes and the user is granted a new set of access
privileges, but the user's current access privileges are not removed or modified, resulting in privilege
escalation. As a result, the user accumulates privileges that are not necessary for the current work tasks. The
principle of least privilege and separation of duties are countermeasures against creeping privileges.
To avoid creeping privileges and to best protect the security of information, the following precautions should
be taken in each stage of the account's life cycle:
Event Precautions
Account When an account is created, apply the appropriate access rights based on the job role
creation as implemented in the access control system. Use the principle of least privilege and
grant only the minimum privileges required to perform the duties of the position.
Old accounts When an account is no longer needed, take appropriate actions to:
Access control is the process by which resource and service use is granted or denied. The following table lists
the most commonly used access control models, also known as access control schemes.
Model Description
Role-based access Role-based access control allows access based on a role in an organization; it is
control not user specific. Role-based access control is also known as non-discretionary
(RBAC) access control.
Rule-based access Rule-based access control uses rules applied to characteristics of objects or
control subjects to restrict access.
Mandatory access Mandatory access control uses labels for both subjects (users who need access)
control (MAC) and objects (resources with controlled access, such as data, applications,
systems, networks, and physical space). Every operation performed is tested
against a set of authorization policies to determine if the operation is allowed.
Discretionary Discretionary access control assigns access directly to subjects based on the
access control owner's discretion.
(DAC)
• Objects have a discretionary access control list (DACL) with entries for
each subject.
• Owners add subjects to the DACL and assign rights or permissions. The
permissions identify the actions the subject can perform on the object.
• With discretionary access control, subjects can pass permissions on to
other subjects.
Model Description
Learning Outcomes:
Configure user accounts and permissions on a local system.
Apply and test access control models such as Role-Based Access Control (RBAC) and Discretionary Access
Control (DAC).
Identify potential vulnerabilities in access control configurations and recommend improvements.
Instructions
Part 1: Preparation
1. Use a personal computer running an operating system with built-in access control features (Windows or
macOS).
2. Create folders or directories representing sensitive data (e.g., “Confidential Files,” “Public Files”).
3. Set up multiple user accounts (e.g., Admin, Manager, Employee).
Example setup:
Admin: Full control over all folders.
Manager: Read/Write access to “Confidential Files,” no access to “Admin Files.”
Employee: Read-only access to “Public Files.”
1. Log in to each user account and attempt actions such as creating, modifying, or deleting files in restricted
folders.
2. Document observed behavior (e.g., access denied, permissions error).
Analyzing Security
1. Introduce a hypothetical issue by incorrectly configuring permissions (e.g., granting Employee write
access to “Confidential Files”).
2. Test the impact of the issue and resolve it by restoring appropriate permissions.
Report:
Discussion Questions:
- Tools/Software Required:
A personal computer with a built-in file system and user account management features.
Text editor for documentation (e.g., Notepad, Word).
Estimated Time: 2-3 hours
- Submit the report with:
• Step-by-step documentation.
• Screenshots of configurations and tests.
• Answers to reflection and discussion questions.
Laboratory Rubric (Total: 50 points)
Criteria Excellent (5 pts) Good (4 pts) Fair (3 pts) Needs Improvement
(1-2 pts)
1. User Accounts Created 3 user accounts Created 2-3 accounts with Created only 1 Accounts missing or
Creation correctly with clearly minor role errors. account correctly; improperly set up.
defined roles. others unclear.
2. Folder Setup Correct folders created and Folders created but minor Some folders Folders not properly
well-organized. naming/organization issues. missing or created.
disorganized.
3. Permission Assigned correct Assigned permissions but Attempted Permissions
Configuration permissions to each with minor errors. permissions setup improperly assigned
account precisely. but multiple errors. or missing.
4. Access Testing Thoroughly tested all user Tested most actions; Some testing done; Little to no testing
actions; documented documentation mostly results incomplete. done or poorly
outcomes fully. clear. documented.
5. Documentation Steps clearly and logically Steps mostly clear with Steps provided but Steps missing or very
of Steps explained with full details. minor missing info. confusing or unclear.
incomplete.
6. Screenshots Screenshots fully support Most screenshots included Few screenshots Very few or no
the documentation and but minor missing provided; screenshots
show all steps/results. elements. incomplete view. provided.
7. Issue Clearly introduced an Error introduced with minor Error introduced but No error introduced
Introduction access control error and clarity issues. poorly explained. or poorly done.
described it well.
8. Issue Testing & Accurately tested and Tested and corrected with Testing or correction No proper testing or
Resolution corrected the introduced minor mistakes. attempted but correction shown.
issue. incomplete.
9. Reflection on Strong analysis of risks Good analysis but missing Basic risk Risks vaguely or not
Risks with examples. examples. identification with discussed.
limited insight.
10. Answers to All questions answered Questions answered, some Answers provided Incomplete or
Discussion insightfully and thoroughly. minor gaps. but lack depth. shallow answers.
Questions