GSP1125

Overview

Event Threat Detection is an integrated service of Security Command Center (SCC) that monitors Google Cloud logs for patterns signaling suspicious activities.

Container Threat Detection is another integrated service of SCC. This service can continuously monitor GKE working nodes. When it detects suspicious events, it analyzes them to confirm whether they can be treated as incidents or not.

In this lab, you receive hands-on practice with SCC's threat detection features and learn how to investigate and triage common vulnerabilities associated with events and virtual machines. You learn how to surface and manage your findings with SCC's Event Threat Detection features.

Objectives

In this lab, you learn how to perform the following tasks:

• Initiate and mitigate a threat with Event Threat Detection.
• Configure a cloud environment to detect threats.
• Manage SCC findings with Event Threat Detection.

Prerequisites

It is recommended that you are familiar with the following before starting this lab:

• Cloud computing concepts.
• The Google Cloud console.
• The Security Command Center interface.
• Containers and Google Kubernetes Engine (this is recommended, but not required).

Setup and requirements

Before you click the Start Lab button

Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources will be made available to you.

This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials that you use to sign in and access Google Cloud for the duration of the lab.

To complete this lab, you need:

• Access to a standard internet browser (Chrome browser recommended).

Note: Use an Incognito or private browser window to run this lab. This prevents any conflicts between your personal account and the Student account, which may cause extra charges incurred to your personal account.

• Time to complete the lab---remember, once you start, you cannot pause a lab.

Note: If you already have your own personal Google Cloud account or project, do not use it for this lab to avoid extra charges to your account.

How to start your lab and sign in to the Google Cloud console

1. Click the Start Lab button. If you need to pay for the lab, a pop-up opens for you to select your payment method. On the left is the Lab Details panel with the following:

   • The Open Google Cloud console button
   • Time remaining
   • The temporary credentials that you must use for this lab
   • Other information, if needed, to step through this lab

2. Click Open Google Cloud console (or right-click and select Open Link in Incognito Window if you are running the Chrome browser).

   The lab spins up resources, and then opens another tab that shows the Sign in page.

   Tip: Arrange the tabs in separate windows, side-by-side.

   Note: If you see the Choose an account dialog, click Use Another Account.

3. If necessary, copy the Username below and paste it into the Sign in dialog.

   {{{user_0.username | "Username"}}}

   You can also find the Username in the Lab Details panel.

4. Click Next.

5. Copy the Password below and paste it into the Welcome dialog.

   {{{user_0.password | "Password"}}}

   You can also find the Password in the Lab Details panel.

6. Click Next.

   Important: You must use the credentials the lab provides you. Do not use your Google Cloud account credentials. Note: Using your own Google Cloud account for this lab may incur extra charges.

7. Click through the subsequent pages:

   • Accept the terms and conditions.
   • Do not add recovery options or two-factor authentication (because this is a temporary account).
   • Do not sign up for free trials.

After a few moments, the Google Cloud console opens in this tab.

Note: To view a menu with a list of Google Cloud products and services, click the Navigation menu at the top-left.

Scenario

Cymbal Bank is an American retail bank with over 2,000 branches in all 50 states. It offers comprehensive debit and credit services that are built on top of a robust payments platform. Cymbal Bank is a digitally transforming legacy financial services institution.

Cymbal Bank was founded in 1920 under the name Troxler. Cymbal Group acquired the company in 1975 after it had been investing heavily in Cymbal Group's proprietary ATMs. As the bank grew into a national leader, they put strategic emphasis on modernizing the customer experience both in-person at their branches and digitally through an app they released in 2014. Cymbal Bank employs 42,000 people nationwide and, in 2019, reported $24 billion in revenue.

As a Cloud Security Engineer at Cymbal Bank, your task is to explore and implement robust security measures, leveraging Security Command Center's Event and Container Threat Detection capabilities for its Google Cloud resources. By integrating these services, you can ensure real-time monitoring, swift anomaly identification, and proactive vulnerability management for the event-driven architectures and containerized applications.

Enable the Security Command Center API

1. Click on the Navigation menu in the top left corner of the Google Cloud console.

2. Select APIs & Services from the drop down and click on Enable APIs & Services.

3. Click + Enable APIs & Services

4. Search for Security Command Center API in the search box.

5. Click on Security Command Center API, then click Enable

Task 1. Initiate and mitigate a threat with Event Threat Detection

Your first task as a Cloud Security Engineer for Cymbal Bank is to initiate and mitigate non-compliant accounts threats with Event Threat Detection.

The Event Threat Detection service of SCC detects many threats by monitoring suspicious activities reported in Google Cloud logs. One of these activities might be delegating sensitive roles to an external user, such as someone who has a miscellaneous gmail.com account that isn't tied to your corporate domain.

This might happen in situations when an intruder has managed to access a GCP organization and now they are interested in establishing persistence. To do this, the hacker would grant sensitive roles to their @gmail.com account.

This delegation simulates establishing persistence. If a hacker accidentally gets temporary access to your system, they will need to establish persistence and to get access to a more stable account.

1. In the Cloud console, on the Navigation menu (), select IAM & Admin > IAM.

2. Press the Grant Access button.

3. In the "New principals" field, enter the demo email address demouser1@gmail.com.

4. For the Role field, select BigQuery > BigQuery Admin and click Save.

5. Open the Navigation menu () and select Security > Security Command Center > Findings.

6. Change the Time Range dropdown to the Last 6 hours.

You should see three Findings, two of which are related to the access you just granted:

• Non org IAM member
• Persistence: IAM anomalous grant

7. Click on the Finding Non org IAM member and scroll down to check the "Source display name" in the description of this Finding.

8. Ensure that the display name is set to Security Health Analytics—this is the SCC service that detected a misconfiguration in your Google Cloud Project.

9. Close the window with the Finding.

10. Click on the other Finding, Persistence: IAM anomalous grant, and scroll down to check the "Source display name" in the description of this Finding.

11. Ensure that the display name is set to Event Threat Detection—this is the SCC service that detected a misconfiguration in your Google Cloud Project.

12. Scroll to the top of the window and select the Source Properties tab.

13. In this tab, expand the Properties > sensitiveRoleGrant field.

14. Here you can find the most important characteristics of this finding:

• principalEmail: who performed the suspicious action
• bindingDetails: information about the role and the member to whom this role has been granted
• members: to whom the permission has been granted

15. Close the Finding window.

16. From the Navigation menu (), select IAM & Admin > IAM.

17. Select the checkbox next to the demouser1@gmail.com principal and click the button Remove Access.

18. Click Confirm.

19. Open the Navigation menu () and select Security > Security Command Center > Findings.

Note that the "Non org IAM member" finding has disappeared from the list of findings. This is because the Security Health Analytics service has checked the updated configuration of IAM policies and deactivated this Finding.

Note: If you still see this Finding in the list, please refresh the browser tab.

The Finding "Persistence: IAM anomalous grant" has not changed its status. It was initiated by the ETD service, and cannot be deactivated automatically. You have already investigated this Finding and can be sure that the user from the gmail.com domain does not have access to your project.

Click Check my progress to verify the objective. Initiate and mitigate a threat with Event Threat Detection

Note: If you are receiving less than 20 points for this task, in the "Checkpoints" right-hand column, click the Check my progress button a couple of times.

Task 2. Configure a cloud environment to detect threats

Now that you've investigated and checked for non-compliant accounts, you need to configure Cymbal's environment to detect service account threats through logging.

Many logs in Google Cloud are enabled by default, but for detecting specific threats, you need to enable additional data access logs. In this exercise, you investigate the Service Account Self-Investigation threat.

In this scenario, a malicious actor exploits vulnerable software on a virtual machine and obtains access to the Default Service Account (which was used to create the instance). The actor wants to understand what they can do in the Google Cloud environment. To check their permissions, the actor calls the projects.getIamPolicy method. SCC should detect and report this suspicious activity recorded in the logs.

For SCC to detect this activity, you need to enable Resource Manager Admin Read logs.

1. In the Cloud console, open the Navigation menu () and select IAM & Admin > Audit Logs.

Note: You can safely ignore the message: "You don't have permission to view inherited audit logs configuration data for one or more parent resources."

2. In the list of services, find Cloud Resource Manager API and select the checkbox associated with it.

Note: If you cannot find it, scroll down to the parameter "Rows per page" and set its value to 200.

3. On the right side of the tab, find the configuration frame: Cloud Resource Manager API - Permission Types.

4. Select the Admin Read checkbox and click Save.

Now Resource Manager Data Read audit logs are collected and Event Threat Detection can analyze them.

Create a virtual machine with default service account access

For reproducing the scenario, you need to create a new virtual machine with a default Service Account and cloud-platform access scope.

1. Open the Navigation menu () and select Compute Engine > VM instances.

2. Click the Create Instance button.

3. In the Machine configuration:

   • Select region as and set zone as .

4. Click Security.

   • In the Access scopes section, select the Allow full access to all Cloud APIs value.

5. Leave all other parameters set to their default value.

6. Click Create to launch the new VM instance.

7. Once the instance is created, click on the SSH button.

8. Accept the authorization prompts when the new SSH window opens.

9. In the SSH session, enter the following command:

gcloud projects get-iam-policy $(gcloud config get project)

You should see the list of IAM permissions granted to users in the Google Cloud project.

10. Open the Navigation menu () and select Security > Security Command Center > Findings.

11. Set the value of the time range selector to Last hour.

You should see 5 Security Findings related to the instance you just created:

• Discovery: Service Account Self-Investigation
• Full API access
• Default service account used
• Compute secure boot disabled
• Public IP address

The Finding "Discovery: Service Account Self-Investigation" was initiated by Event Threat Detection (ETD), which classifies findings with the THREAT Finding Class.

Other findings have been initiated by the Security Health Analytics component, which classifies Findings by MISCONFIGURATION.

12. Click on the Finding, Discovery: service account self-investigation.

13. Select the Source Properties tab at the top of the window.

14. Now expand the field properties > serviceAccountGetsOwnIamPolicy.

15. Inspect the following values:

• principalEmail - the email address of the Service Account that is investigating its own permissions
• callerIp - IP address from which the projects.getIamPolicy method was called. In our case it should be the external IP address of the virtual machine instance-1.

16. Exit out of the Finding window.

Outside of this scenario, this Finding can inform you that your virtual machine and the default Service Account have been compromised and you need to investigate and contain this incident.

Mute the finding you've investigated

Now that you've investigated the finding, mute it.

1. Select the checkbox next to the Discovery: Service Account Self-Investigation Finding.

2. Expand the Mute options drop-down list.

3. Then select the Apply mute override option.

4. Ensure that this Finding no longer appears in the SCC interface.

Click Check my progress to verify the objective. Configure a cloud environment to detect threats

Task 3. Manage SCC findings with Event Threat Detection

When detecting some threats you may need to enable additional logs, which are not enabled by default. For detecting some findings, you also need to create additional configurations, such as DNS policies.

This allows you to detect malicious software running on compute resources and to identify well-known malicious DNS addresses.

When a DNS request is made on a virtual machine, this query is not logged by default, and in turn SCC cannot detect connections to malicious internet resources.

In the previous task, you enabled logs for the Resource Manager service using an IAM configuration. For logging all DNS queries, you need to create a DNS policy with logging enabled.

Note: You can refer to the Use logging and monitoring reference guide to learn more about logging and monitoring metrics for Cloud DNS.

1. To enable full DNS query logging, open the Navigation menu (), scroll down, click View All Products, and select Network services > Cloud DNS.

2. Click the DNS Server Policies tab and click the Create Policy button.

3. Enter dns-test-policy for the name of the DNS policy.

4. Select the On radio button for DNS logs.

5. In the "Alternate DNS servers" part, select default from the network dropdown and click OK.

6. Click the Create button.

7. Now return to the SSH session of your virtual machine and try connecting to the malicious URL by running the following command:

curl etd-malware-trigger.goog

You should receive output similar to the following.

Output:

<!DOCTYPE html> <html lang="en-us"> <meta charset="utf-8"> <title>ETD Malware Trigger</title> <p>This domain is used to trigger a malware finding in Google Event Threat Detection. For more information, please visit <a href="https://cloud.google.com/event-threat-detection">https://cloud.google.com/event-threat-detection</a>

8. Return to the Google Cloud console browser tab.

9. Open the Navigation menu () and select Security > Security Command Center > Findings.

10. You should now see a new threat appear, "Malware: Bad Domain".

Note: If you don't see the new threat, refresh your browser window.

11. Click on this Finding.

12. In the new window, click on the Source properties tab.

13. Expand the Properties field and examine the following:

• Domains: the list of domains for which the instance requested address resolution
• InstanceDetails: the ID of the instance that connected to the "malicious" domain

14. Close the Finding Window.

15. Select the checkbox associated with the Finding, Malware: Bad Domain.

16. Expand the Mute Options drop-down list.

17. Click Apply mute override. This Finding is now removed from the SCC interface.

18. From the Navigation menu (), select Compute Engine > VM instances.

19. Select the checkbox next to the virtual machine instance you created previously and click Delete.

20. Confirm the delete action and click Delete.

Click Check my progress to verify the objective.

Manage SCC findings with Event Threat Detection

Congratulations!

In this lab, you learned how to initiate and mitigate a threat with Event Threat Detection, configure a cloud environment to detect threats, and manage SCC findings with Event Threat Detection.

Next steps / Learn more

• Check out the lab titled Mitigate Threats and Vulnerabilities with Security Command Center: Challenge Lab.

Google Cloud training and certification

...helps you make the most of Google Cloud technologies. Our classes include technical skills and best practices to help you get up to speed quickly and continue your learning journey. We offer fundamental to advanced level training, with on-demand, live, and virtual options to suit your busy schedule. Certifications help you validate and prove your skill and expertise in Google Cloud technologies.

Manual Last Updated December 11, 2024

Lab Last Tested October 1, 2024

Copyright 2024 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.