Your company has deployed two on-premises firewalls. You need to configure the firewalls to send logs to Google Security Operations (SecOps) using Syslog. What should you do?
Answer(s): C
On-premises firewalls cannot send logs directly to Google SecOps. The correct approach is to deploy a third- party agent (such as Bindplane or NXLog) in your on-premises environment and configure the firewalls to forward Syslog data to that agent. The agent then reliably forwards the logs to Google SecOps for ingestion.
You are a platform engineer at an organization that is migrating from a third-party SIEM product to Google Security Operations (SecOps). You previously manually exported context data from Active Directory (AD) and imported the data into your previous SIEM as a watchlist when there were changes in AD's user/asset context data. You want to improve this process using Google SecOps. What should you do?
Answer(s): D
The best approach is to ingest AD organizational context data directly into Google SecOps as user/asset context. This ensures that AD user and asset information is automatically enriched in security events without manual exports or watchlists. It improves correlation, investigation efficiency, and automation compared to maintaining separate reference lists or data tables.
You manage a large fleet of Compute Engine instances. Security Health Analytics (SHA) has generated a CONFIDENTIAL_COMPUTING_DISABLED finding within Security Command Center (SCC). You need to quickly remediate this finding. What should you do?
When you delete the offending VM instance, the related SHA finding will be automatically marked as inactive in Security Command Center (SCC). This is the correct and efficient way to remediate the finding without manually muting or disabling detectors, ensuring the issue is resolved and tracked properly.
Your company's SOC recently responded to a ransomware incident that began with the execution of a malicious document. EDR tools contained the initial infection. However, multiple privileged service accounts continued to exhibit anomalous behavior, including credential dumping and scheduled task creation. You need to design an automated playbook in Google Security Operations (SecOps) SOAR to minimize dwell time and accelerate containment for future similar attacks. Which action should you take in your Google SecOps SOAR playbook to support containment and escalation?
Answer(s): A
To minimize dwell time and contain privileged account abuse in ransomware incidents, the SOAR playbook should revoke OAuth tokens and suspend sessions for high-privilege accounts based on entity risk. This action directly disrupts attacker persistence and lateral movement while automated escalation ensures timely response, reducing reliance on manual intervention.
Your organization uses Google Security Operations (SecOps) for security analysis and investigation. Your organization has decided that all security cases related to Data Loss Prevention (DLP) events must be categorized with a defined root cause specific to one of five DLP event types when the case is closed in Google SecOps. How should you achieve this?
The correct solution is to customize the Close Case dialog in Google SecOps to include the five defined DLP event types as selectable root cause options. This enforces consistent categorization at case closure, ensuring analysts must assign the correct DLP event type root cause before completing the workflow.
Post your Comments and Discuss Google Security-Operations-Engineer exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Security-Operations-Engineer content, but please register or login to continue.