Security design patterns in Cybersecurity - Time & Space Complexity

Time Complexity: Security design patterns

O(n)

Understanding Time Complexity

When using security design patterns, it is important to understand how the time needed to enforce security grows as the system handles more data or users.

We want to know how the cost of applying these patterns changes when the input size increases.

Scenario Under Consideration

Analyze the time complexity of the following authentication check pattern.

function authenticate(user, password) {
  if (!userExists(user)) {
    return false;
  }
  let storedHash = getPasswordHash(user);
  return verifyPassword(password, storedHash);
}
    

This code checks if a user exists, retrieves the stored password hash, and verifies the password.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Searching for the user in the user database.
• How many times: Once per authentication attempt, but the search may scan many users depending on data structure.

How Execution Grows With Input

As the number of users grows, the time to find a user may increase.

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

Pattern observation: The time grows roughly in direct proportion to the number of users if a simple search is used.

Final Time Complexity

Time Complexity: O(n)

This means the time to authenticate grows linearly as the number of users increases.

Common Mistake

[X] Wrong: "Authentication time stays the same no matter how many users there are."

[OK] Correct: If the user search is done by scanning a list, more users mean more checks, so time grows with user count.

Interview Connect

Understanding how security checks scale helps you design systems that stay fast and safe as they grow, a key skill in real-world security work.

Self-Check

"What if we changed the user storage from a list to a hash map? How would the time complexity change?"

Practice

1. Which of the following best describes the purpose of security design patterns?

easy

A. They are ways to reduce software file size.

B. They provide proven solutions to common security problems in software design.

C. They are methods to increase software user interface appeal.

D. They are tools used to write faster code.

Solution

1. Step 1: Understand the role of security design patterns

   Security design patterns are established methods to solve security challenges in software development.

2. Step 2: Compare options with this understanding

   Only They provide proven solutions to common security problems in software design. correctly states that these patterns provide proven security solutions, while others focus on unrelated aspects.

3. Final Answer:

   They provide proven solutions to common security problems in software design. -> Option B

4. Quick Check:

   Security design patterns = proven security solutions [OK]

Hint: Security patterns solve security issues, not UI or speed [OK]

Common Mistakes:

• Confusing security patterns with UI design methods
• Thinking they improve software speed
• Assuming they reduce file size

2. Which of the following is a correct example of the 'Least Privilege' security design pattern?

easy

A. Giving users only the access rights they need to perform their tasks.

B. Allowing all users full access to all system resources.

C. Sharing passwords among team members for convenience.

D. Disabling all security checks to speed up processing.

Solution

1. Step 1: Define the 'Least Privilege' pattern

   This pattern means users get only the minimum access needed to do their job.

2. Step 2: Match options to this definition

   Giving users only the access rights they need to perform their tasks. matches perfectly; others contradict security principles.

3. Final Answer:

   Giving users only the access rights they need to perform their tasks. -> Option A

4. Quick Check:

   Least Privilege = minimal necessary access [OK]

Hint: Least Privilege means minimal access only [OK]

Common Mistakes:

• Thinking least privilege means full access
• Believing password sharing is secure
• Ignoring security checks for speed

3. Consider this code snippet implementing an Access Control pattern:

user_role = 'guest'
if user_role == 'admin':
    access = 'full'
elif user_role == 'user':
    access = 'partial'
else:
    access = 'none'
print(access)

What will be the output?

medium

A. full

B. error

C. partial

D. none

Solution

1. Step 1: Analyze the user_role value

   The variable user_role is set to 'guest', which does not match 'admin' or 'user'.

2. Step 2: Follow the conditional logic

   Since 'guest' matches none of the first two conditions, the else block runs, setting access to 'none'.

3. Final Answer:

   none -> Option D

4. Quick Check:

   guest role leads to no access = none [OK]

Hint: Check which condition matches the role first [OK]

Common Mistakes:

• Assuming 'guest' gets partial access
• Confusing elif with else
• Expecting an error due to missing role

4. A developer wrote this code to enforce the 'Fail-Safe Defaults' pattern:

def check_access(user):
    if user == 'admin':
        return True
    elif user == 'guest':
        return False
    # Missing return for other users

What is the main problem with this code?

medium

A. It uses incorrect syntax for the function.

B. It grants access to all users by default.

C. It does not deny access by default for unknown users.

D. It returns True for guests.

Solution

1. Step 1: Understand 'Fail-Safe Defaults'

   This pattern means access should be denied unless explicitly allowed.

2. Step 2: Check the function's return paths

   The function returns True for 'admin', False for 'guest', but returns nothing (None) for others, which may be treated as allowed or cause errors.

3. Final Answer:

   It does not deny access by default for unknown users. -> Option C

4. Quick Check:

   Fail-Safe Defaults = deny unless allowed [OK]

Hint: Always deny access if user unknown [OK]

Common Mistakes:

• Assuming missing return means deny
• Thinking syntax is wrong
• Confusing guest access rights

5. You want to design a system that limits user actions based on their roles and ensures no user can access data beyond their permissions. Which combination of security design patterns should you apply?

hard

A. Least Privilege and Role-Based Access Control (RBAC)

B. Fail-Safe Defaults and Password Sharing

C. Open Access and Least Privilege

D. Full Access and Security through Obscurity

Solution

1. Step 1: Identify patterns that limit user actions by role

   Role-Based Access Control (RBAC) assigns permissions based on user roles, controlling access effectively.

2. Step 2: Ensure minimal permissions with Least Privilege

   Least Privilege ensures users get only the access they need, preventing excess permissions.

3. Final Answer:

   Least Privilege and Role-Based Access Control (RBAC) -> Option A

4. Quick Check:

   Limit actions by role + minimal access = A [OK]

Hint: Combine role control with minimal access [OK]

Common Mistakes:

• Choosing insecure patterns like password sharing
• Confusing open access with security
• Relying on obscurity instead of control