Google Security Operations SIEM is a cloud service, built as a specialized layer on top of
core Google infrastructure, designed for enterprises to privately retain, analyze,
and search the massive amounts of security and network telemetry they generate.
Google Security Operations normalizes, indexes, correlates, and analyzes the data to
provide instant analysis and context on risky activity.
Google Security Operations lets you to examine the aggregated security information
for your enterprise going back for months or longer. Use Google Security Operations to
search across all of the domains accessed within your enterprise. You can narrow
your search to any specific asset, domain, or IP address to determine if any
compromise has taken place.
Google Security Operations platform overview
Data collection
Google Security Operations can ingest numerous security telemetry types through a variety of methods, including:
Forwarder: A lightweight software component, deployed in the customer's network, that supports syslog, packet capture,
and existing log management or security information and event management (SIEM) data repositories.
Ingestion APIs: APIs that enable logs to be sent directly to the Google Security Operations platform, eliminating the need for additional hardware or software in customer environments.
Third-party integrations: Integration with third-party cloud APIs to facilitate ingestion of logs, including sources like Office 365 and Azure AD.
Data analysis
The analytical capabilities of Google Security Operations are delivered to security professionals as a simple, browser-based
application. Many of these capabilities are also accessible programmatically through Read APIs.
Google Security Operations gives analysts a way, when they see a potential threat, to determine what it is, what it's doing,
whether it matters, and how best to respond.
Security and compliance
As a specialized, private layer built over core Google infrastructure, Google Security Operations inherits compute and storage
capabilities as well as the security design and capabilities of that infrastructure.
As part of its security design, Google SecOps stores user credentials (for example, credentials that you provide so a Google SecOps feed can ingest log data from a third-party API) in Secret Manager.
Google Security Operations features
Search
Raw Log Scan: Search your raw unparsed logs.
Regular Expressions: Search your raw unparsed logs using regular expressions.
Investigative views
Asset view: Investigate assets within your enterprise and whether or not they have interacted with suspicious domains.
IP Address view: Investigate specific IP addresses within your enterprise and what impact they have on your assets.
Hash view: Search for and investigate files based on their hash value.
Domain view: Investigate specific domains within your enterprise and what impact they have on your assets.
User view: Investigate users within your enterprise who may have been impacted by security events.
Procedural filtering: Fine tune information about an asset, including by event type, log source, network connection status, and Top Level Domain (TLD).
Curated information
Asset insight blocks: Highlights the domains and alerts that you might want to investigate further.
Prevalence graph: Shows the number of domains an asset has connected to over a specified time period.
### Detection Engine
You can use the Google Security Operations Detection Engine to automate the process of searching across
your data for security issues. You can specify rules to search all of your incoming data and
notify you when potential and known threats appear in your enterprise.
VirusTotal
You can launch VirusTotal from Google Security Operations to further investigate an asset, domain, or IP address by clicking VT Context.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eGoogle Security Operations SIEM is a cloud-based service designed for enterprises to retain, analyze, and search extensive security and network telemetry data.\u003c/p\u003e\n"],["\u003cp\u003eThis platform aggregates and analyzes security data, allowing users to investigate security information over extended periods and across various domains, assets, and IP addresses.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Security Operations supports data collection through forwarders, ingestion APIs, and third-party integrations like Office 365 and Azure AD, enabling seamless ingestion of security logs.\u003c/p\u003e\n"],["\u003cp\u003eThe platform offers a variety of investigative views, such as Enterprise Insights, Asset, IP Address, Hash, Domain, and User views, to facilitate in-depth security analysis.\u003c/p\u003e\n"],["\u003cp\u003eThe Detection Engine automates the search for security threats within your data, and VirusTotal can be launched from the platform for further asset, domain, or IP address investigation.\u003c/p\u003e\n"]]],[],null,["# Google Security Operations SIEM overview\n========================================\n\nSupported in: \n[SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n\nGoogle Security Operations SIEM is a cloud service, built as a specialized layer on top of\ncore Google infrastructure, designed for enterprises to privately retain, analyze,\nand search the massive amounts of security and network telemetry they generate.\nGoogle Security Operations normalizes, indexes, correlates, and analyzes the data to\nprovide instant analysis and context on risky activity.\n\nGoogle Security Operations lets you to examine the aggregated security information\nfor your enterprise going back for months or longer. Use Google Security Operations to\nsearch across all of the domains accessed within your enterprise. You can narrow\nyour search to any specific asset, domain, or IP address to determine if any\ncompromise has taken place.\n\n**Google Security Operations platform overview**\n\nData collection\n---------------\n\nGoogle Security Operations can ingest numerous security telemetry types through a variety of methods, including:\n\n- Forwarder: A lightweight software component, deployed in the customer's network, that supports syslog, packet capture,\n and existing log management or security information and event management (SIEM) data repositories.\n\n- Ingestion APIs: APIs that enable logs to be sent directly to the Google Security Operations platform, eliminating the need for additional hardware or software in customer environments.\n\n- Third-party integrations: Integration with third-party cloud APIs to facilitate ingestion of logs, including sources like Office 365 and Azure AD.\n\nData analysis\n-------------\n\nThe analytical capabilities of Google Security Operations are delivered to security professionals as a simple, browser-based\napplication. Many of these capabilities are also accessible programmatically through Read APIs.\nGoogle Security Operations gives analysts a way, when they see a potential threat, to determine what it is, what it's doing,\nwhether it matters, and how best to respond.\n\nSecurity and compliance\n-----------------------\n\nAs a specialized, private layer built over core Google infrastructure, Google Security Operations inherits compute and storage\ncapabilities as well as the security design and capabilities of that infrastructure.\n\nAs part of its security design, Google SecOps stores user credentials (for example, credentials that you provide so a Google SecOps feed can ingest log data from a third-party API) in [Secret Manager](/secret-manager).\n| **Note:** Both Google SecOps and Google employees with permissions to Google SecOps can access user credentials.\n\nGoogle Security Operations features\n-----------------------------------\n\n### Search\n\n- Raw Log Scan: Search your raw unparsed logs.\n- Regular Expressions: Search your raw unparsed logs using regular expressions.\n\n### Investigative views\n\n- Asset view: Investigate assets within your enterprise and whether or not they have interacted with suspicious domains.\n- IP Address view: Investigate specific IP addresses within your enterprise and what impact they have on your assets.\n- Hash view: Search for and investigate files based on their hash value.\n- Domain view: Investigate specific domains within your enterprise and what impact they have on your assets.\n- User view: Investigate users within your enterprise who may have been impacted by security events.\n- Procedural filtering: Fine tune information about an asset, including by event type, log source, network connection status, and Top Level Domain (TLD).\n\n### Curated information\n\n- Asset insight blocks: Highlights the domains and alerts that you might want to investigate further.\n- Prevalence graph: Shows the number of domains an asset has connected to over a specified time period. ### Detection Engine You can use the Google Security Operations Detection Engine to automate the process of searching across your data for security issues. You can specify rules to search all of your incoming data and notify you when potential and known threats appear in your enterprise.\n\n### VirusTotal\n\nYou can launch VirusTotal from Google Security Operations to further investigate an asset, domain, or IP address by clicking [VT Context](/chronicle/docs/investigation/view-virustotal-information).\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]
