Security best practices in GCP - Time & Space Complexity

Time Complexity: Security best practices

O(n)

Understanding Time Complexity

When applying security best practices in cloud setups, it's important to understand how the time to enforce these practices grows as the system scales.

We want to know how adding more resources or users affects the time spent on security operations.

Scenario Under Consideration

Analyze the time complexity of applying security policies to multiple cloud resources.

// Pseudocode for applying IAM roles to resources
for resource in resources_list:
  apply_iam_policy(resource, policy)
  verify_policy(resource)

This sequence applies and verifies a security policy on each resource in a list.

Identify Repeating Operations

Look at what repeats as the number of resources grows.

• Primary operation: Applying and verifying IAM policies on each resource.
• How many times: Once per resource in the list.

How Execution Grows With Input

As you add more resources, the number of policy applications and verifications grows directly with the number of resources.

Input Size (n)	Approx. API Calls/Operations
10	20 (apply + verify each)
100	200
1000	2000

Pattern observation: The operations increase in a straight line as resources increase.

Final Time Complexity

Time Complexity: O(n)

This means the time to apply security policies grows directly with the number of resources.

Common Mistake

[X] Wrong: "Applying security policies happens instantly no matter how many resources there are."

[OK] Correct: Each resource needs its own policy application and verification, so more resources mean more time.

Interview Connect

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

Self-Check

"What if we batch apply policies to multiple resources at once? How would the time complexity change?"

Practice

1. Which of the following is a key security best practice when managing access to Google Cloud resources?

easy

A. Give all users owner permissions for convenience

B. Assign the least privilege necessary using IAM roles

C. Share your service account keys publicly

D. Disable all logging to improve performance

Solution

1. Step 1: Understand IAM role assignment

   IAM roles control what users can do. Assigning least privilege means giving only the permissions needed.

2. Step 2: Evaluate options for security

   Giving owner permissions broadly or sharing keys publicly risks unauthorized access. Disabling logging hides important audit info.

3. Final Answer:

   Assign the least privilege necessary using IAM roles -> Option B

4. Quick Check:

   Least privilege = Assign minimal permissions [OK]

Hint: Always give only needed permissions, never more [OK]

Common Mistakes:

• Giving broad permissions for convenience
• Sharing keys or credentials publicly
• Disabling audit logs

2. Which of the following is the correct way to encrypt data in Google Cloud using Cloud KMS?

easy

A. Use Cloud KMS to generate encryption keys and encrypt data with those keys

B. Store encryption keys in plaintext in Cloud Storage

C. Encrypt data manually without using Cloud KMS

D. Disable encryption to improve speed

Solution

1. Step 1: Understand Cloud KMS role

   Cloud KMS manages encryption keys securely and helps encrypt/decrypt data safely.

2. Step 2: Evaluate encryption methods

   Storing keys in plaintext or disabling encryption risks data exposure. Manual encryption is error-prone.

3. Final Answer:

   Use Cloud KMS to generate encryption keys and encrypt data with those keys -> Option A

4. Quick Check:

   Cloud KMS = Secure key management [OK]

Hint: Always use Cloud KMS for key management and encryption [OK]

Common Mistakes:

• Storing keys unencrypted
• Skipping encryption for speed
• Encrypting data without key management

3. Consider this IAM policy snippet in JSON format:

{
  "bindings": [
    {
      "role": "roles/storage.objectViewer",
      "members": ["user:[e-mail]"]
    }
  ]
}

What permission does Alice have on the storage bucket?

medium

A. She can upload and delete objects

B. She has no access

C. She can only view objects

D. She can manage bucket settings

Solution

1. Step 1: Identify the role assigned

   The role is roles/storage.objectViewer, which grants read-only access to objects.

2. Step 2: Understand permissions of the role

   This role allows viewing objects but not uploading, deleting, or managing bucket settings.

3. Final Answer:

   She can only view objects -> Option C

4. Quick Check:

   objectViewer = read-only access [OK]

Hint: Viewer roles allow read-only access, no changes [OK]

Common Mistakes:

• Confusing viewer with editor or owner roles
• Assuming upload/delete permissions
• Ignoring role details

4. You have a service account key stored in a public GitHub repository. What is the best immediate action to secure your Google Cloud environment?

medium

A. Change the project name to confuse attackers

B. Ignore it since the key is not used

C. Share the key with your team for transparency

D. Delete the exposed key and create a new one

Solution

1. Step 1: Recognize the risk of exposed keys

   Publicly exposed keys can be used by attackers to access resources.

2. Step 2: Take immediate action to revoke and replace keys

   Deleting the exposed key and creating a new one prevents unauthorized access.

3. Final Answer:

   Delete the exposed key and create a new one -> Option D

4. Quick Check:

   Exposed keys = revoke immediately [OK]

Hint: Revoke exposed keys immediately to prevent breaches [OK]

Common Mistakes:

• Ignoring exposed keys
• Changing unrelated settings
• Sharing keys openly

5. You want to enforce that all data stored in Cloud Storage buckets is encrypted with customer-managed keys (CMKs) using Cloud KMS. Which combination of steps ensures this security best practice?

hard

A. Create a Cloud KMS key ring and key, then configure the bucket to use this key for default encryption

B. Store keys in a Compute Engine instance and manually encrypt files before upload

C. Use Google-managed encryption only and disable Cloud KMS

D. Encrypt files locally and upload without bucket encryption settings

Solution

1. Step 1: Create a Cloud KMS key ring and key

   This provides a customer-managed key to control encryption.

2. Step 2: Configure the Cloud Storage bucket to use the CMK for default encryption

   This ensures all objects are encrypted automatically with your key.

3. Final Answer:

   Create a Cloud KMS key ring and key, then configure the bucket to use this key for default encryption -> Option A

4. Quick Check:

   CMK + bucket default encryption = secure data [OK]

Hint: Use CMK with bucket default encryption for strong control [OK]

Common Mistakes:

• Relying only on Google-managed keys
• Encrypting manually without bucket settings
• Storing keys insecurely