Security best practices in GCP - Commands & Configuration

Introduction

Security best practices help protect your cloud resources from unauthorized access and data leaks. They guide you to set up safe access controls and keep your data private and secure.

When you want to control who can access your cloud storage buckets to keep data safe.

When you need to give temporary access to a developer without sharing permanent credentials.

When you want to encrypt sensitive data stored in your cloud databases.

When you want to monitor and log access to your cloud resources for auditing.

When you want to avoid exposing your cloud services to the public internet unnecessarily.

Commands

This command gives Alice read-only access to the project, following the principle of least privilege.

Terminal

gcloud projects add-iam-policy-binding example-project --member='user:[e-mail]' --role='roles/viewer'

Expected Output

Updated IAM policy for project [example-project].

→

--member - Specifies the user or service account to grant the role.

→

--role - Specifies the exact role to assign, limiting permissions.

Creates a Cloud KMS key to encrypt sensitive data, ensuring data is protected at rest.

Terminal

gcloud kms keys create my-key --location=us-east1 --keyring=my-keyring --purpose=encryption

Expected Output

Created key [my-key].

→

--location - Specifies the region for the key.

→

--purpose - Defines the key's use, here for encryption.

Creates a logging sink to export logs from Compute Engine instances to a storage bucket for auditing.

Terminal

gcloud logging sinks create my-sink storage.googleapis.com/my-logs-bucket --log-filter='resource.type=gce_instance'

Expected Output

Created sink [my-sink].

→

--log-filter - Filters logs to only include those from specific resources.

Creates a firewall rule to deny all incoming traffic from internal IP ranges, reducing attack surface.

Terminal

gcloud compute firewall-rules create deny-internal --direction=INGRESS --priority=1000 --network=default --action=DENY --rules=all --source-ranges=10.128.0.0/9

Expected Output

Creating firewall rule...done.

→

--direction - Sets the traffic direction the rule applies to.

→

--action - Defines whether to allow or deny the traffic.

Key Concept

If you remember nothing else from this pattern, remember: always grant the minimum permissions needed and protect data with encryption and monitoring.

Common Mistakes

Granting broad roles like 'owner' to users who only need to view resources.

This gives users more access than necessary, increasing security risks.

Assign specific roles like 'viewer' or 'editor' based on actual needs.

Not enabling logging or exporting logs for auditing.

Without logs, you cannot track who accessed or changed resources, making it hard to detect breaches.

Set up logging sinks to export logs to secure storage for review.

Leaving firewall rules open to all IP addresses by default.

This exposes services to the internet, increasing chances of attacks.

Restrict firewall rules to only allow trusted IP ranges or internal networks.

Summary

Use IAM roles to give users only the permissions they need.

Encrypt sensitive data using Cloud KMS keys.

Set up logging sinks to monitor access and changes.

Create firewall rules to limit network access.

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