Why Security best practices in GCP? - Purpose & Use Cases

The Big Idea

What if a simple mistake could let strangers into your cloud? Learn how to stop that before it happens.

The Scenario

Imagine you have a big office building with many rooms and valuable items. You try to keep it safe by asking everyone to remember which doors to lock and which keys to use. But you don't have a clear system or rules, so sometimes doors are left open or keys get lost.

The Problem

Doing security by hand is slow and confusing. People forget steps, make mistakes, or share keys with the wrong people. This can let strangers in or cause important data to be lost or stolen. Fixing these problems after they happen is costly and stressful.

The Solution

Security best practices give you clear, simple rules and tools to protect your cloud resources automatically. They help you control who can access what, keep secrets safe, and watch for unusual activity. This way, your cloud environment stays safe without extra work or worry.

Before vs After

✗ Before

Open all ports, share passwords by email, no user roles

✓ After

Use firewall rules to limit ports, store secrets in Secret Manager, assign roles with IAM

What It Enables

It lets you build cloud systems that are safe by design, so you can focus on your work without fearing security breaches.

Real Life Example

A company uses security best practices to give each employee access only to the tools they need. When someone leaves, their access is removed instantly, keeping the company data safe.

Key Takeaways

Manual security is risky and hard to manage.

Best practices automate protection and control access.

Following them keeps your cloud safe and your mind at ease.

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