GC
Vendor EntityUnverified Profile

Google Cloud

Visit Vendor Website

Google Cloud offers a portfolio covering collecting and analyzing security-relevant events, providing external threat context for analysis and decisions, investigating and managing cybersecurity incidents and assessing cloud exposure or protecting running workloads. The entries in this catalog include Google Security Operations, Google Threat Intelligence, Mandiant Incident Response and Security Command Center. Google Security Operations focuses on cloud security analytics and threat investigation. Google Threat Intelligence focuses on threat intelligence and adversary research. Mandiant Incident Response focuses on incident investigation and recovery support. When reviewing Google Cloud, compare the named products individually: a platform family, a specific module and a managed service can have different scopes and purchasing requirements. Selection should account for log onboarding, detection content, query workflows and integration with response tools. Portfolio detail - Google Security Operations: the catalog lists Google security analytics workflow, Threat hunting, Response automation. - Google Threat Intelligence: the catalog lists Mandiant intelligence context, VirusTotal analysis context, Threat intelligence collection. - Mandiant Incident Response: the catalog lists Incident investigation, Containment planning, Digital evidence analysis. - Security Command Center: the catalog lists Cloud entitlement analysis, Runtime threat detection, Cloud compliance checks. For procurement, map each required capability to a named offering and confirm the edition, dependencies and delivery responsibility with the vendor. Product-level entries below provide the operational context and evaluation questions for that comparison.

Documented Software Products (3)

Software Product

Google Security Operations

Google Security Operations from Google Cloud focuses on cloud security analytics and threat investigation. It is security operations platform used for analyzing collected security telemetry and supporting investigation workflows. Capabilities - Google security analytics workflow: Brings supported security telemetry into Google's security operations analysis environment. - Threat hunting: Lets analysts investigate hypotheses across the security data available in the platform. - Response automation: Connects detection and investigation with the automated actions documented for the offering. Use and operational context Google Security Operations is relevant to security operations teams using Google's analytics environment when the requirement centers on analyzing collected security telemetry and supporting investigation workflows. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review log onboarding, detection content, query workflows and integration with response tools. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Google Security Operations focuses on analyzing collected security telemetry and supporting investigation workflows. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.

Pricing: Pricing not publicly documented
Software Product

Google Threat Intelligence

Google Threat Intelligence from Google Cloud focuses on threat intelligence and adversary research. It is threat intelligence technology or service used for providing external threat context for analysis and decisions. Capabilities - Mandiant intelligence context: Includes the Mandiant threat intelligence context described in Google's combined intelligence offering. - VirusTotal analysis context: Adds the documented VirusTotal-related analysis context to the intelligence workflow. - Threat intelligence collection: Brings threat information into a workflow that supports analysis and security decisions. - Threat indicator enrichment: Adds context to indicators so teams can assess their relevance to an investigation. - Threat intelligence integrations: Connects intelligence with the supported analysis tools or security workflows. - Intelligence prioritization: Helps teams focus attention on the threat information most relevant to their requirements. Use and operational context Google Threat Intelligence is relevant to analysts investigating adversaries, indicators or emerging exposures when the requirement centers on providing external threat context for analysis and decisions. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review source relevance, freshness, integration methods and how intelligence changes a specific investigation or protection decision. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Google Threat Intelligence focuses on providing external threat context for analysis and decisions. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.

Pricing: Pricing not publicly documented
Software Product

Security Command Center

Security Command Center from Google Cloud focuses on cloud asset risk assessment and posture management. It is cloud security technology used for assessing cloud exposure or protecting running workloads. Capabilities - Cloud entitlement analysis: Examines cloud permissions to identify overly broad or risky access. - Runtime threat detection: Uses activity from running workloads to identify or respond to active threats. - Cloud compliance checks: Compares observed cloud settings with the control checks supported by the product. Use and operational context Security Command Center is relevant to cloud and security teams working across accounts and workloads when the requirement centers on assessing cloud exposure or protecting running workloads. Scope the evaluation around the functions listed above and the assets or workflows that need coverage. A useful trial should use representative business conditions so the team can assess the quality of the results and the effort needed to act on them. Deployment and evaluation Before adoption, review cloud permissions required for onboarding, the assets assessed, runtime coverage and how findings reach remediation owners. Assign an owner for administration, document required permissions and identify how the product or service will fit the existing operating process. Buyer questions - What is the main purpose? Security Command Center focuses on assessing cloud exposure or protecting running workloads. - What should a proof of concept establish? Test the listed capabilities against representative assets and workflows, record useful results and unresolved gaps, and confirm who handles follow-up work. - What should be confirmed before purchase? Ask the vendor which edition or service scope includes the required features, which dependencies must be configured and what licensing or contract terms apply. Pricing has not been verified for this catalog.

Pricing: Pricing not publicly documented