File permissions and access control in Cybersecurity - Time & Space Complexity

Time Complexity: File permissions and access control

O(n)

Understanding Time Complexity

When checking file permissions and access control, the system must verify who can do what with a file.

We want to understand how the time to check permissions grows as the number of users or rules increases.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Simplified permission check
function checkAccess(user, file) {
  for (let rule of file.accessRules) {
    if (rule.user === user) {
      return rule.permission;
    }
  }
  return 'no access';
}
    

This code checks each access rule for a file to find if the user has permission.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through the list of access rules for the file.
• How many times: Up to the number of rules, until a match is found or all rules are checked.

How Execution Grows With Input

As the number of access rules grows, the time to check permissions grows roughly the same way.

Input Size (n)	Approx. Operations
10	Up to 10 checks
100	Up to 100 checks
1000	Up to 1000 checks

Pattern observation: The time grows directly with the number of rules; doubling rules roughly doubles the checks.

Final Time Complexity

Time Complexity: O(n)

This means the time to check permissions grows linearly with the number of access rules.

Common Mistake

[X] Wrong: "Checking permissions is always instant regardless of rules."

[OK] Correct: The system must look through rules one by one, so more rules mean more time needed.

Interview Connect

Understanding how permission checks scale helps you explain system behavior and design efficient access control.

Self-Check

"What if the access rules were stored in a hash map instead of a list? How would the time complexity change?"

Practice

1. What does the read permission allow a user to do with a file?

easy

A. Modify the contents of the file

B. View the contents of the file

C. Execute the file as a program

D. Delete the file

Solution

1. Step 1: Understand the meaning of read permission

   The read permission allows a user to open and see the contents of a file without changing it.

2. Step 2: Compare with other permissions

   Write permission allows changes, execute allows running the file, and delete is a separate action.

3. Final Answer:

   View the contents of the file -> Option B

4. Quick Check:

   Read permission = View file contents [OK]

Hint: Read means viewing file contents only [OK]

Common Mistakes:

• Confusing read with write permission
• Thinking read allows file execution
• Assuming read allows file deletion

2. Which of the following is the correct symbolic notation for giving the owner execute permission on a file in Unix/Linux?

easy

A. u+x

B. g+x

C. o+x

D. a+x

Solution

1. Step 1: Understand symbolic notation for permissions

   In Unix/Linux, 'u' stands for user (owner), 'g' for group, 'o' for others, and 'a' for all.

2. Step 2: Identify execute permission addition

   Adding execute permission is done with '+x'. So 'u+x' means add execute for owner.

3. Final Answer:

   u+x -> Option A

4. Quick Check:

   Owner execute permission = u+x [OK]

Hint: u means owner; +x adds execute permission [OK]

Common Mistakes:

• Using g+x or o+x for owner permissions
• Confusing a+x with owner only
• Misunderstanding symbolic letters

3. Given the file permission string -rwxr-x---, which users can execute the file?

medium

A. Owner and group members

B. Only the owner

C. Everyone

D. Only others

Solution

1. Step 1: Break down the permission string

   The string '-rwxr-x---' means: owner has read, write, execute; group has read and execute; others have no permissions.

2. Step 2: Identify who can execute

   Owner (rwx) can execute, group (r-x) can execute, others (---) cannot.

3. Final Answer:

   Owner and group members -> Option A

4. Quick Check:

   Execute permission for owner and group [OK]

Hint: Look for 'x' in owner and group parts [OK]

Common Mistakes:

• Ignoring group execute permission
• Assuming others have execute
• Misreading permission string

4. A user tries to write to a file but gets a 'Permission denied' error. The file permissions are -rw-r--r--. What is the most likely cause?

medium

A. User has execute permission but not write

B. File is read-only for everyone

C. User is not the owner and has no write permission

D. File is locked by another process

Solution

1. Step 1: Analyze the permission string

   '-rw-r--r--' means owner can read and write; group and others can only read.

2. Step 2: Understand user's permission

   If the user is not the owner, they only have read permission, so writing is denied.

3. Final Answer:

   User is not the owner and has no write permission -> Option C

4. Quick Check:

   Write denied if not owner with write permission [OK]

Hint: Write permission only for owner here [OK]

Common Mistakes:

• Assuming read means write allowed
• Confusing execute with write permission
• Ignoring ownership in permissions

5. You want to allow a group of users to read and execute a script but prevent them from modifying it. Which permission setting should you apply?

hard

A. Set group permissions to ---

B. Set group permissions to rw-

C. Set group permissions to rwx

D. Set group permissions to r-x

Solution

1. Step 1: Understand required permissions

   Users need to read and execute but not write (modify) the script.

2. Step 2: Match permissions to requirements

   'r-x' means read and execute allowed, write denied. 'rw-' allows write, 'rwx' allows all, '---' denies all.

3. Final Answer:

   Set group permissions to r-x -> Option D

4. Quick Check:

   Read + execute, no write = r-x [OK]

Hint: r-x means read and execute, no write [OK]

Common Mistakes:

• Choosing rw- which allows writing
• Choosing rwx which allows all permissions
• Choosing --- which denies access