Assured Workloads helps ensure that your Google Cloud Armor deployments across your organization are configured in a compliant manner. You create a folder that contains the projects in which you want to maintain compliance, and then apply one or more control packages to that folder to enforce those controls across all of those projects. This document explains what control packages you can apply to Google Cloud Armor resources, and highlights what resources aren't supported by Assured Workloads.
Maintain compliance through Assured Workloads
Google Cloud Armor can be deployed in configurations which satisfy a variety of global, country specific, or industry specific compliance frameworks. A comprehensive list of supported compliance offerings across Google Cloud and whether Google Cloud Armor is in scope for them can be found in our Compliance Offerings.
Control packages by security policy type
The following table explains what control packages are available for each security policy type. For more information about these control packages and to search for the control packages that support Google Cloud Armor, see supported products by control package.
Control package | Global backend security policy | Edge security policy | Regional backend security policy | Network edge security policy |
---|---|---|---|---|
Criminal Justice Information Systems (CJIS) | ||||
FedRAMP High | Under JAB review | |||
FedRAMP Moderate | Under JAB review | |||
Healthcare and Life Sciences Controls | ||||
Healthcare and Life Sciences Controls with US support | ||||
Impact Level 2 (IL2) | ||||
Impact Level 4 (IL4) | ||||
Impact Level 5 (IL5) | ||||
International Traffic in Arms Regulations (ITAR) | ||||
IRS Publication 1075 | ||||
Regions where Google Cloud Armor is listed | ||||
Regions and Support where Google Cloud Armor is listed | ||||
EU Regions and Support with Sovereignty controls | ||||
Sovereign Controls for Kingdom of Saudi Arabia |