Assured Workloads frameworks
This page provides reference content for the built-in frameworks that are included in Assured Workloads and Audit Manager.
Australia Data Boundary
Supported cloud provider: Google Cloud
Australia Data Boundary sets data location controls to support Australia-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Australia Data Boundary and Support
Supported cloud provider: Google Cloud
Australia Data Boundary and Support sets data location controls to support Australia-only regions. Support access and technical support are set to personnel who are located in five specific countries (United States, Canada, Australia, New Zealand, and United Kingdom).
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Brazil Data Boundary
Supported cloud provider: Google Cloud
Brazil Data Boundary sets data location controls to support Brazil-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Data Boundary for Canada Controlled Goods
Supported cloud provider: Google Cloud
Data Boundary for Canada Controlled Goods sets data location controls to support Canada-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure NetApp Volumes to Support Data Boundaries
- Create CMEK Project and Key Ring
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Compute Instance Data Access APIs
- Disable Creation of Global Load Balancers
- Disable Creation of Global Self-managed SSL Certificates
- Disable GKE Diagnostic Administrative Access
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Enable Access Transparency
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enforce allowed CMEK crypto key projects
- Enforce FIPS-Compliant Machine Types
- Enforce In-Transit Regions for Pub/Sub Messages
- Require CMEK Protection
- Restrict Access to VM Core Memory
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Canada Data Boundary
Supported cloud provider: Google Cloud
Canada Data Boundary sets data location controls to support Canada-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Canada Data Boundary and Support
Supported cloud provider: Google Cloud
Canada Data Boundary and Support sets data location controls to support Canada-only regions. Support access controls for first-level and second-level support are set to personnel who are legally eligible to work in Canada and physically located within the country of Canada.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Data Boundary for Canada Protected B
Supported cloud provider: Google Cloud
Data Boundary for Canada Protected B sets data location controls to support Canada-only regions. Support access controls are set to Canadian support personnel who have completed Reliability Status screenings.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Chile Data Boundary
Supported cloud provider: Google Cloud
Chile Data Boundary sets data location controls to support Chile-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
CJIS
Supported cloud provider: Google Cloud
Data Boundary for Criminal Justice Information Systems (CJIS) sets data location controls to support US-only regions. Support access controls are set to support personnel who have completed CJIS background checks and are located in the US. This means that Assured Workloads support cases are restricted to CJIS-adjudicated support staff located in the US. Escorted session controls are also used to supervise and monitor support actions by non-adjudicated staff.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Create CMEK Project and Key Ring
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Compute Instance Data Access APIs
- Disable Enhanced Text Search for Firestore
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Identity
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Enforce allowed CMEK crypto key projects
- Require CMEK Protection
- Restrict Resource Locations
- Restrict Service Usage
- Restrict the BigQuery Data Transfer Service API
- Restrict TLS Versions
- Specify Cloud KMS Key Protection Levels
NATO Public Cloud Directive
Supported cloud provider: Google Cloud
This framework is designed to align with the security measures required for the implementation and management of cloud infrastructure to protect NATO UNCLASSIFIED (NU) and NATO RESTRICTED (NR) information in the public cloud, in accordance with the “NATO Technical and Implementation Directive for the Protection of NATO Information within Public Cloud-Based Communication and Information Systems” (AC/322-D(2021)0032-REV1).
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- Allow Only IL5 Compliant APIs for Gemini Enterprise Agent Platform
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Create CMEK Project and Key Ring
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Compute Instance Data Access APIs
- Disable Creation of Global Load Balancers
- Disable diagnostic and administrative access pathways in Cloud SQL
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Service Account Key Creation
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Compliance Settings for Cloud Identity
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Regulatory Settings for Cloud DNS
- Enforce allowed CMEK crypto key projects
- Prevent Automatic Creation of Default Network
- Prevent Automatic Granting of Editor Role to Default Service Accounts
- Require CMEK Protection
- Restrict Cloud SQL Resource Creation
- Restrict Public Access to Data Stored in Buckets
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
- Set Zonal DNS as Default for Compute Engine
- Specify Cloud KMS Key Protection Levels
DBG CSA CCM
Supported cloud provider: Google Cloud
DBG CSA CCM
This framework includes the cloud control groups and cloud controls in the following sections.
csa-ccm-bcr-08-3
The BCR-08.3 monitors configuration of standard Backup agents for three GCP services running in the current project:
- Backup Agent for GKE is enabled for all GKE clusters;
- Backup configuration is enabled for Cloud SQL instances;
- Continuous backup is enabled for AlloyDB instances;
The controls is violated if any of the required Backup configurations is not enabled.
csa-ccm-bcr-11-2
The BCR-11.2 monitors effective value of the Organization Policy gcp.resourceLocations.
The control is violated if the Organization Policy is not set or is not restricting location of new resources to the regions:
- europe-west3 (Frankfurt)
- europe-west6 (Milan)
- europe-west8 (Zurich)
csa-ccm-bcr-11-4
The BCR-11.4 monitors geographical location of Google Cloud resources, supporting regionalization.
Complaint Google Cloud resources should be launched in any of these regions:
- europe-west3 (Frankfurt)
- europe-west6 (Milan)
- europe-west8 (Zurich)
The control is violated if any other location is used. This includes EU multi-region.
- GCP Foundation Landing Zone Constraints Regions To Europe
- GCP Foundation Resources Not Running Outside Europe
csa-ccm-ccc-05-1
Check shared responsibility documentation in change procedures
csa-ccm-ccc-06
CCC-06 monitors that every Google Cloud project enables only those GCP services that have been tested and approved for usage.
csa-ccm-cek-02-5
Newly created data storage services must use CMEK, located in a specific dedicated project. This project ID must be enforced with Organization Policy constraints/gcp.restrictCmekCryptoKeyProjects
csa-ccm-cek-04-3
All keys, used for encrypting data in storage, should be generated in on-premise HSM device and then imported to GCP CMEK. All keys are stored in the cloud-based HSM system
csa-ccm-cek-08-3
All Storage Service used in GCP should use Customer Managed Encryption Key for encrypting data-at-rest.
csa-ccm-dsp-04
DSP-04.1 monitors that all resources, supporting labels, have a label attached.
csa-ccm-dsp-16
DSP-16.3 monitors configuration of GCS buckets. Every GCS bucket needs to have the Soft Delete feature enabled or both features: Object Versioning and Object Retention enabled simultaneously.
csa-ccm-ivs-05-1
IVS-05.1 monitors that every GCP project has the attached Resource Manager Tag that define the environment.
csa-ccm-ivs-09-1
Firewall rules are not using tags and do not enable access to any services from the public Internet
csa-ccm-log-04-1
Restrict audit logs access to authorized personnel and maintain records that provide unique access accountability.
csa-ccm-log-06
Use a reliable time source across all relevant information processing systems.
DORA
Supported cloud provider: Google Cloud
Digital Operational Resilience Act
This framework includes the cloud control groups and cloud controls in the following sections.
dora-article-07
Financial entities must maintain updated ICT systems, protocols and tools that are appropriate for use, reliable, and resilient.
- Block Generic Access to Cassandra Ports
- Block Generic Access to CiscoSecure/WebSM Ports
- Block Generic Access to Directory Service Ports
- Block Generic Access to DNS Ports from All IP Addresses
- Block Generic Access to Elasticsearch Ports from All IP Addresses
- Block Generic Access to FTP Ports
- Block Generic Access to HTTP Ports
- Block Generic Access to LDAP Ports
- Block Generic Access to Memcached Ports
- Block Generic Access to MongoDB Ports
- Block Generic Access to MySQL Ports
- Block Generic Access to NetBIOS Ports from All IP Addresses
- Block Generic Access to Oracle Database Ports
- Block Generic Access to POP3 Server Ports
- Block Generic Access to PostgreSQL Server Ports from All IP Addresses
- Block Generic Access to Redis Server Ports from All IP Addresses
- Block Generic Access to SMTP Server Ports
- Block Generic Access to Telnet Servers
- Block Overly Permissive Firewall Rules
- Block Serial Ports for Compute Engine Instances
- Configure the Allowed Ingress Settings for Cloud Run Organization Policy Constraint
- Configure the Allowed VPC Egress Settings for Cloud Run Organization Policy Constraint
- Configure the Disable VPC External IPv6 Usage Organization Policy
- Define Rotation Period for Cloud KMS Keys
- Enable CMEK for AlloyDB Clusters
- Enable CMEK for BigQuery Datasets
- Enable CMEK for BigQuery Tables
- Enable CMEK for Cloud SQL Databases
- Enable CMEK for Cloud Storage Buckets
- Enable CMEK on GKE Node Pool Boot Disks
- Enable Control Plane Authorized Networks on GKE Clusters
- Enable DNSSEC for Cloud DNS
- Enable Encryption on GKE Clusters
- Enable IP Alias Range for GKE Clusters
- Enable Network Policy on GKE Clusters
- Enable Private Clusters for GKE
- Enable Private Google Access for VPC Subnets
- Enable Private Google Access on an instance
- Enable Shielded GKE Nodes on a Cluster
- Enable SSL Encryption On AlloyDB Instances
- Enable the Restrict Authorized Networks on Cloud SQL Instances Organization Policy Constraint
- Encrypt Pub/Sub topic with CMEK
- Enforce SSL for all Incoming Database Connections
- Limit KMS Crypto Keys Users to Three
- Require Container-Optimized OS for a GKE Cluster
- Restrict Public Access to BigQuery Datasets
- Restrict User Managed Service Account Keys
- Use Custom VPC Networks
dora-article-09
Financial entities must implement security tools that continually monitor and control ICT systems and ensure, but not limited to, privacy, availability, integrity and confidentiality.
- Assess Actions that Don't Require Identification or Authentication
- Authorize and Monitor Privileged Remote Access
- Authorize Wireless Access to Production Systems
- Automate Account Management System
- Automate Near Real-time Event Analysis
- Avoid RSASHA1 for DNSSEC Signing
- Block Administrator Roles from Service Accounts
- Block Automatic IAM Grants to Default Service Accounts
- Block External IP Address Access on Compute Engine VM Instances
- Block Generic Access to Cassandra Ports
- Block Generic Access to CiscoSecure/WebSM Ports
- Block Generic Access to Directory Service Ports
- Block Generic Access to DNS Ports from All IP Addresses
- Block Generic Access to Elasticsearch Ports from All IP Addresses
- Block Generic Access to FTP Ports
- Block Generic Access to HTTP Ports
- Block Generic Access to LDAP Ports
- Block Generic Access to Memcached Ports
- Block Generic Access to MongoDB Ports
- Block Generic Access to MySQL Ports
- Block Generic Access to NetBIOS Ports from All IP Addresses
- Block Generic Access to Oracle Database Ports
- Block Generic Access to POP3 Server Ports
- Block Generic Access to PostgreSQL Server Ports from All IP Addresses
- Block Generic Access to RDP Ports
- Block Generic Access to Redis Server Ports from All IP Addresses
- Block Generic Access to SMTP Server Ports
- Block Generic Access to SSH Ports
- Block Generic Access to Telnet Servers
- Block Legacy Authorization on GKE Clusters
- Block Overly Permissive Firewall Rules
- Block Project-Wide SSH Keys on Compute Engine Instances
- Block Public IP Addresses for AlloyDB Cluster Instances
- Block Public IP Addresses for Cloud SQL Instances
- Block Serial Ports for Compute Engine Instances
- Block Service Account Key Creation
- Block Service Account Key Uploads
- Configure a Wireless Intrusion Detection Mechanism
- Configure Access Controls for the Network Boundary
- Configure Log Metrics and Alerts for Cloud Storage IAM Policy Changes
- Configure Network Devices to Fail in a Secure State
- Configure Security Logging Policies for Google Cloud Services
- Configure the Allowed VPC Egress Settings for Cloud Run Organization Policy Constraint
- Configure the Disable VM Serial Port Logging to Stackdriver Organization Policy
- Configure the Disable VPC External IPv6 Usage Organization Policy
- Configure the Disable VPC Internal IPv6 Usage Organization Policy
- Configure VPC Firewall Rules, Subnets, and VPN Gateway
- Control Integrations with External Systems
- Control Remote Device Connections
- Correlate Audit Records
- Create Artifact Registry Cleanup Policies
- Create GKE Clusters with Limited Privileges
- Create Inventory of Security Data Assets
- Define a Security Policy to Mitigate for DDoS Events
- Define Allowed Services for Service Perimeter
- Define Cloud Billing Budget Threshold
- Define Cloud KMS Crypto Keys Protection Level
- Define Mobile Code Policies and Controls
- Define Rotation Period for Cloud KMS Keys
- Define Service Perimeters in VPC Service Controls
- Define Storage Class Lifestyle Action
- Define the Maximum Number of Concurrent Sessions for System Accounts in Workforce Identity Pools
- Define VPC Connector Egress For Cloud Run Functions
- Define Worker Pools for Cloud Builds
- Develop System and Communications Protection Policy and Procedures
- Disable Alpha Features on GKE Clusters
- Don't Use Legacy Networks
- Don't Use User Connections Flag for SQL Server
- Don't Use User Options Flag for SQL Server
- Employ Monthly Checks for Flaw Remediation Status
- Employ Spam Protection Mechanisms
- Enable 3625 Trace Database Flag for SQL Server
- Enable Artifact Analysis Vulnerability Scanning
- Enable Audit Logs Bucket Enumeration
- Enable Audit Logs for All Services
- Enable Auto Upgrade on GKE Clusters
- Enable Cloud Asset Inventory Service
- Enable Cloud DNS Logs Monitoring
- Enable Cloud Logging on GKE Clusters
- Enable Cloud Monitoring on GKE Clusters
- Enable CMEK for AlloyDB Clusters
- Enable CMEK for BigQuery Datasets
- Enable CMEK for BigQuery Tables
- Enable CMEK for Cloud SQL Databases
- Enable CMEK for Cloud Storage Buckets
- Enable CMEK on Compute Engine Persistent Disks
- Enable CMEK on GKE Node Pool Boot Disks
- Enable Confidential Computing for Compute Engine Instances
- Enable Control Plane Authorized Networks on GKE Clusters
- Enable Data Write Audit Logs for Organization Policy
- Enable DNSSEC for Cloud DNS
- Enable Encryption for Mobile Devices
- Enable Encryption on GKE Clusters
- Enable Integrity Monitoring on GKE Clusters
- Enable Intranode Visibility for GKE Clusters
- Enable IP Alias Range for GKE Clusters
- Enable Log Checkpoints Flag for PostgreSQL
- Enable Log Connections Flag for PostgreSQL
- Enable Log Disconnections Flag for PostgreSQL
- Enable Log Duration Flag for PostgreSQL instance
- Enable Log Error Verbosity Flag for PostgreSQL
- Enable Log Events Data Sharing
- Enable Log Locks Wait Flag for PostgreSQL instance
- Enable Log Min Error Statement Flag for PostgreSQL
- Enable Log Min Messages Flag for PostgreSQL
- Enable Log Statement Flag for PostgreSQL
- Enable Network Policy on GKE Clusters
- Enable Private Clusters for GKE
- Enable Private Google Access for VPC Subnets
- Enable Private Google Access on an instance
- Enable SDP for Data Discovery
- Enable Shielded GKE Nodes on a Cluster
- Enable Shielded VM for Compute Engine Instances
- Enable Skip Show Database Flag for MySQL
- Enable SSL Encryption On AlloyDB Instances
- Enable System Use Notifications on VMs
- Enable the Confidential VM Organization Policy Constraint
- Enable Uniform Bucket-Level Access on Cloud Storage Buckets
- Enable VPC Flow Logs for Compute Engine Instances
- Enable Workload Identity Federation for GKE on clusters
- Encrypt Data at Rest with CMEK
- Encrypt Pub/Sub topic with CMEK
- Enforce 2-Step Verification for Super Admin Accounts
- Enforce CMEK for Supported Services
- Enforce Compute Session Inactive Policy
- Enforce Deny All Egress Firewall Rule
- Enforce Domain Restricted Sharing
- Enforce HTTPS Traffic Only
- Enforce IAM Least Privilege
- Enforce Least Privilege
- Enforce Least Privilege Guide
- Enforce Separation of Duties
- Enforce Session Lock Policy
- Enforce SSL Encryption for Remote Access
- Enforce SSL for all Incoming Database Connections
- Generate Auditable Events
- Implement Authorized Decision Makers for Access Requests
- Implement Centralized Security Monitoring
- Implement certificate lifecycle management
- Implement Continuous Network Traffic Monitoring
- Implement Error Handling Mechanism
- Implement Event Logging for Google Cloud Services
- Implement On-Demand Audit Log Access
- Implement Remote Access Policy
- Implement Secure Domain Name Resolution Service
- Implement Security Alert Advisory Management
- Import Google Workspace Audit Logs
- Inspect the External Load Balancer and SSL Connections
- Limit KMS Crypto Keys Users to Three
- Limit Super Admin Accounts
- Maintain Resource Isolation
- Manage Access to Audit Logs
- Manage Access to Google Cloud Resources from Mobile Devices
- Manage Data Handling and Retention
- Manage Malicious Code Protection Mechanisms
- Manage Publicly Accessible Content
- Manage System Integrity Policies and Procedures
- Perform Integrity Checks Every Month
- Prevent IP Forwarding on Compute Engine Instances
- Protect System Memory
- Remove Inactive Accounts
- Remove Temporary Accounts
- Require Additional Logging for Sensitive Buckets
- Require Audit Logging for Privileged Activities
- Require CMEK on Managed Service for Apache Spark Clusters
- Require Container-Optimized OS for a GKE Cluster
- Require Least Privilege
- Require Service Account Key Rotation
- Require Unique Super Admin Account
- Restrict Access Control Points for Authorized and Managed Remote Access
- Restrict Access to Audit Logs
- Restrict API Access to Google Cloud APIs for Compute Engine Instances
- Restrict Cloud Shell Access Settings
- Restrict CMEK Crypto Key Projects
- Restrict External IP Addresses to Specific VM Instances
- Restrict Insecure SSL Policies for Compute Engine Instances
- Restrict Legacy TLS Versions
- Restrict Non CMEK Services
- Restrict Non-Privileged Users from Executing Privileged Functions
- Restrict Public Access to BigQuery Datasets
- Restrict Public Access to Cloud SQL Database Instances
- Restrict Public Access to Cloud Storage Buckets
- Restrict Public IP Addresses to Compute Engine Instances
- Restrict User Managed Service Account Keys
- Restrict VM IP Forwarding for Compute Engine Instances
- Restrict VPC Networks on Agent Platform Workbench Instances
- Retain Audit Records
- Review Authentication, Authorization, User Account Management
- Review Log and Alert Configuration
- Separate User and Administrator Roles
- Set Ingress and Egress Controls for Compute
- Set Log Bucket Flag for Bucket Logging
- Set Log Error Verbosity Flag for AlloyDB Instances
- Set Log Min Error Statement Flag for AlloyDB Instances
- Set Log Min Messages Flag for AlloyDB Instances
- Set Uniform Bucket Level Access for Cloud Storage Buckets
- Set Up Job Scheduling and Configurations
- Subscribe a GKE Cluster to a Release Channel
- Synchronize System Clocks
- Terminate Network Connections
- Triage and Remediate System Flaws
- Turn Off Contained Database Authentication Flag for SQL Server
- Turn Off Cross Database Ownership Chaining Flag for SQL Server
- Turn Off External Scripts Flag for SQL Server
- Turn off Log Hostname Flag for PostgreSQL
- Turn Off Log Min Duration Statement Flag for PostgreSQL
- Turn Off Remote Access Flag for SQL Server
- Use Custom Service Accounts for Compute Engine Instances
- Use Custom VPC Networks
- Use IAM Tags
- Use Least Privilege Service Accounts for GKE Clusters
- Use Secure Web Proxy for Network Traffic Control
- Use TLS 1.2 or Higher
- Verify Cloud KMS Key Version Algorithm
dora-article-10
Financial entities must implement mechanisms for prompt detection of anomalous activities and support ICT related incident response.
- Automate Integrity Verification
- Automate Near Real-time Event Analysis
- Block Generic Access to RDP Ports
- Block Generic Access to SSH Ports
- Block Legacy Authorization on GKE Clusters
- Configure a Wireless Intrusion Detection Mechanism
- Configure Log Metrics and Alerts for Cloud Storage IAM Policy Changes
- Configure Security Logging Policies for Google Cloud Services
- Create Artifact Registry Cleanup Policies
- Disable Alpha Features on GKE Clusters
- Employ Monthly Checks for Flaw Remediation Status
- Enable Artifact Analysis Vulnerability Scanning
- Enable Audit Logs Bucket Enumeration
- Enable Audit Logs for All Services
- Enable Cloud Logging on GKE Clusters
- Enable Cloud Monitoring on GKE Clusters
- Enable Data Write Audit Logs for Organization Policy
- Enable Intranode Visibility for GKE Clusters
- Enable Log Checkpoints Flag for PostgreSQL
- Enable Log Connections Flag for PostgreSQL
- Enable Log Disconnections Flag for PostgreSQL
- Enable Log Duration Flag for PostgreSQL instance
- Enable Log Error Verbosity Flag for PostgreSQL
- Enable Log Locks Wait Flag for PostgreSQL instance
- Enable Log Min Error Statement Flag for PostgreSQL
- Enable Log Min Messages Flag for PostgreSQL
- Enable Log Statement Flag for PostgreSQL
- Generate Auditable Events
- Implement Alerting for Incidence Response
- Implement Audit Lifecycle Management
- Implement Centralized Security Monitoring
- Implement Error Handling Mechanism
- Implement Event Logging for Google Cloud Services
- Implement Security Alert Advisory Management
- Import Google Workspace Audit Logs
- Incorporate Integrity Monitoring into Incident Response
- Limit Super Admin Accounts
- Manage Access to Audit Logs
- Manage Data Handling and Retention
- Manage Malicious Code Protection Mechanisms
- Manage System Integrity Policies and Procedures
- Perform Integrity Checks Every Month
- Prevent IP Forwarding on Compute Engine Instances
- Protect System Memory
- Require Additional Logging for Sensitive Buckets
- Require Container-Optimized OS for a GKE Cluster
- Restrict Access to Audit Logs
- Restrict Resource Service Usage
- Retain Audit Records
- Review Log and Alert Configuration
- Set Log Bucket Flag for Bucket Logging
- Set Log Error Verbosity Flag for AlloyDB Instances
- Set Log Min Error Statement Flag for AlloyDB Instances
- Set Log Min Messages Flag for AlloyDB Instances
- Subscribe a GKE Cluster to a Release Channel
- Synchronize System Clocks
- Triage and Remediate System Flaws
- Turn Off External Scripts Flag for SQL Server
- Turn off Log Hostname Flag for PostgreSQL
- Turn Off Log Min Duration Statement Flag for PostgreSQL
EU Data Boundary
Supported cloud provider: Google Cloud
EU Data Boundary sets data location controls to support EU-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
EU Data Boundary and Support
Supported cloud provider: Google Cloud
EU Data Boundary and Support sets data location controls to support EU-only regions. Support access controls are set to EU support personnel based in the EU.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
EU Data Boundary with Access Justifications
Supported cloud provider: Google Cloud
The EU Data Boundary with Access Justifications sets data location controls to support EU-only regions. Support access controls are set to support personnel who are based in the EU and provides data residency and data sovereignty assurances for EU-based customers.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Auto Approval of Access Approval Emergency Response
- Disable Compute Instance Data Access APIs
- Disable diagnostic and administrative access pathways in Cloud SQL
- Disable Enhanced Text Search for Firestore
- Disable GKE Diagnostic Administrative Access
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Disable SSH In Browser
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Regulatory Settings for Apigee
- Enforce allowed CMEK crypto key projects
- Enforce Uniform Bucket-Level Access for Cloud Storage Buckets
- Require CMEK Protection
- Restrict Access to VM Core Memory
- Restrict Authorization Types for Cloud Storage
- Restrict Cloud SQL Resource Creation
- Restrict Resource Locations
- Restrict Service Usage
- Restrict the BigQuery Data Transfer Service API
- Restrict TLS Versions
- Specify Cloud KMS Key Protection Levels
FedRAMP 20x Class C
Supported cloud provider: Google Cloud
A Government-wide program that provides a standardized, reusable approach to security assessment and authorization for cloud computing products and services that process unclassified information used by agencies. FedRAMP Moderate impact is most appropriate for CSOs where the loss of confidentiality, integrity and availability would result in serious adverse effect on an agency's operations, assets or individuals.
This framework includes the cloud control groups and cloud controls in the following sections.
ksi-ced-rat
The effectiveness of relevant cybersecurity education and training is persistently reviewed, including at least general training for all employees, role-specific training for employees in high risk roles, training for development and engineering staff on secure software delivery, and training for staff involved with incident response or disaster recovery.
ksi-cmt-lmc
Modifications to the cloud service offering are logged and monitored.
- Generate Auditable Events
- Implement Audit Lifecycle Management
- Implement Event Logging for Google Cloud Services
- Use Central SIEM
ksi-cmt-rmv
Changes to machine-based information resources are executed through the redeployment of version controlled resources rather than direct modification wherever reasonable.
- Enforce Configuration Management for IAC
- Guidance for Immutable Infrastructure on Google Cloud
- Manage Configurations Centrally
ksi-cmt-vtd
Persistent testing and validation of changes throughout deployment is automated.
ksi-cna-dfp
The functionality and privileges for infrastructure and services are strictly defined.
- Define Agent Platform Workbench Instance Access Mode
- Define External Build Integrations for Cloud Build
- Define Worker Pools for Cloud Builds
- Enable Workload Identity Federation for GKE on clusters
- Enforce Agent Platform Environment Options
- Remove Overprivileged Service Accounts
- Restrict API Access to Google Cloud APIs for Compute Engine Instances
- Restrict API Keys for Required APIs Only
- Restrict Legacy IAM Roles
- Restrict Resource Service Usage
- Use Custom Service Accounts for Compute Engine Instances
- Use Least Privilege Service Accounts for GKE Clusters
ksi-cna-eis
Use automated services to persistently assess the security posture of all machine-based information resources and automatically enforce their intended operational state.
- Enable Auto Repair for GKE Clusters
- Enable Auto Upgrade on GKE Clusters
- Require Auto Upgrade Schedule Set for Agent Platform Workbench
ksi-cna-ibp
The use and configuration of third-party machine-based information resources is persistently compared against the original provider's best practices and guidance.
- Block Automatic IAM Grants to Default Service Accounts
- Enable Auto Repair for GKE Clusters
- Enable Integrity Monitoring for Agent Platform Workbench Instances
- Enable Integrity Monitoring on GKE Clusters
- Enable Secure Boot for Agent Platform Workbench Instances
- Enable Secure Boot for Shielded GKE Nodes
- Enable Secure Boot for Vertex AI Runtime Templates
- Enable Secure Boot on Compute Engine Instances
- Enable Shielded GKE Nodes on a Cluster
- Enable Shielded VM for Compute Engine Instances
- Enable vTPM on Agent Platform Workbench Instances
- Enforce Domain Restricted Sharing
- Require Auto Upgrade Schedule Set for Agent Platform Workbench
- Require Container-Optimized OS for a GKE Cluster
- Restrict Resource Service Usage
ksi-cna-mat
Machine-based information resources are persistently reviewed to ensure they have a minimal attack surface and that lateral movement is minimized if compromised.
- Block Project-Wide SSH Keys on Compute Engine Instances
- Block Serial Ports for Compute Engine Instances
- Configure VPC Firewall Rules, Subnets, and VPN Gateway
- Disable Alpha Features on GKE Clusters
- Disable Client Certificate Authentication for GKE
- Disable Legacy Metadata Server Endpoints on Kubernetes Clusters
- Don't Use Kubernetes Web UI
- Don't Use Legacy Networks
- Enable Network Policy on GKE Clusters
- Enable Shielded GKE Nodes on a Cluster
- Prevent IP Forwarding on Compute Engine Instances
- Prevent Nested Virtualization for Compute Engine VMs
- Require Container-Optimized OS for a GKE Cluster
- Restrict Default Network Creation for Compute Engine Instances
- Review Artifact Registry Images
- Review Cloud Run Images
ksi-cna-ofa
Machine-based information resources are persistently reviewed to ensure they are appropriately optimized for high availability and rapid recovery.
- Assess the Availability of Compute and GKE Resources
- Enable AlloyDB Automated Backups on Cluster
- Enable Auto Repair for GKE Clusters
- Enable Automatic Backups for Cloud SQL Databases
- Enable Object Versioning on Buckets
ksi-cna-rnt
Machine-based information resources are persistently reviewed to ensure they are appropriately configured to limit inbound and outbound network traffic.
- Block External IP Address Access on Compute Engine VM Instances
- Block Generic Access to RDP Ports
- Block Generic Access to SSH Ports
- Block Internet Access for Vertex AI Runtime Templates
- Block Public IP Address for Agent Platform Workbench Instances
- Block Public IP Addresses for AlloyDB Cluster Instances
- Block Public IP Addresses for Cloud SQL Instances
- Configure the Allowed Ingress Settings for Cloud Run Organization Policy Constraint
- Configure the Allowed VPC Egress Settings for Cloud Run Organization Policy Constraint
- Configure the Disable VPC External IPv6 Usage Organization Policy
- Configure VPC Firewall Rules, Subnets, and VPN Gateway
- Define VPC Connector Egress For Cloud Run Functions
- Enable Control Plane Authorized Networks on GKE Clusters
- Enable Network Policy on GKE Clusters
- Enable Private Clusters for GKE
- Enable the Restrict Authorized Networks on Cloud SQL Instances Organization Policy Constraint
- Inspect the External Load Balancer and SSL Connections
- Restrict Default Network Creation for Compute Engine Instances
- Restrict Public IP Addresses on Agent Platform Workbench Notebooks and Instances
- Restrict Public IP Addresses to Compute Engine Instances
- Restrict VM IP Forwarding for Compute Engine Instances
- Retrieve Cloud NAT Configurations
ksi-cna-rvp
The effectiveness of protection against denial of service attacks and other unwanted activity for machine-based information resources is persistently reviewed.
ksi-cna-uln
Logical networking and related capabilities are used and persistently reviewed to enforce traffic flow controls.
- Block Generic Access to DNS Ports from All IP Addresses
- Block Generic Access to HTTP Ports
- Block Generic Access to NetBIOS Ports from All IP Addresses
- Configure VPC Firewall Rules, Subnets, and VPN Gateway
- Define VPC Connector Egress For Cloud Run Functions
- Don't Use Legacy Networks
- Enable Network Policy on GKE Clusters
- Enable Private Clusters for GKE
- Restrict Default Network Creation for Compute Engine Instances
- Restrict Public IP Addresses to Compute Engine Instances
- Restrict VPC Networks on Agent Platform Workbench Instances
- Retrieve VPC Network Peering Configurations
ksi-iam-aam
Securely manage the lifecycle and privileges of all accounts, roles, and groups, using automation.
- Block Automatic IAM Grants to Default Service Accounts
- Disable Suspicious Accounts Automatically
- Enforce Least Privilege
- Review Authentication, Authorization, User Account Management
- Use Least Privilege and Just in Time Access
ksi-iam-apm
Secure passwordless methods are used for user authentication and authorization when feasible, otherwise strong passwords with phishing-resistant MFA is used.
- Enforce 2-Step Verification for Super Admin Accounts
- Enforce Two-Step Verification
- Use FIPS 201 Approved Products
- Use Multifactor or Passwordless Authentication
ksi-iam-elp
Identity and access management measures are used and persistently reviewed to ensure each user or device can only access the resources they need.
- Block Automatic IAM Grants to Default Service Accounts
- Block Legacy Authorization on GKE Clusters
- Create GKE Clusters with Limited Privileges
- Enable Uniform Bucket-Level Access on Cloud Storage Buckets
- Enable Workload Identity Federation for GKE on clusters
- Enforce Domain Restricted Sharing
- Enforce Least Privilege
- Remove Overprivileged Service Accounts
- Require Least Privilege
- Restrict Legacy IAM Roles
- Restrict the Use of Default Service Account for Agent Platform Workbench Instances
- Use Custom Service Accounts for Compute Engine Instances
- Use Google Groups for Kubernetes RBAC
- Use Least Privilege and Just in Time Access
- Use Least Privilege Service Accounts for GKE Clusters
ksi-iam-jit
A least-privileged, role and attribute-based, and just-in-time security authorization model is used and persistently reviewed for all user and non-user accounts and services.
- Block Legacy Authorization on GKE Clusters
- Enforce Least Privilege
- KSI-IAM-AAM: Automating Account Management by Confirming JIT Usage on Critical Roles
- Require Least Privilege
- Restrict Legacy IAM Roles
- Use Google Groups for Kubernetes RBAC
- Use Least Privilege and Just in Time Access
ksi-iam-snu
Appropriately secure authentication methods are used and persistently reviewed for non-user accounts and services.
- Block Service Account Key Creation
- Block Service Account Key Uploads
- Enable Workload Identity Federation for GKE on clusters
- Require Service Account Key Rotation
- Require Workload Identity Federation for GKE and the GKE Metadata Server
- Restrict API Keys for Required APIs Only
- Restrict User Managed Service Account Keys
- Set Application Restriction on API Keys
ksi-iam-sus
Accounts with privileged access are disabled or otherwise secured in response to suspicious activity.
ksi-inr-aar
Incident after action reports are generated and lessons learned are persistently incorporated.
ksi-inr-rir
The effectiveness of documented incident response procedures is persistently reviewed.
ksi-inr-rpi
Past incidents are persistently reviewed for patterns or vulnerabilities that were not previously apparent or identified.
ksi-mla-ala
Use a least-privileged, role and attribute-based, and just-in-time access authorization model for access to log data based on organizationally defined data sensitivity.
- KSI-MLA-ALA: Authorizing Log Access JIT Enablement
- KSI-MLA-ALA: Authorizing Log Access User Verification
- Manage Access to Audit Logs
- Restrict Access to Audit Logs
- Restrict Legacy IAM Roles
ksi-mla-evc
The configuration of machine-based information resources, especially infrastructure as code, is persistently evaluated and tested.
ksi-mla-let
Maintain a list of information resources and event types that will be logged, monitored, and audited, then do so.
- Enable Cloud DNS Logs Monitoring
- Enable Cloud Logging on GKE Clusters
- Enable Cloud Monitoring on GKE Clusters
- Enable Data Access Logs for AlloyDB
- Enable Data Access Logs for Bigtable
- Enable Data Access Logs for Cloud SQL
- Enable Data Access Logs for Cloud Storage
- Enable Data Access Logs for Datastore
- Enable Data Access Logs for Filestore
- Enable Data Access Logs for Firestore
- Enable Data Access Logs for Secret Manager
- Enable Data Access Logs for Spanner
- Enable Firewall Rule Logging
- Enable Intranode Visibility for GKE Clusters
- Enable Load Balancer Logging
- Enable Log Connections Flag for PostgreSQL
- Enable VPC Flow Logs for Compute Engine Instances
- Generate Auditable Events
- Require Cloud Storage Bucket Logging
- Require IAM Logs
ksi-mla-osm
A Security Information and Event Management (SIEM) or similar system(s) is used and persistently reviewed for centralized, tamper-resistant logging of events, activities, and changes.
- Enable Cloud Logging on GKE Clusters
- Require Audit Logging for Privileged Activities
- Store Audit Logs in a Separate Repository
- Use Central SIEM
ksi-piy-giv
Authoritative sources are used to automatically generate real-time inventories of all information resources when needed.
ksi-rpl-abo
The alignment of machine-based information resource backups with defined recovery objectives is persistently reviewed.
ksi-scr-mit
Persistently identify, review, and mitigate potential supply chain risks.
- Enable Artifact Analysis Vulnerability Scanning
- Enable Secure Boot on Compute Engine Instances
- Enable Shielded GKE Nodes on a Cluster
- Enable Shielded VM for Compute Engine Instances
ksi-scr-mon
Third party software information resources are automatically monitored for upstream vulnerabilities using mechanisms that may include contractual notification requirements or active monitoring services.
ksi-svc-asm
Management, protection, and regular rotation of digital keys, certificates, and other secrets is automated and persistently reviewed.
- Block Public Access to Cloud KMS Keys
- Define Rotation Period for Cloud KMS Keys
- Define Secret Manager Rotation Schedule
- Require Rotation of API Key
- Require Service Account Key Rotation
- Retrieve Cloud KMS Configurations
ksi-svc-eis
Information resources are persistently evaluated for opportunities to improve security and those improvements are persistently made.
- Enable Auto Upgrade on GKE Clusters
- Enable Automatic Upgrades for Agent Platform WorkBench Instances
- Require Auto Upgrade Schedule Set for Agent Platform Workbench
- Review Artifact Registry Images
- Review Cloud Run Images
- Review Hardened Compute Images
- Subscribe a GKE Cluster to a Release Channel
- Use Latest Image Versions on Managed Service for Apache Spark Clusters
ksi-svc-prr
Persistently review plans, procedures, and the state of information resources after making changes to limit and remove unwanted residual elements that would likely negatively affect the confidentiality, integrity, or availability of federal customer data.
ksi-svc-sin
Information is encrypted or otherwise secured from unwanted access or modification.
- Block Public Access to Cloud KMS Keys
- Enable DNSSEC for Cloud DNS
- Enable Encryption on GKE Clusters
- Enable SSL Encryption On AlloyDB Instances
- Enforce Public Access Prevention
- Enforce SSL for all Incoming Database Connections
- Restrict CMEK Crypto Key Projects
- Restrict Legacy TLS Versions
- Restrict Public Access to BigQuery Datasets
- Restrict Public Access to Cloud Storage Buckets
- Restrict Public Access to Compute Images
- Retrieve Cloud KMS Configurations
ksi-svc-vcm
Persistently validate the authenticity and integrity of communications between machine-based information resources using automation.
ksi-svc-vri
Use cryptographic methods to validate the integrity of machine-based information resources.
- Enable Integrity Monitoring for Agent Platform Workbench Instances
- Enable Integrity Monitoring on GKE Clusters
- Enable Secure Boot for Agent Platform Workbench Instances
- Enable Secure Boot for Shielded GKE Nodes
- Enable Secure Boot for Vertex AI Runtime Templates
- Enable Secure Boot on Compute Engine Instances
- Enable Shielded GKE Nodes on a Cluster
- Enable Shielded VM for Compute Engine Instances
- Enable vTPM on Agent Platform Workbench Instances
- Retrieve Binary Authorization Configurations
FedRAMP High
Supported cloud provider: Google Cloud
Data Boundary for FedRAMP High sets data location controls to support US-only regions. Support access controls for first-level and second-level support are set to support personnel who have completed enhanced background checks and are located in the US. This means that Assured Workloads support cases are restricted to FedRAMP-adjudicated support staff located in the US.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Define the Permitted Versions for Cloud Run Functions
- Disable Creation of Global Load Balancers
- Disable Enhanced Text Search for Firestore
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Enable Access Transparency
- Enable Compliance Regulatory Settings for Cloud Deploy
- Enable Compliance Regulatory Settings for NGFW Enterprise
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Identity
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Cloud DNS
- Enable Regulatory Settings for Gemini Enterprise
- Require OS Login
- Restrict Resource Locations
- Restrict Service Usage
- Restrict the BigQuery Data Transfer Service API
- Restrict TLS Versions
FedRAMP Moderate
Supported cloud provider: Google Cloud
Data Boundary for FedRAMP Moderate sets support access controls for first-level and second-level support personnel who have completed enhanced background checks. This means that Assured Workloads support cases are restricted to FedRAMP-adjudicated first-level and second-level support staff. The FedRAMP Moderate control baseline is a subset of the FedRAMP High control baseline. Therefore, if you're pursuing a FedRAMP Moderate ATO for your workloads deployed in Assured Workloads, you can use any FedRAMP High authorized Google Cloud service in your FedRAMP Moderate workloads.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Enable Compliance Regulatory Settings for NGFW Enterprise
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Cloud DNS
- Enable Regulatory Settings for Gemini Enterprise
- Require OS Login
- Restrict Resource Locations
- Restrict Service Usage
- Restrict the BigQuery Data Transfer Service API
- Restrict TLS Versions
HIPAA
Supported cloud provider: Google Cloud
Health Insurance Portability and Accountability Act
This framework includes the cloud control groups and cloud controls in the following sections.
hipaa-security-ss164-308-a-3-i-workforce-security
Implement policies and procedures to ensure that all members of its workforce have appropriate access to electronic protected health information and to prevent those workforce members who do not have access from obtaining access to electronic protected health information.
- Enable Skip Show Database Flag for MySQL
- Restrict Public IP Addresses to Compute Engine Instances
- Set Uniform Bucket Level Access for Cloud Storage Buckets
- Turn Off Contained Database Authentication Flag for SQL Server
- Turn Off Cross Database Ownership Chaining Flag for SQL Server
hipaa-security-ss164-308-a-3-ii-a-workforce-security-authorization-and-or-supervision
Implement procedures for the authorization and/or supervision of workforce members who work with EPHI or in locations where it might be accessed.
- Enable Skip Show Database Flag for MySQL
- Restrict Public IP Addresses to Compute Engine Instances
- Set Uniform Bucket Level Access for Cloud Storage Buckets
- Turn Off Contained Database Authentication Flag for SQL Server
- Turn Off Cross Database Ownership Chaining Flag for SQL Server
hipaa-security-ss164-308-a-7-ii-a-contingency-plan-data-backup-plan
Establish and implement procedures to create and maintain retrievable exact copies of EPHI.
hipaa-security-ss164-310-d-2-iii-device-and-media-controls-accountability
Maintain a record of the movements of hardware and electronic media and any person responsible therefore.
hipaa-security-ss164-312-a-1-access-control
Implement technical policies and procedures for electronic information systems that maintain electronic protected health information to allow access only to those persons or software programs that have been granted access rights
- Enable Skip Show Database Flag for MySQL
- Restrict Public IP Addresses to Compute Engine Instances
- Set Uniform Bucket Level Access for Cloud Storage Buckets
- Turn Off Contained Database Authentication Flag for SQL Server
- Turn Off Cross Database Ownership Chaining Flag for SQL Server
hipaa-security-ss164-312-a-2-iv-access-control-encryption-and-decryption
Implement a mechanism to encrypt and decrypt EPHI.
- Block Project-Wide SSH Keys on Compute Engine Instances
- Define Rotation Period for Cloud KMS Keys
- Enable CMEK for BigQuery Tables
- Enable Confidential Computing for Compute Engine Instances
- Enforce SSL for all Incoming Database Connections
- Require CMEK on Managed Service for Apache Spark Clusters
hipaa-security-ss164-312-b-audit-controls
Implement hardware, software, and/or procedural mechanisms that record and examine activity in information systems that contain or use electronic protected health information.
hipaa-security-ss164-312-e-1-transmission
Implement technical security measures to guard against unauthorized access to electronic protected health information that is being transmitted over an electronic communications network.
- Block Project-Wide SSH Keys on Compute Engine Instances
- Enforce SSL for all Incoming Database Connections
hipaa-security-ss164-312-e-2-i-transmission-security-integrity-controls
Implement security measures to ensure that electronically transmitted EPHI is not improperly modified without detection until disposed of.
- Block Project-Wide SSH Keys on Compute Engine Instances
- Enforce SSL for all Incoming Database Connections
hipaa-security-ss164-312-e-2-ii-transmission-security-encryption
Implement a mechanism to encrypt EPHI whenever deemed appropriate.
- Block Project-Wide SSH Keys on Compute Engine Instances
- Define Rotation Period for Cloud KMS Keys
- Enable CMEK for BigQuery Tables
- Enable Confidential Computing for Compute Engine Instances
- Enforce SSL for all Incoming Database Connections
- Require CMEK on Managed Service for Apache Spark Clusters
Hong Kong Data Boundary
Supported cloud provider: Google Cloud
Hong Kong Data Boundary sets data location controls to support Hong Kong-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
IL2
Supported cloud provider: Google Cloud
Data Boundary for IL2 sets data location controls to support US-only regions. Support access controls are set to support personnel who have completed enhanced background checks, are US Persons, and are located in the United States.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Define the Permitted Versions for Cloud Run Functions
- Disable Creation of Global Load Balancers
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Enable Access Transparency
- Enable Compliance Regulatory Settings for Cloud Deploy
- Enable Compliance Regulatory Settings for NGFW Enterprise
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Identity
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Cloud DNS
- Enable Regulatory Settings for Gemini Enterprise
- Require OS Login
- Restrict Resource Locations
- Restrict Service Usage
- Restrict the BigQuery Data Transfer Service API
- Restrict TLS Versions
IL4
Supported cloud provider: Google Cloud
Data Boundary for IL4 sets data location controls to support US-only regions. Support access controls are set to support personnel who have completed enhanced background checks, are US Persons, and are located in the United States.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Compute Instance Data Access APIs
- Disable Creation of Global Load Balancers
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Disable GKE Diagnostic Administrative Access
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Compliance Settings for Cloud Identity
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Regulatory Settings for Cloud DNS
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
- Specify Cloud KMS Key Protection Levels
IL5
Supported cloud provider: Google Cloud
Data Boundary for IL5 sets data location controls to support US-only regions. Support access controls are set to support personnel who have completed enhanced background checks, are US Persons, and are located in the United States.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- Allow Only IL5 Compliant APIs for Gemini Enterprise Agent Platform
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Create CMEK Project and Key Ring
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Compute Instance Data Access APIs
- Disable Creation of Global Load Balancers
- Disable diagnostic and administrative access pathways in Cloud SQL
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Service Account Key Creation
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Compliance Settings for Cloud Identity
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Regulatory Settings for Cloud DNS
- Enable Regulatory Settings for Gemini Enterprise
- Enforce allowed CMEK crypto key projects
- Prevent Automatic Creation of Default Network
- Prevent Automatic Granting of Editor Role to Default Service Accounts
- Require CMEK Protection
- Restrict Cloud SQL Resource Creation
- Restrict Public Access to Data Stored in Buckets
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
- Set Zonal DNS as Default for Compute Engine
- Specify Cloud KMS Key Protection Levels
India Data Boundary
Supported cloud provider: Google Cloud
India Data Boundary sets data location controls to support India-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
India Data Boundary for MeitY
Supported cloud provider: Google Cloud
Helps achieve data residency and sovereignty, and supports compliance with India's Ministry of Electronics and Information Technology (MeitY) MeghRaj GI Cloud empanelment guidelines, CERT-In cybersecurity directions, IT Amendment Rules, and the Digital Personal Data Protection (DPDP) Act.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Define the Permitted Versions for Cloud Run Functions
- Disable Compute Instance Data Access APIs
- Disable Creation of Global Load Balancers
- Disable Creation of Global Self-managed SSL Certificates
- Disable diagnostic and administrative access pathways in Cloud SQL
- Disable Enhanced Text Search for Firestore
- Disable GKE Diagnostic Administrative Access
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Service Account Key Creation
- Disable Spanner Multi-Region Instances
- Disable SSH In Browser
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Regulatory Settings for Cloud Deploy
- Enable Compliance Regulatory Settings for NGFW Enterprise
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Cloud DNS
- Enable Regulatory Settings for Gemini Enterprise
- Enforce In-Transit Regions for Pub/Sub Messages
- Enforce Uniform Bucket-Level Access for Cloud Storage Buckets
- Restrict Access to VM Core Memory
- Restrict Authorization Types for Cloud Storage
- Restrict Cloud SQL Resource Creation
- Restrict Public Access to Data Stored in Buckets
- Restrict Resource Locations
- Restrict Service Usage
- Restrict the BigQuery Data Transfer Service API
- Restrict TLS Versions
- Set Zonal DNS as Default for Compute Engine
- Specify Cloud KMS Key Protection Levels
Indonesia Data Boundary
Supported cloud provider: Google Cloud
Indonesia Data Boundary sets data location controls to support Indonesia-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Data Boundary for IRS Publication 1075
Supported cloud provider: Google Cloud
Data Boundary for IRS Publication 1075 sets data location controls to support US-only regions. Support access controls are set to support personnel who have completed fingerprint-based CJIS background checks, state-level law enforcement checks, and citizenship verification. This means that Assured Workloads support cases are restricted to background-checked staff located in the US. Escorted session controls are also used to supervise and monitor support actions by non-background checked staff.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Define the Permitted Versions for Cloud Run Functions
- Disable Creation of Global Load Balancers
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Enable Access Transparency
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Identity
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict the BigQuery Data Transfer Service API
- Restrict TLS Versions
Israel Data Boundary
Supported cloud provider: Google Cloud
Israel Data Boundary sets data location controls to support Israel-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Israel Data Boundary and Support
Supported cloud provider: Google Cloud
Israel Data Boundary and Support sets data location controls to support Israel-only regions. Support access controls are set to support personnel who are either security-cleared Israeli Personnel located in Israel or US Persons who have completed enhanced background checks located in the US.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
ITAR
Supported cloud provider: Google Cloud
Data Boundary for ITAR sets data location controls to support US-only regions. Support access controls are set to support personnel who are US Persons, and are located in the US. This means that Assured Workloads support cases are restricted to US Persons located in the US.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- Allow Only ITAR Compliant APIs for Gemini Enterprise Agent Platform
- BigQuery compliance settings
- Cloud Build Regulatory Settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Cloud Serverless for Apache Spark to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Create CMEK Project and Key Ring
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Compute Instance Data Access APIs
- Disable Creation of Global Load Balancers
- Disable Creation of Global Self-managed SSL Certificates
- Disable Enhanced Text Search for Firestore
- Disable Ephemeral Disk Storage for Cloud Run Jobs
- Disable Ephemeral Disk Storage for Cloud Run Services
- Disable Ephemeral Disk Storage for Cloud Run Worker Pools
- Disable GKE Diagnostic Administrative Access
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Regulatory Settings for Cloud Deploy
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enforce allowed CMEK crypto key projects
- Enforce In-Transit Regions for Pub/Sub Messages
- Require CMEK Protection
- Restrict Access to VM Core Memory
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Japan Data Boundary
Supported cloud provider: Google Cloud
Japan Data Boundary sets data location controls to support Japan-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Kingdom of Saudi Arabia Data Boundary with Access Justifications
Supported cloud provider: Google Cloud
The Kingdom of Saudi Arabia (KSA) Data Boundary with Access Justifications is restricted to customers with a billing address that is located outside of KSA, whether for a business, residence, or a domicile. This control package sets data location controls to support the me-central2 region.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Auto Approval of Access Approval Emergency Response
- Disable Compute Instance Data Access APIs
- Disable Creation of Global Load Balancers
- Disable diagnostic and administrative access pathways in Cloud SQL
- Disable GKE Diagnostic Administrative Access
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Disable SSH In Browser
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enforce In-Transit Regions for Pub/Sub Messages
- Enforce Uniform Bucket-Level Access for Cloud Storage Buckets
- Restrict Access to VM Core Memory
- Restrict Authorization Types for Cloud Storage
- Restrict Cloud SQL Resource Creation
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
- Specify Cloud KMS Key Protection Levels
Qatar Data Boundary
Supported cloud provider: Google Cloud
Qatar Data Boundary sets data location controls to support Qatar-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Singapore Data Boundary
Supported cloud provider: Google Cloud
Singapore Data Boundary sets data location controls to support Singapore-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
South Africa Data Boundary
Supported cloud provider: Google Cloud
South Africa Data Boundary sets data location controls to support South Africa-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
South Korea Data Boundary
Supported cloud provider: Google Cloud
South Korea Data Boundary sets data location controls to support South Korea-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Switzerland Data Boundary
Supported cloud provider: Google Cloud
Switzerland Data Boundary sets data location controls to support Switzerland-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Switzerland Data Boundary with EU Support
Supported cloud provider: Google Cloud
Switzerland Data Boundary with EU Support sets data location controls to support Switzerland-only regions. Support access controls are set to EU support personnel based in the EU.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Create CMEK Project and Key Ring
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Switzerland Data Boundary with Access Justifications
Supported cloud provider: Google Cloud
Switzerland Data Boundary with Access Justifications sets data location controls to support Switzerland-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Global Cloud Armor Policies
- Enable Access Transparency
- Enable Compliance Settings for Cloud Logging
- Enforce allowed CMEK crypto key projects
- Require CMEK Protection
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
Taiwan Data Boundary
Supported cloud provider: Google Cloud
Taiwan Data Boundary sets data location controls to support Taiwan-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
UK Data Boundary
Supported cloud provider: Google Cloud
UK Data Boundary sets data location controls to support UK-only regions.
This framework includes the following cloud controls:
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
US Data Boundary
Supported cloud provider: Google Cloud
US Data Boundary sets data location controls to support US-only regions.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
US Data Boundary and Support
Supported cloud provider: Google Cloud
US Data Boundary and Support sets data location controls to support US-only regions. Support access controls are set to support personnel who are US Persons and are located in the US.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Google Agent Platform to Support Data Boundaries
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure NetApp Volumes to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Enhanced Text Search for Firestore
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
US Data Boundary for Healthcare and Life Sciences
Supported cloud provider: Google Cloud
US Data Boundary for Healthcare and Life Sciences sets data location controls to support US-only regions.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
US Data Boundary for Healthcare and Life Sciences with Support
Supported cloud provider: Google Cloud
US Data Boundary for Healthcare and Life Sciences with Support sets data location controls to support US-only regions.
This framework includes the following cloud controls:
- Allow Only Compliant APIs for Agent Platform
- BigQuery compliance settings
- Cloud Databases Context Store Regulatory Settings
- Configure Knowledge Catalog to Support Data Boundaries
- Configure Managed Service for Apache Spark to Support Data Boundaries
- Configure Spanner to Support Data Boundaries
- Define Locations for Default and Required Cloud Logging Buckets
- Define Locations for Technical Support Services
- Disable Global Cloud Armor Policies
- Disable Pub/Sub Subscription Message Transforms
- Disable Pub/Sub Topic Message Transforms
- Disable Spanner Multi-Region Instances
- Enable Access Transparency
- Enable Advanced Service Controls for Spanner
- Enable Compliance Settings for Backup and DR
- Enable Compliance Settings for Cloud Logging
- Enable Compliance Settings for Cloud Monitoring
- Enable Compliance Settings for Looker (Google Cloud core)
- Enable Regulatory Settings for Apigee
- Enable Regulatory Settings for Gemini Enterprise
- Restrict Resource Locations
- Restrict Service Usage
- Restrict TLS Versions
What's next
- Learn more about Assured Workloads frameworks.
- Learn how to manage frameworks.