Regulatory support in Pub/Sub
Stay organized with collections
Save and categorize content based on your preferences.
This document describes the features, configurations and APIs in Pub/Sub that align
with the controls for supported control packages. This document assumes that
you're using Assured Workloads.
Data Boundary For FedRAMP High
Supported services
The following table lists the Pub/Sub APIs and versions that meet the requirements of Data Boundary For FedRAMP High.
Service
Version
Status
pubsub.googleapis.com
v1
SUPPORTED
Compliance supported regions
Pub/Sub is available for Data Boundary For FedRAMP High 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
Management tools
The following table describes how management tools support Data Boundary For FedRAMP High with Pub/Sub.
Tool
Description
Google Cloud SDK
You must use Google Cloud SDK version 403.0.0 or later to help ensure data regionalization for FedRAMP High technical data. To verify your current Google Cloud SDK version, run gcloud --version, and then run gcloud components update to update to the latest version.
Administrator controls
By default, non-compliant APIs are disabled. However, administrators with sufficient permissions can enable a non-compliant API. When non-compliance APIs are enabled, you are notified in the Assured Workloads Monitoring page.
Affected features
The following table describes which features are affected by Data Boundary For FedRAMP High:
Feature
Description
Single Message Transforms (SMTs)
This feature is not supported for FedRAMP High compliance and should not be used. It is disabled by default under Assured Workloads folders.
Applicable settings
The following table describes the organization policy constraints and product
settings that apply to Data Boundary For FedRAMP High. By default, these are set by Assured Workloads. If you change these settings, you must first consider how that change impacts your compliance status. For instructions on configuring organization policies, see Creating and managing organization policies.
The following table lists the field categories and specific fields that aren't designed for sensitive information. To maintain compliance, avoid placing protected data in these fields.
[[["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-10-21 UTC."],[],[]]