0% found this document useful (0 votes)
6 views

Access Matrix Report[1]

The Access Matrix Simulator project report outlines a security model used in operating systems to control user access to resources. It details the purpose, background, and various types of access matrix models, as well as the tools and technologies used for development. The project enables users to manage permissions dynamically and visualize access control scenarios, enhancing understanding of core operating system concepts.
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
0% found this document useful (0 votes)
6 views

Access Matrix Report[1]

The Access Matrix Simulator project report outlines a security model used in operating systems to control user access to resources. It details the purpose, background, and various types of access matrix models, as well as the tools and technologies used for development. The project enables users to manage permissions dynamically and visualize access control scenarios, enhancing understanding of core operating system concepts.
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/ 7

ACCESS MATRIX SIMULATOR

“ Operating System Project Report ”

SUBMITTED BY:

Fatima Amir (23251101025)

Maodona Akmal (23251101067)

Mehak Iqbal (23251101071)

Wajeeha Mehmood (23251101113)

SUBMITTED TO: Dr. Fahima Tahir

Section: B

Department of Computer Science (2023-2027)

Lahore College For Woman University


1. Introduction
The Access Matrix is a fundamental security model in operating systems that controls how users
(or domains) can access system resources. It defines the permissions each user has over various
resources, ensuring only authorized access is allowed.

This model helps prevent unauthorized operations by clearly specifying who can read, write, or
own resources. It also supports delegation, where users with certain rights can share them with
others securely.

The common access rights used in this project include:

• Read — Permission to view a resource


• Write — Permission to modify a resource
• Owner — Full control over the resource, including managing other users' rights
• Read* and Write* — Rights that allow delegation of read or write permissions to others.

2. Purpose
The purpose of the Access Matrix model is to provide a systematic way to define and enforce
access control in operating systems. It specifies what operations users (or domains) can perform
on system resources, such as files, devices, or data. This ensures security by preventing
unauthorized access or modifications, maintaining data integrity and confidentiality.

3. Background
In computer security, managing who can access what resource is crucial. The Access Matrix was
introduced as a flexible and intuitive model to represent the permissions of multiple users across
various resources in a matrix format. Each row corresponds to a user or domain, and each column
corresponds to a resource. The intersection cells specify the rights (like read, write, execute) that
the user holds on that resource.

This model forms the foundation for many practical access control systems, such as Access Control
Lists (ACLs) and Capability Lists. It also supports advanced features like delegation of rights,
which allows users with sufficient privileges to share their access rights with others.

4. Types of Access Matrix Models


There are several variations of the Access Matrix model used in operating systems, including:

1. Basic Access Matrix


o Lists users, resources, and their rights in a static matrix form.
o Primarily used to view and manage permissions straightforwardly.
2. Copy (Delegation) Model
o Allows users with delegation rights (read*, write*) to grant limited permissions to
others.
o Supports dynamic sharing and distribution of access rights.
3. Owner Rights Model
o Introduces the concept of an owner for each resource who has full control, including
modifying access rights and delegation privileges.
o Enhances security by centralizing control to resource owners.

5. Tools and Technologies


➢ Languages Used:

This Access Matrix Simulator is developed using:

• HTML for the webpage structure


• CSS for styling the interface
• JavaScript to implement the access control logic and dynamic interactions

➢ Libraries:

No external libraries are used; all code is written in plain JavaScript for better control and learning.

➢ Functions and their purpose:

Function Name Purpose


addUser() Adds a user/domain to the matrix
addResource() Adds a resource/file
updateSelectors() Updates dropdowns after adding new users/resources
grantPermission() Grants a permission (e.g. read, write) to a user
revokePermission() Revokes an existing permission
delegatePermission() Delegates rights from one user to another if eligible (copy control)
drawMatrix() Displays the current matrix state
checkAccess() Verifies access request against granted rights
updateSelectors() Update dropdown menus with users/resources
addResource() Add new resource and assign owner
grantPermission() Grant permission if authority permits
revokePermission() Revoke permission if authority permits
drawMatrix() Display current access matrix as a table
6. Output – Basic & Copy Access Matrix

7. Output – Access Metrix with Owner Rights


8. Testing and Scenarios
i. Basic & Copy Access Matrix

Scenario 1:

Scenario 2:
ii. Access Metrix with Owner Rights

Scenario 1:

Scenario 2:

Scenario 3:
Conclusion:
This project successfully simulates the Access Matrix model used in operating systems for
managing permissions. It was developed using HTML, CSS, and JavaScript with two main parts:

1. Basic Access Matrix with copy rights


2. Access Matrix with owner rights and delegation

Users can dynamically add domains, resources, assign permissions, and delegate rights. The
simulator allows testing different scenarios, helping visualize how access control and permission
propagation work. Overall, the project made it easier to understand core OS concepts like security,
access rights, and user-resource interaction in a hands-on and interactive way.

You might also like