1. Docs
  2. Reference
  3. Pre-built Policy Packs
  4. HITRUST
  5. Google Cloud

HITRUST CSF 11.5 - Google Cloud

    This page lists all 72 policies in the HITRUST CSF 11.5 pack for Google Cloud.

    Policy NameDescriptionFramework ReferenceFramework Specification
    kms-key-iamRequire proper access controls for Cloud KMS key IAM policies01.a Access Control PolicyA privilege management process shall be implemented and include the allocation of different levels of access privileges, the authorization process for such privileges, and the maintenance of all privileges on a system.
    service-account-restricted-namesRestrict default service account creation with prohibited names01.b User RegistrationThere shall be a formal user registration and de-registration procedure in place governing the allocation of access rights to all information systems and services.
    iam-no-broad-rolesEnforce least privilege access control by prohibiting overly broad roles01.c Privilege ManagementA privilege management process shall be implemented to ensure that the allocation of access rights is appropriately restricted.
    pubsub-topic-iam-least-privilegeEnforce least privilege IAM policies for Pub/Sub topics01.c Privilege ManagementA privilege management process shall be implemented and include the allocation of different levels of access privileges, the authorization process for such privileges, and the maintenance of all privileges on a system.
    pubsub-subscription-iam-least-privilegeEnforce least privilege IAM policies for Pub/Sub subscriptions01.c Privilege ManagementA privilege management process shall be implemented and include the allocation of different levels of access privileges, the authorization process for such privileges, and the maintenance of all privileges on a system.
    cloudfunctions-iam-source-restrictionsRequire Cloud Functions IAM bindings to configure source restrictions01.c Privilege ManagementA privilege management process shall be implemented to ensure that the allocation of access rights is appropriately restricted.
    service-account-keyEnsure proper service account key usage and prohibit insecure authentication methods01.p Secure Log-on ProceduresSecure logon procedures shall be implemented to prevent unauthorized access. Where password authentication is used, the system shall enforce a secure password policy.
    cloudfunctions-execution-timeLimit Cloud Functions execution time to prevent extended access01.u Limitation of Connection TimeConnection times shall be limited to minimize the opportunity for unauthorized access.
    bucket-iam-least-privilegeEnforce least privilege access for Cloud Storage bucket IAM policies01.v Information Access RestrictionAccess rights shall be regularly reviewed and updated according to business requirements and personal changes. The access to information and application system functions shall be restricted according to business requirements and defined and documented in the access control policy.
    private-service-connectRequire Private Service Connect endpoints to have restrictive security policies01.v Information Access RestrictionAccess to information shall be restricted to authorized users and limited to authorized uses.
    compute-instance-encrypted-attached-diskRequire Compute Engine instances to have encrypted attached disks06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    compute-instance-encrypted-boot-diskRequire Compute Engine instances to have encrypted boot disks06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    instance-template-encrypted-diskRequire instance templates to have encrypted disks06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    instance-template-encrypted-boot-diskRequire instance templates to have encrypted boot disks06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    gke-secrets-encryptionRequire GKE clusters to have Application-layer Secrets Encryption enabled06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    bucket-customer-managed-kmsRequire Cloud Storage buckets to use customer-managed Cloud KMS keys for encryption06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    bucket-versioningRequire Cloud Storage buckets to have versioning enabled for data protection06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    pubsub-encryptionRequire Pub/Sub topics to have encryption enabled with customer-managed Cloud KMS keys06.d Data Protection and Privacy of Covered InformationCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    bucket-lifecycleRequire Cloud Storage buckets to have lifecycle management policies configured06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    hardcoded-secretsProhibit hardcoded secrets in code and configuration06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction.
    cloudsql-secure-credentialsRequire Cloud SQL instances to use secure master credentials management06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction.
    pubsub-message-retentionRequire Pub/Sub subscriptions to have appropriate message retention policies06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction.
    bucket-dlp-accessRequire Cloud Storage buckets to have appropriate access for data classification services like Cloud DLP06.d Data Protection and Privacy of Covered InformationInformation in storage shall be protected from unauthorized disclosure, modification and destruction. The organization shall implement appropriate technical, physical and procedural safeguards to protect information assets from unauthorized access, use, disclosure, disruption, modification or destruction.
    cloudfunctions-documentationRequire Cloud Functions to have adequate documentation09.b Change ManagementChanges to information processing facilities and systems shall be controlled through appropriate change management procedures.
    resource-labelingRequire all GCP resources to have proper labeling for change tracking09.b Change ManagementChanges to information processing facilities and systems shall be controlled through the use of formal change management procedures.
    environment-labelRequire all labelable resources to have an environment label09.d Separation of Development Test and Operational EnvironmentsSegregation of test, development and operational environments shall be maintained to ensure that the test and development environments do not adversely impact the operational environment.
    single-environment-stackEnsure all resources in a stack belong to the same environment09.d Separation of Development Test and Operational EnvironmentsSegregation of test, development and operational environments shall be maintained to ensure that the test and development environments do not adversely impact the operational environment.
    bucket-access-loggingRequire Cloud Storage buckets to have access logging enabled for audit trails09.e Service DeliveryAutomated logging procedures shall be implemented to enable monitoring and detection of security events.
    gke-private-endpointsRequire GKE cluster API endpoints to be private09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications using the network, including information in transit.
    firewall-ssh-rdpEnforce firewall rule restrictions for SSH and RDP access09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    firewall-strictEnforce strict firewall rules with explicit allow/deny configuration09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    bucket-no-public-readRequire Cloud Storage buckets to disallow public read access09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications using the network, including information in transit.
    cloudsql-private-ipRequire Cloud SQL instances to be deployed with private IP only09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    compute-no-public-ipRequire Compute Engine instances to disallow public IP addresses09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications using the network, including information in transit.
    instance-template-no-public-ipRequire instance templates to disallow public IP addresses09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications using the network, including information in transit.
    bucket-uniform-accessRequire Cloud Storage buckets to have uniform bucket-level access enabled09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications using the network, including information in transit.
    cloud-armorRequire public-facing applications to have Cloud Armor protection09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    cloud-cdn-armorRequire Cloud CDN to have Cloud Armor configuration for DDoS protection09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    database-network-accessEnforce strict network access controls for database resources09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    firewall-no-http-ingressRequire firewall rules to disallow inbound HTTP traffic from unauthorized sources09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    firewall-no-public-ingressRequire firewall rules to disallow public internet ingress unless specifically authorized09.m Network ControlsNetworks shall be managed and controlled in order to protect the organization from threats and to maintain security for the systems and applications which use the network, and to protect information in transit.
    subnetwork-flow-logsRequire subnetworks to have flowLogsConfig enabled09.z Publicly Available InformationInformation shall be protected from unauthorized disclosure or modification to protect the organization from malicious attacks or unauthorized access attempts.
    load-balancer-loggingRequire Cloud Load Balancers to configure access logging09.z Publicly Available InformationInformation shall be protected from unauthorized disclosure or modification to protect the organization from malicious attacks or unauthorized access attempts.
    cloud-build-loggingRequire Cloud Build triggers to have secure logging configurations09.z Publicly Available InformationInformation shall be captured and maintained to support monitoring and auditing of security events and system activity.
    bigtable-change-streamsRequire Bigtable tables to have change streams enabled for change tracking10.c Control of Internal ProcessingControls shall be in place to ensure the correct processing of information in applications.
    cloudfunctions-kms-env-varsRequire Cloud Functions environment variables to be encrypted with Cloud KMS10.d Message IntegrityMessages shall be protected against unauthorized modification. Integrity controls shall be applied to detect unauthorized modification of information.
    cloudfunctions-loggingRequire Cloud Functions to have logging configuration enabled10.e Output Data ValidationOutput data shall be validated to ensure that stored data is not corrupted as a result of processing errors or deliberate acts.
    cloudsql-sslRequire Cloud SQL connections to use SSL/TLS encryption10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    persistent-disk-customer-kmsRequire Persistent Disks to use customer-managed encryption keys10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations, and with risk management requirements identified through the risk assessment process.
    kms-key-rotationRequire Cloud KMS keys to have key rotation enabled10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    bigquery-dataset-kmsRequire BigQuery datasets to use customer-managed Cloud KMS keys10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations, and with risk management requirements identified through the risk assessment process.
    load-balancer-tlsRequire Cloud Load Balancers to disallow unencrypted traffic10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    cloud-cdn-origin-tlsRequire Cloud CDN to use secure TLS to origin10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    dataflow-kmsRequire Dataflow jobs and pipelines to use customer-managed Cloud KMS keys10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations, and with risk management requirements identified through the risk assessment process.
    kms-key-configurationRequire proper Cloud KMS key creation and configuration10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    instance-template-customer-kmsRequire instance templates to use customer-managed Cloud KMS keys for disk encryption10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations, and with risk management requirements identified through the risk assessment process.
    artifactregistry-customer-kmsRequire Artifact Registry repositories to use customer-managed Cloud KMS keys for encryption10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations, and with risk management requirements identified through the risk assessment process.
    filestore-customer-kmsRequire Filestore instances to use customer-managed Cloud KMS keys for encryption10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    secretmanager-customer-kmsRequire Secret Manager secrets to use customer-managed Cloud KMS keys10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    kms-key-lifecycleRequire proper Cloud KMS key deletion and lifecycle management10.f Policy on the Use of Cryptographic ControlsCryptographic controls shall be used in compliance with all relevant agreements, laws and regulations.
    artifactregistry-immutable-imagesRequire Artifact Registry repositories to disallow mutable images for security and compliance10.h Control of Operational SoftwareThere shall be restrictions on the installation of software by users. Controls shall be in place to restrict access to program source code.
    cloudfunctions-runtime-versionsRestrict Cloud Functions to approved runtime versions only10.h Control of Operational SoftwareThere shall be restrictions on the installation of software by users. Controls shall be in place to restrict access to program source code.
    cloudsql-patchingRequire Cloud SQL instances to use managed service patching10.k Change Control ProceduresChange control procedures shall be established to ensure adequate assessment and authorization of all changes to information processing facilities.
    compute-osconfig-vulnerabilityRequire OS Config agent for vulnerability management on compute instances10.m Control of Technical VulnerabilitiesVulnerabilities shall be identified and associated with risk levels. Technical vulnerabilities of information systems shall be managed in a timely fashion.
    bucket-multi-regionRequire Cloud Storage buckets to have multi-region replication for business continuity12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
    cloudsql-backupRequire Cloud SQL instances to have backup retention enabled12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
    cloudsql-high-availabilityRequire Cloud SQL instances to have high availability configuration across zones12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
    pubsub-dead-letter-queueRequire Pub/Sub subscriptions to have dead letter queue configuration12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
    cloud-tasks-retry-configurationRequire Cloud Tasks queues to have proper retry configuration for business continuity12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
    load-balancer-multi-zoneRequire Cloud Load Balancers to be configured across multiple zones for high availability12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
    load-balancer-health-checksRequire Cloud Load Balancers to enable health checks for monitoring backend instance health12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
    firestore-pitrFirestore databases must have Point-In-Time Recovery (PITR) enabled for business continuity12.a Including Information Security in the Business Continuity ManagementInformation security continuity shall be embedded in the organization’s business continuity management systems.
      Neo just got smarter about infrastructure policy automation