Regulatory support in Cloud Trace
Stay organized with collections
Save and categorize content based on your preferences.
This document describes the features, configurations and APIs in Cloud Trace that align
with the controls for supported control packages. This document assumes that
you're using Assured Workloads.
Data Boundary for ITAR
Supported services
The following table lists the Cloud Trace APIs and versions that meet the requirements of Data Boundary for ITAR.
Service
Version
Status
cloudtrace.googleapis.com
v1
SUPPORTED
cloudtrace.googleapis.com
v2
SUPPORTED
cloudtrace.googleapis.com
v2beta1
SUPPORTED
Compliance supported regions
Cloud Trace is available for Data Boundary for ITAR in the following Google Cloud regions:
us-central1
us-central2
us-east1
us-east4
us-east5
us-south1
us-west1
us-west2
us-west3
us-west4
API fields for sensitive data
Resource: No resource
The following table specifies the API resources and fields that are designed to handle data that is protected under Data Boundary for ITAR.
The following table provides an illustrative list of field categories and specific fields that aren't suitable for sensitive information. To maintain compliance, avoid placing protected data in these fields. For a complete list, contact your Google Cloud representative.
Key/value pairs in protected map fields, which have well-established semantic conventions in OpenTelemetry, are not protected, and aren't suitable for sensitive information:
[[["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 2026-09-28 UTC."],[],[]]