
# Incident & investigation management on Google Cloud

Compare documented Incident & investigation management deployments on Google Cloud, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/gcp/incident-investigation-management/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: Google Cloud project
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects (checked 2026-11-20).
- Network: VPC network
- Identity and access: IAM policies and service accounts
- Installation guidance: Terraform, optionally using Infrastructure Manager for resource provisioning; deploy the application separately.
- Guidance source: https://docs.cloud.google.com/infrastructure-manager/docs/overview
- Guidance reviewed: 2026-11-10


### Private offers

Cloud Marketplace vendors can negotiate a private offer for a specified Cloud Billing account. Check duration, renewal terms and commitment treatment in the actual agreement.
Source: https://docs.cloud.google.com/marketplace/docs/offers/discover-private-offers (reviewed 2026-11-14).

### Private connectivity

Private Service Connect connects VPC consumers to supported managed or producer services. Confirm the actual product endpoint and network/DNS architecture.
Source: https://docs.cloud.google.com/vpc/docs/private-service-connect (reviewed 2026-11-14).

### External workload access

Workload Identity Federation can grant external workloads scoped Google Cloud access without long-lived service-account keys. Validate the trust configuration and exact roles.
Source: https://docs.cloud.google.com/iam/docs/workload-identity-federation (reviewed 2026-11-14).

### Regulated environments

Assured Workloads applies control packages for residency and access boundaries. Confirm supported services, regions and the product deployment; it is not automatic product certification.
Source: https://docs.cloud.google.com/assured-workloads/docs/overview (reviewed 2026-11-14).

The listings below have evidence for Google Cloud. Read each cloud evidence note for the applicable package, edition and support qualifications.

3 listings.


## Darktrace Forensic Acquisition and Investigation

Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.

- Listing: https://launchinyourcloud.com/directory/cado-response/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.
- Licensing model: commercial-only
- Installation: CloudFormation; Terraform
- Architecture: Provider-specific CloudFormation or Terraform application stacks and evidence storage.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.

Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation.

Provider-specific CloudFormation or Terraform application stacks and evidence storage. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Commercial customer-deployed cloud-forensics acquisition and investigation platform, formerly Cado Response.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy (checked 2026-11-19). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy (checked 2026-11-19). 


### Cloud deployment evidence

- AWS CloudFormation (aws): https://docs.cadosecurity.com/cado/deploy/aws/cloudformation
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- Azure Deploy (azure): https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- GCP Deploy (gcp): https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy
  Provider-specific CloudFormation or Terraform application stacks and evidence storage. Collection roles, evidence sources, application hosting and licence activation are separate permissions and data-flow concerns. The named-cloud guides install the actual platform, rather than just an acquisition agent.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.


### Sources

- AWS CloudFormation: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation

- Azure Deploy: https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy

- GCP Deploy: https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy

- Licensing Docs: https://docs.cadosecurity.com/cado/deploy/licenses

- Product Page: https://www.darktrace.com/forensic-acquisition-investigation

- Darktrace News: https://www.darktrace.com/news/darktrace-unveils-automated-forensics-capabilities-in-its-activeai-security-platform

### Licensing sources

- https://docs.cadosecurity.com/cado/deploy/licenses

- https://www.darktrace.com/forensic-acquisition-investigation

### Infrastructure sources

- https://docs.cadosecurity.com/cado/deploy/aws/cloudformation

- https://docs.cadosecurity.com/cado/deploy/azure/azure-deploy

- https://docs.cadosecurity.com/cado/deploy/gcp/gcp-deploy


### Buyer diligence


Research coverage: 4/12 fields (33%); 4 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The customer-deployed guide documents an Okta SAML integration, explicitly marked beta, with application callback/audience and email/group mapping. It excludes SaaS deployments and points those to a different identity guide. Validate the selected release, beta suitability, IdP and administrator-group handling. Scope: Darktrace customer-deployed Forensic Acquisition and Investigation; documented beta Okta SAML path. Source: https://docs.cadosecurity.com/cado/manage/users-authentication/sso/okta_saml (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The vendor supplies CloudFormation templates for public/private, existing-VPC and GovCloud deployment, with IAM/network parameters and sales/trial delivery access. Obtain the entitled template and licence, review permissions/TLS/storage, and choose the appropriate account/region topology. Scope: Vendor Cado/Darktrace customer-deployed AWS CloudFormation delivery. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (reviewed 2026-11-21). Deployment artifact: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation. Artifact reference: Current vendor CloudFormation guide reviewed on this date.

- Minimum footprint / sizing: Documented. The CloudFormation guide recommends m5.4xlarge as the enterprise minimum for the main EC2 server. Acquisition/processing workers, evidence volumes, network transfer and standby/recovery resources are additional. This is a vendor main-server recommendation, not a whole-system cost or HA workload guarantee. Scope: Customer-deployed Darktrace/Cado main-server recommendation; worker and evidence capacity separate. Source: https://docs.cadosecurity.com/cado/deploy/aws/cloudformation (reviewed 2026-11-21).

- License pricing: Documented. Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. Scope: Darktrace Forensic Acquisition and Investigation; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://docs.cadosecurity.com/cado/deploy/licenses (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## SAP S/4HANA EHS — Customer-Operated

Customer-operated SAP S/4HANA environmental compliance and safety incident-management capabilities.

- Listing: https://launchinyourcloud.com/directory/sap-s4hana-ehs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial SAP S/4HANA on-premise licensing; verify EHS component entitlements
- Licensing model: commercial-only
- Installation: Install the licensed SAP S/4HANA on-premise edition and configure the selected EHS components using SAP implementation guides
- Architecture: SAP S/4HANA application stack with SAP HANA database and EHS Fiori applications
- Operations: Customer manages the application and database infrastructure, installation, upgrades, access, backups and EHS configuration; agree implementation and support arrangements.
- Product website: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The on-premise edition is explicitly customer-installed and customer-operated. This entry covers its EHS components, not SAP-managed Cloud Private Edition or Public Edition. Check the selected release, component entitlements and implementation scope. Environmental reporting still requires configured requirements and reliable source data.

The listed on-premise edition uses SAP commercial software licensing. The official deployment comparison describes its perpetual-license model; the customer agreement defines the exact component rights.

Customer-operated SAP application and HANA database services run on provisioned infrastructure. This is the on-premise edition, separate from SAP-managed cloud services.


### Category fit

- energy-environmental-compliance: Environmental requirements, emissions calculations, compliance scenarios, deviations and reports for environmental authorities.

- incident-investigation-management: Safety incident and near-miss capture, investigations, root-cause classifications and follow-up actions. This is industrial EHS scope, rather than a general legal investigation platform.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (checked 2026-11-12). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana (checked 2026-11-12). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp (checked 2026-11-12). 


### Cloud deployment evidence

- Customer-provided SAP S/4HANA deployment on AWS (aws): https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html
  AWS Launch Wizard provisions customer resources and can install customer-provided SAP S/4HANA software. Evidence covers the underlying S/4HANA platform; confirm EHS licensing, supported sizing, database and SAP release before deployment.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA infrastructure deployment on Azure (azure): https://learn.microsoft.com/en-us/azure/sap/center-sap-solutions/deploy-s4hana
  Microsoft documents S/4HANA infrastructure in a customer Azure subscription. Evidence covers the platform hosting option; confirm EHS modules, SAP licensing, supported operating systems and software installation separately.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- SAP S/4HANA reference architecture on Google Cloud (gcp): https://docs.cloud.google.com/sap/docs/architectures/sap-s4hana-on-gcp
  Google documents S/4HANA on SAP-certified Compute Engine infrastructure. This is platform hosting evidence; EHS functionality, licenses and supported SAP configurations still require confirmation.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- Customer-operated on-premise installation and operations: https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest

- Environment Management scope: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/1b3596cc5dd5428d887966a4193ddc29/6d08555321d77d77e10000000a441470.html

- Current incident-investigation configuration: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/f5d3e1005efd4e86acf9a65abf428082/96e81bbdc3c54a70b3b374b182bb87c0.html?locale=en-US&version=2025.000

- Commercial model and deployment responsibilities: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Licensing sources

- https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5

### Infrastructure sources

- https://help.sap.com/docs/r/product/SAP_S4HANA_ON-PREMISE/latest


### Buyer diligence


Research coverage: 4/12 fields (33%); 2 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. The reviewed EHS and deployment material does not establish the selected application UI, release and complete identity configuration. SAP platform authentication options require the actual Fiori/ABAP/GUI entry points and compatible identity components; do not infer a ready EHS federation setup from a generic SAP capability. Scope: Customer-operated S/4HANA EHS identity deployment remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. AWS Launch Wizard can provision SAP landscapes and install customer-provided supported S/4HANA software, including separate multi-instance/HA patterns. Supply licensed installation media and validate supported releases. This is underlying S/4HANA platform automation; EHS activation, business configuration and data migration remain separate. Scope: Provider-documented S/4HANA deployment supporting the EHS parent platform; not a packaged EHS solution. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21). Deployment artifact: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html. Artifact reference: Current AWS Launch Wizard supported SAP deployment guide.

- Minimum footprint / sizing: Sources checked — unresolved. Launch Wizard selects resources from supplied SAP requirements; it does not establish an EHS-specific capacity baseline. Obtain certified S/4HANA/HANA sizing for application/database memory, batch/analytics, data volume and HA rather than interpreting supported maximum memory as a minimum. Scope: S/4HANA EHS workload sizing remains unconfirmed. Source: https://docs.aws.amazon.com/launchwizard/latest/userguide/launch-wizard-sap.html (reviewed 2026-11-21).

- License pricing: Documented. SAP distinguishes customer-managed S/4HANA on-premise perpetual licensing from subscription-based Private Edition with SAP technical managed services. Do not substitute a cloud subscription for the customer-operated scope; EHS module rights and implementation pricing require the actual agreement. Scope: S/4HANA on-premise deployment model; not a module-specific EHS quote. Source: https://learning.sap.com/courses/exploring-sap-cloud-erp/describing-the-technical-layers-and-deployment-variants-of-sap-s-4hana_b81ddd87-646f-4c28-89e0-e29815cb59d5 (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Timesketch

Open-source collaborative forensic timeline analysis application.

- Listing: https://launchinyourcloud.com/directory/timesketch/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: gcp, azure
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
- Licensing model: open-source
- Installation: Helm / Kubernetes operator; Kubernetes manifests; VM image
- Architecture: Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack.
- Operations: Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
- Product website: https://github.com/google/timesketch
- Source review: 2026-11-19; cloud review: 2026-11-19; licensing review: 2026-11-19; infrastructure review: 2026-11-19

### Scope and qualifications

Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.

Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.


### Category fit

- incident-investigation-management: Open-source collaborative forensic timeline analysis application.

### Deployment boundaries


- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://google.github.io/osdfir-infrastructure/docs/getting-started.html (checked 2026-11-19). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://secureanycloud.com/stacks/timesketch/ (checked 2026-11-19). 


### Cloud deployment evidence

- OSDFIR Getting Started (gcp): https://google.github.io/osdfir-infrastructure/docs/getting-started.html
  Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
  Source type: vendor-documentation; reviewed: 2026-11-19; vendor support: not-assessed.

- SecureAnyCloud Azure (azure): https://secureanycloud.com/stacks/timesketch/
  Google's OSDFIR Helm application on GKE or SecureAnyCloud's separately packaged Azure VM stack. Azure packaging is supplied by SecureAnyCloud, not Google. The upstream release and image stack versions are separate. Timeline analysis complements acquisition and incident-intake tools; it does not replace every investigation or case-management function.
  Source type: third-party-package; reviewed: 2026-11-19; vendor support: not-assessed.


### Community and maintenance

The reviewed upstream contributor history includes berggren, kiddinn, jaegeral, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Reviewed 2026-11-19.

- Community, governance or adoption evidence: https://github.com/google/timesketch/graphs/contributors

- Upstream project: https://github.com/google/timesketch

### Sources

- OSDFIR Getting Started: https://google.github.io/osdfir-infrastructure/docs/getting-started.html

- SecureAnyCloud Azure: https://secureanycloud.com/stacks/timesketch/

- OSDFIR Timesketch: https://google.github.io/osdfir-infrastructure/charts/timesketch/

- Apache-2.0: https://github.com/google/timesketch/blob/master/LICENSE

- Releases: https://github.com/google/timesketch/releases

### Licensing sources

- https://github.com/google/timesketch/blob/master/LICENSE

### Infrastructure sources

- https://google.github.io/osdfir-infrastructure/docs/getting-started.html

- https://secureanycloud.com/stacks/timesketch/


### Buyer diligence


Research coverage: 5/12 fields (42%); 5 documented, 0 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. The versioned configuration supports trusted web-server REMOTE_USER SSO and separately Google OIDC/Cloud IAP options, with actual token/authentication implementation. Configure the selected mode, trusted proxy boundary, identity claims and group policy; these mechanisms are not interchangeable and must not trust spoofed headers. Scope: Timesketch 20261014 configured user SSO/OIDC/IAP paths. Source: https://github.com/google/timesketch/blob/20261014/data/timesketch.conf (reviewed 2026-11-21). Supporting source: Google token validation — https://github.com/google/timesketch/blob/20261014/timesketch/lib/google_auth.py. Supporting source: Application authentication views — https://github.com/google/timesketch/blob/20261014/timesketch/views/auth.py.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Google maintains OSDFIR Helm charts with Timesketch values and production installation guidance. Select compatible chart/application/OpenSearch versions, expose ingress deliberately and configure secrets, persistent storage and backups. Local Minikube instructions and default port-forward access are not production deployment. Scope: Maintainer Timesketch Kubernetes/Helm deployment; chart and application versions separate. Source: https://google.github.io/osdfir-infrastructure/charts/timesketch/ (reviewed 2026-11-21). Deployment artifact: https://google.github.io/osdfir-infrastructure/charts/timesketch/. Artifact reference: Current OSDFIR Timesketch chart guide reviewed on this date.

- Minimum footprint / sizing: Documented. The upstream scaling guide gives at least 8 GB RAM for its described Ubuntu environment and stresses fast local storage and OpenSearch sizing/shard limits. This is an entry baseline, not capacity for arbitrary timelines/events or an HA cluster; separately size indexes, imports, workers, replicas and backups. Scope: Timesketch published entry baseline and search-scaling guidance. Source: https://timesketch.org/guides/admin/scaling-and-limits/ (reviewed 2026-11-21).

- License pricing: Documented. Apache License 2.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms. Scope: Timesketch; software terms only, excluding cloud charges, labour and separately licensed services. Source: https://github.com/google/timesketch/blob/master/LICENSE (reviewed 2026-11-19).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. Reviewed upstream 20261014 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence. Scope: Timesketch upstream application; verify compatibility with the selected package. Source: https://github.com/google/timesketch/releases/tag/20261014 (reviewed 2026-11-19).






