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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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.

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.

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.

dora-article-10

Financial entities must implement mechanisms for prompt detection of anomalous activities and support ICT related incident response.

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:

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:

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:

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.

ksi-cmt-rmv

Changes to machine-based information resources are executed through the redeployment of version controlled resources rather than direct modification wherever reasonable.

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.

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.

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.

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.

ksi-cna-ofa

Machine-based information resources are persistently reviewed to ensure they are appropriately optimized for high availability and rapid recovery.

ksi-cna-rnt

Machine-based information resources are persistently reviewed to ensure they are appropriately configured to limit inbound and outbound network traffic.

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.

ksi-iam-aam

Securely manage the lifecycle and privileges of all accounts, roles, and groups, using automation.

ksi-iam-apm

Secure passwordless methods are used for user authentication and authorization when feasible, otherwise strong passwords with phishing-resistant MFA is used.

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.

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.

ksi-iam-snu

Appropriately secure authentication methods are used and persistently reviewed for non-user accounts and services.

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-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.

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.

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.

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.

ksi-svc-eis

Information resources are persistently evaluated for opportunities to improve security and those improvements are persistently made.

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.

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.

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:

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:

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.

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.

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

hipaa-security-ss164-312-a-2-iv-access-control-encryption-and-decryption

Implement a mechanism to encrypt and decrypt EPHI.

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.

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.

hipaa-security-ss164-312-e-2-ii-transmission-security-encryption

Implement a mechanism to encrypt EPHI whenever deemed appropriate.

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

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:

What's next