Policy types for @turbot/gcp-functions

• GCP > Functions > API Enabled
• GCP > Functions > Approved Regions [Default]
• GCP > Functions > CMDB
• GCP > Functions > Enabled
• GCP > Functions > Function > Active
• GCP > Functions > Function > Active > Age
• GCP > Functions > Function > Active > Last Modified
• GCP > Functions > Function > Approved
• GCP > Functions > Function > Approved > Custom
• GCP > Functions > Function > Approved > Regions
• GCP > Functions > Function > Approved > Usage
• GCP > Functions > Function > CMDB
• GCP > Functions > Function > Policy
• GCP > Functions > Function > Policy > Trusted Access
• GCP > Functions > Function > Policy > Trusted Access > All Authenticated
• GCP > Functions > Function > Policy > Trusted Access > All Users
• GCP > Functions > Function > Policy > Trusted Access > Domains
• GCP > Functions > Function > Policy > Trusted Access > Groups
• GCP > Functions > Function > Policy > Trusted Access > Service Accounts
• GCP > Functions > Function > Policy > Trusted Access > Users
• GCP > Functions > Function > Regions
• GCP > Functions > Function > Usage
• GCP > Functions > Function > Usage > Limit
• GCP > Functions > Permissions
• GCP > Functions > Permissions > Levels
• GCP > Functions > Permissions > Levels > Modifiers
• GCP > Functions > Regions
• GCP > Functions > Trusted Domains [Default]
• GCP > Functions > Trusted Groups [Default]
• GCP > Functions > Trusted Service Accounts [Default]
• GCP > Functions > Trusted Users [Default]
• GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-functions
• GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-functions
• GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-functions

GCP > Functions > API Enabled

Check whether GCP Functions API is enabled.

API Enabled refers specifically to the API state of a service in a cloud project.
This control determines whether the API state is set as per desired level.

The GCP > Functions > API Enabled control compares
the API state against the API Enabled policies,
raises an alarm, and takes the defined enforcement action.

[
  "Skip",
  "Check: Disabled",
  "Check: Enabled",
  "Check: Enabled if Functions > Enabled",
  "Enforce: Disabled",
  "Enforce: Enabled",
  "Enforce: Enabled if Functions > Enabled"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Disabled",
    "Check: Enabled",
    "Check: Enabled if Functions > Enabled",
    "Enforce: Disabled",
    "Enforce: Enabled",
    "Enforce: Enabled if Functions > Enabled"
  ],
  "default": "Skip"
}

GCP > Functions > Approved Regions [Default]

A list of GCP regions in which GCP Functions resources are approved for use.

The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.

This policy is the default value for all GCP Functions resources' Approved > Regions policies.

"{\n  regions: policyValue(uri:\"tmod:@turbot/gcp#/policy/types/approvedRegionsDefault\") {\n    value\n  }\n}\n"

"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"

GCP > Functions > CMDB

Record and synchronize details for GCP Functions service into the CMDB.

[
  "Skip",
  "Enforce: Enabled"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Enforce: Enabled"
  ],
  "example": [
    "Skip"
  ],
  "default": "Enforce: Enabled"
}

GCP > Functions > Enabled

Enabled Functions.

[
  "Enabled",
  "Enabled: Metadata Only",
  "Disabled"
]

{
  "type": "string",
  "enum": [
    "Enabled",
    "Enabled: Metadata Only",
    "Disabled"
  ],
  "example": [
    "Enabled"
  ],
  "default": "Disabled"
}

GCP > Functions > Function > Active

Determine the action to take when an GCP Functions function, based on the GCP > Functions > Function > Active > * policies.

The control determines whether the resource is in active use, and if not,
has the ability to delete / cleanup the resource. When running an automated
compliance environment, it's common to end up with a wide range of alarms
that are difficult and time consuming to clear. The Active control brings
automated, well-defined control to this process.

The Active control checks the status of all defined Active policies for the
resource (GCP > Functions > Function > Active > *), raises an alarm, and takes the defined enforcement
action. Each Active sub-policy can calculate a status of active, inactive
or skipped. Generally, if the resource appears to be Active for any reason
it will be considered Active.
Note the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

See Active for more information.

[
  "Skip",
  "Check: Active",
  "Enforce: Delete inactive with 1 day warning",
  "Enforce: Delete inactive with 3 days warning",
  "Enforce: Delete inactive with 7 days warning",
  "Enforce: Delete inactive with 14 days warning",
  "Enforce: Delete inactive with 30 days warning",
  "Enforce: Delete inactive with 60 days warning",
  "Enforce: Delete inactive with 90 days warning",
  "Enforce: Delete inactive with 180 days warning",
  "Enforce: Delete inactive with 365 days warning"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Active",
    "Enforce: Delete inactive with 1 day warning",
    "Enforce: Delete inactive with 3 days warning",
    "Enforce: Delete inactive with 7 days warning",
    "Enforce: Delete inactive with 14 days warning",
    "Enforce: Delete inactive with 30 days warning",
    "Enforce: Delete inactive with 60 days warning",
    "Enforce: Delete inactive with 90 days warning",
    "Enforce: Delete inactive with 180 days warning",
    "Enforce: Delete inactive with 365 days warning"
  ],
  "example": [
    "Check: Active"
  ],
  "default": "Skip"
}

GCP > Functions > Function > Active > Age

The age after which the GCP Functions function
is no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.

The Active
control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated
compliance environment, it's common to end up with a wide range of alarms
that are difficult and time consuming to clear. The Active control brings
automated, well-defined control to this process.

The Active control checks the status of all defined Active policies for the
resource (GCP > Functions > Function > Active > *),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.
Note the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

[
  "Skip",
  "Force inactive if age > 1 day",
  "Force inactive if age > 3 days",
  "Force inactive if age > 7 days",
  "Force inactive if age > 14 days",
  "Force inactive if age > 30 days",
  "Force inactive if age > 60 days",
  "Force inactive if age > 90 days",
  "Force inactive if age > 180 days",
  "Force inactive if age > 365 days"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Force inactive if age > 1 day",
    "Force inactive if age > 3 days",
    "Force inactive if age > 7 days",
    "Force inactive if age > 14 days",
    "Force inactive if age > 30 days",
    "Force inactive if age > 60 days",
    "Force inactive if age > 90 days",
    "Force inactive if age > 180 days",
    "Force inactive if age > 365 days"
  ],
  "example": [
    "Force inactive if age > 90 days"
  ],
  "default": "Skip"
}

GCP > Functions > Function > Active > Last Modified

The number of days since the GCP Functions function was last modified before it is considered
inactive.

The Active
control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated
compliance environment, it's common to end up with a wide range of alarms
that are difficult and time consuming to clear. The Active control brings
automated, well-defined control to this process.

The Active control checks the status of all defined Active policies for the
resource (GCP > Functions > Function > Active > *), raises an alarm, and takes the defined enforcement
action. Each Active sub-policy can calculate a status of active, inactive
or skipped. Generally, if the resource appears to be Active for any reason
it will be considered Active.
Note the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

[
  "Skip",
  "Active if last modified <= 1 day",
  "Active if last modified <= 3 days",
  "Active if last modified <= 7 days",
  "Active if last modified <= 14 days",
  "Active if last modified <= 30 days",
  "Active if last modified <= 60 days",
  "Active if last modified <= 90 days",
  "Active if last modified <= 180 days",
  "Active if last modified <= 365 days",
  "Force active if last modified <= 1 day",
  "Force active if last modified <= 3 days",
  "Force active if last modified <= 7 days",
  "Force active if last modified <= 14 days",
  "Force active if last modified <= 30 days",
  "Force active if last modified <= 60 days",
  "Force active if last modified <= 90 days",
  "Force active if last modified <= 180 days",
  "Force active if last modified <= 365 days"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Active if last modified <= 1 day",
    "Active if last modified <= 3 days",
    "Active if last modified <= 7 days",
    "Active if last modified <= 14 days",
    "Active if last modified <= 30 days",
    "Active if last modified <= 60 days",
    "Active if last modified <= 90 days",
    "Active if last modified <= 180 days",
    "Active if last modified <= 365 days",
    "Force active if last modified <= 1 day",
    "Force active if last modified <= 3 days",
    "Force active if last modified <= 7 days",
    "Force active if last modified <= 14 days",
    "Force active if last modified <= 30 days",
    "Force active if last modified <= 60 days",
    "Force active if last modified <= 90 days",
    "Force active if last modified <= 180 days",
    "Force active if last modified <= 365 days"
  ],
  "example": [
    "Active if last modified <= 90 days"
  ],
  "default": "Skip"
}

GCP > Functions > Function > Approved

Determine the action to take when a GCP Functions function is not approved based on GCP > Functions > Function > Approved > * policies.

The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.

For any enforcement actions that specify if new, e.g., Enforce: Delete unapproved if new, this control will only take the enforcement actions for resources created within the last 60 minutes.

See Approved for more information.

[
  "Skip",
  "Check: Approved",
  "Enforce: Delete unapproved if new"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Approved",
    "Enforce: Delete unapproved if new"
  ],
  "example": [
    "Check: Approved"
  ],
  "default": "Skip"
}

GCP > Functions > Function > Approved > Custom

Determine whether the GCP Functions function is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Functions function is not approved, it will be subject to the action specified in the GCP > Functions > Function > Approved policy.
See Approved for more information.

Note: The policy value must be a string with a value of Approved, Not approved or Skip, or in the form of YAML objects. The object(s) must contain the key result with its value as Approved or Not approved. A custom title and message can also be added using the keys title and message respectively.

{
  "example": [
    "Approved",
    "Not approved",
    "Skip",
    {
      "result": "Approved"
    },
    {
      "title": "string",
      "result": "Not approved"
    },
    {
      "title": "string",
      "result": "Approved",
      "message": "string"
    },
    [
      {
        "title": "string",
        "result": "Approved",
        "message": "string"
      },
      {
        "title": "string",
        "result": "Not approved",
        "message": "string"
      }
    ]
  ],
  "anyOf": [
    {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string",
            "pattern": "^[\\W\\w]{1,32}$"
          },
          "message": {
            "type": "string",
            "pattern": "^[\\W\\w]{1,128}$"
          },
          "result": {
            "type": "string",
            "pattern": "^(Approved|Not approved|Skip)$"
          }
        },
        "required": [
          "result"
        ],
        "additionalProperties": false
      }
    },
    {
      "type": "object",
      "properties": {
        "title": {
          "type": "string",
          "pattern": "^[\\W\\w]{1,32}$"
        },
        "message": {
          "type": "string",
          "pattern": "^[\\W\\w]{1,128}$"
        },
        "result": {
          "type": "string",
          "pattern": "^(Approved|Not approved|Skip)$"
        }
      },
      "required": [
        "result"
      ],
      "additionalProperties": false
    },
    {
      "type": "string",
      "pattern": "^(Approved|Not approved|Skip)$"
    }
  ],
  "default": "Skip"
}

GCP > Functions > Function > Approved > Regions

A list of GCP regions in which GCP Functions functions are approved for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy will be evaluated by the Approved control. If a GCP Functions function is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Functions > Function > Approved policy.

See Approved for more information.

"{\n  regions: policyValue(uri:\"tmod:@turbot/gcp-functions#/policy/types/functionsApprovedRegionsDefault\") {\n    value\n  }\n}\n"

"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"

GCP > Functions > Function > Approved > Usage

Determine whether the GCP Functions function is allowed to exist.

This policy will be evaluated by the Approved control. If a GCP Functions function is not approved, it will be subject to the action specified in the GCP > Functions > Function > Approved policy.

See Approved for more information.

[
  "Not approved",
  "Approved",
  "Approved if GCP > Functions > Enabled"
]

{
  "type": "string",
  "enum": [
    "Not approved",
    "Approved",
    "Approved if GCP > Functions > Enabled"
  ],
  "example": [
    "Not approved"
  ],
  "default": "Approved if GCP > Functions > Enabled"
}

GCP > Functions > Function > CMDB

Configure whether to record and synchronize details for the GCP Functions function into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in GCP > Functions > Function > Regions policy, the CMDB control will delete the resource from the CMDB.

(Note: Setting CMDB to "Skip" will also pause these changes.)

[
  "Skip",
  "Enforce: Enabled",
  "Enforce: Enabled if Functions API is enabled",
  "Enforce: Disabled"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Enforce: Enabled",
    "Enforce: Enabled if Functions API is enabled",
    "Enforce: Disabled"
  ],
  "example": [
    "Skip"
  ],
  "default": "Enforce: Enabled if Functions API is enabled"
}

GCP > Functions > Function > Policy

GCP > Functions > Function > Policy > Trusted Access

Check or Enforce access checking on the GCP Functions Function policy.

Google Cloud IAM allows you to control who has access to the
functions function via an IAM Policy. The Trusted Access policy
allows you to configure whether Guardrails will evaluate or
enforce restrictions on which members are allowed to be granted
access.

If enabled, the members in the IAM policy will be evaluated
against the list of allowed members in each of the Trusted
Access sub-policies (Trusted Access > Domains,
Trusted Access > Groups, etc).

If set to "Enforce: Trusted Access > *", access to non-trusted
members will be removed.

[
  "Skip",
  "Check: Trusted Access > *",
  "Enforce: Trusted Access > *"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Trusted Access > *",
    "Enforce: Trusted Access > *"
  ],
  "default": "Skip"
}

GCP > Functions > Function > Policy > Trusted Access > All Authenticated

Determine whether public access may be granted on GCP Functions Function policy.
This policy is used by the GCP > Functions > Function > Policy > Trusted Access
control to determine whether grants to allAuthenticatedUsers is allowed.

[
  "Allow allAuthenticatedUsers (Public Access)",
  "Do not allow allAuthenticatedUsers"
]

{
  "type": "string",
  "enum": [
    "Allow allAuthenticatedUsers (Public Access)",
    "Do not allow allAuthenticatedUsers"
  ],
  "default": "Allow allAuthenticatedUsers (Public Access)"
}

GCP > Functions > Function > Policy > Trusted Access > All Users

Determine whether anonymous access may be granted on GCP Functions Function policy.
This policy is used by the GCP > Functions > Function > Policy > Trusted Access
control to determine whether grants to allUsers is allowed.

[
  "Allow allUsers (Anonymous Access)",
  "Do not allow allUsers"
]

{
  "type": "string",
  "enum": [
    "Allow allUsers (Anonymous Access)",
    "Do not allow allUsers"
  ],
  "default": "Allow allUsers (Anonymous Access)"
}

GCP > Functions > Function > Policy > Trusted Access > Domains

List of GCP Domains that are trusted for access in the GCP Functions Function policy.

This policy is used by the GCP > Functions > Function > Policy > Trusted Access
control to determine which members of type "domain" are allowed
to be granted access.You may use the '*' and '?' wildcard characters.

<br />example:<br /> - company.com<br /> - company-dev.org<br />

Note: Setting the policy to Empty array will remove all domains.

"{\n  value: policy(uri: \"tmod:@turbot/gcp-functions#/policy/types/functionsTrustedDomains\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Functions > Function > Policy > Trusted Access > Groups

List of GCP Groups that are trusted for access in the GCP Functions Function policy.

This policy is used by the GCP > Functions > Function > Policy > Trusted Access
control to determine which members of type "group" are allowed
to be granted access.You may use the '' and '?' wildcard characters.

```
example:
- notification@company.com
- "@company.com"
``<br /><br />**Note**: Setting the policy to an Empty` array will remove all groups.

"{\n  value: policy(uri: \"tmod:@turbot/gcp-functions#/policy/types/functionsTrustedGroups\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Functions > Function > Policy > Trusted Access > Service Accounts

List of GCP Service Accounts that are trusted for access in the GCP Functions Function policy.

This policy is used by the GCP > Functions > Function > Policy > Trusted Access
control to determine which members of type "serviceAccount" are allowed
to be granted access.You may use the '' and '?' wildcard characters.

```
example:
- project-owner@dev-aaa.iam.gserviceaccount.com
- "" # All service account trusted
``<br /><br />**Note**: Setting the policy to an Empty` array will remove all service accounts.

"{\n  value: policy(uri: \"tmod:@turbot/gcp-functions#/policy/types/functionsTrustedServiceAccounts\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Functions > Function > Policy > Trusted Access > Users

List of GCP Users that are trusted for access in the GCP Functions Function policy.

This policy is used by the GCP > Functions > Function > Trusted Access
control to determine which members of type "user" are allowed
to be granted access.You may use the '' and '?' wildcard characters.

```
example:
- "@company.com" # All users with email ending in @company.com are trusted
- "test@dev-company.com"
- "dummy@gmail.com"
``<br /><br />**Note**: Setting the policy to an Empty` array will remove all users.

"{\n  value: policy(uri: \"tmod:@turbot/gcp-functions#/policy/types/functionsTrustedUsers\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Functions > Function > Regions

A list of GCP regions in which GCP Functions functions are supported for use.

Any functions in a region not listed here will not be recorded in CMDB.

The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.

{
  "allOf": [
    {
      "$ref": "gcp#/definitions/regionNameMatcherList"
    },
    {
      "default": [
        "asia-east1",
        "asia-east2",
        "asia-northeast1",
        "asia-northeast2",
        "asia-northeast3",
        "asia-south1",
        "asia-south2",
        "asia-southeast1",
        "asia-southeast2",
        "australia-southeast1",
        "australia-southeast2",
        "europe-central2",
        "europe-north1",
        "europe-west1",
        "europe-west2",
        "europe-west3",
        "europe-west4",
        "europe-west6",
        "northamerica-northeast1",
        "northamerica-northeast2",
        "southamerica-east1",
        "southamerica-west1",
        "us-central1",
        "us-east1",
        "us-east4",
        "us-west1",
        "us-west2",
        "us-west3",
        "us-west4"
      ]
    }
  ]
}

GCP > Functions > Function > Usage

Configure the number of GCP Functions functions that can be used for this region and the current consumption against the limit.

You can configure the behavior of the control with this GCP > Functions > Function > Usage policy.

[
  "Skip",
  "Check: Usage <= 85% of Limit",
  "Check: Usage <= 100% of Limit"
]

{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Usage <= 85% of Limit",
    "Check: Usage <= 100% of Limit"
  ],
  "example": [
    "Check: Usage <= 85% of Limit"
  ],
  "default": "Skip"
}

GCP > Functions > Function > Usage > Limit

Maximum number of items that can be created for this region

{
  "type": "integer",
  "minimum": 0,
  "default": 1000
}

GCP > Functions > Permissions

Configure whether permissions policies are in effect for GCP Functions.
This setting does not affect Project level permissions (GCP/Admin, GCP/Owner, etc).

Note: The behavior of this policy depends on the value of GCP > Permissions.

[
  "Enabled",
  "Disabled",
  "Enabled if GCP > Functions > Enabled"
]

{
  "type": "string",
  "enum": [
    "Enabled",
    "Disabled",
    "Enabled if GCP > Functions > Enabled"
  ],
  "example": [
    "Enabled"
  ],
  "default": "Enabled if GCP > Functions > Enabled"
}

GCP > Functions > Permissions > Levels

Define the permissions levels that can be used to grant access to Functions
an GCP project. Permissions levels defined will appear in the UI to assign access to Guardrails users.

Note: Some services do not use all permissions levels, and any permissions level that has
no permissions associated will not be created even if it is selected here.

[
  "{\n  item: project {\n    turbot{\n      id\n    }\n  }\n}\n",
  "{\n  availableLevels: policyValues(filter:\"policyTypeLevel:self resourceId:{{ $.item.turbot.id }} policyTypeId:'tmod:@turbot/gcp-iam#/policy/types/permissionsLevelsDefault'\") {\n    items {\n      value\n    }\n  }\n}\n"
]

"{% if $.availableLevels.items[0].value | length == 0 %} [] {% endif %}{% for item in $.availableLevels.items[0].value %}- {{ item }}\n{% endfor %}"

{
  "type": "array",
  "items": {
    "type": "string",
    "enum": [
      "Metadata",
      "ReadOnly",
      "Operator",
      "Admin",
      "Owner"
    ]
  }
}

GCP > Functions > Permissions > Levels > Modifiers

A map of GCP API to Guardrails Permission Level used to customize Guardrails' standard permissions.
You can add, remove or redefine the mapping of GCP API operations to Guardrails permissions levels here.

Note: Modifiers are cumulative - if you add a permission to the metadata level, it is also added
to readOnly, operator and admin. Modifier policies set here will “roll up” to the GCP level too - if
you add a permission to Admin, it will be granted to GCP/Storage/Admin and also GCP/Admin

<br />example:<br /> - &quot;storage.bucket.create&quot;: admin<br /> - &quot;sql.database.create&quot;: metadata<br />

GCP > Functions > Regions

A list of GCP regions in which GCP Functions resources are supported for use.

The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.

This policy is the default value for all GCP Functions resources' Regions policies.

{
  "allOf": [
    {
      "$ref": "gcp#/definitions/regionNameMatcherList"
    },
    {
      "default": [
        "asia-east1",
        "asia-east2",
        "asia-northeast1",
        "asia-northeast2",
        "asia-northeast3",
        "asia-south1",
        "asia-south2",
        "asia-southeast1",
        "asia-southeast2",
        "australia-southeast1",
        "australia-southeast2",
        "europe-central2",
        "europe-north1",
        "europe-west1",
        "europe-west2",
        "europe-west3",
        "europe-west4",
        "europe-west6",
        "northamerica-northeast1",
        "northamerica-northeast2",
        "southamerica-east1",
        "southamerica-west1",
        "us-central1",
        "us-east1",
        "us-east4",
        "us-west1",
        "us-west2",
        "us-west3",
        "us-west4"
      ]
    }
  ]
}

GCP > Functions > Trusted Domains [Default]

List of GCP Domains that are trusted for access in the GCP Functions policy.

This policy is used by the GCP > Functions > Policy > Trusted Access
control to determine which members of type "domain" are allowed
to be granted access.You may use the '*' and '?' wildcard characters.

<br />example:<br /> - company.com<br /> - company-dev.org<br />

Note: Setting the policy to Empty array will remove all domains.

"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedDomains\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Functions > Trusted Groups [Default]

List of GCP Groups that are trusted for access in the GCP Functions policy.

This policy is used by the GCP > Functions > Policy > Trusted Access
control to determine which members of type "group" are allowed
to be granted access.You may use the '' and '?' wildcard characters.

```
example:
- notification@company.com
- "@company.com"
``<br /><br />**Note**: Setting the policy to an Empty` array will remove all groups.

"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedGroups\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Functions > Trusted Service Accounts [Default]

List of GCP Service Accounts that are trusted for access in the GCP Functions policy.

This policy is used by the GCP > Functions > Policy > Trusted Access
control to determine which members of type "serviceAccount" are allowed
to be granted access.You may use the '' and '?' wildcard characters.

```
example:
- project-owner@dev-aaa.iam.gserviceaccount.com
- "" # All service account trusted
``<br /><br />**Note**: Setting the policy to an Empty` array will remove all service accounts.

"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedServiceAccounts\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Functions > Trusted Users [Default]

List of GCP Users that are trusted for access in the GCP Functions policy.

This policy is used by the GCP > Functions > Trusted Access
control to determine which members of type "user" are allowed
to be granted access.You may use the '' and '?' wildcard characters.

```
example:
- "@company.com" # All users with email ending in @company.com are trusted
- "test@dev-company.com"
- "dummy@gmail.com"
``<br /><br />**Note**: Setting the policy to an Empty` array will remove all users.

"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedUsers\")\n}\n"

"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"

{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-functions

A GCP logs advanced filter
used to specify a subset of log entries that will be forwarded by the
logging sink on behalf of the gcp-functions mod

This is a read-only policy that is used internally by Guardrails

{
  "type": "string",
  "default": "(resource.type = cloud_function AND (protoPayload.authorizationInfo.permission != cloudfunctions.functions.get OR protoPayload.authorizationInfo.permission != cloudfunctions.functions.list OR protoPayload.authorizationInfo.permission != cloudfunctions.functions.sourceCodeGet) AND severity>=INFO AND severity<ERROR)"
}

GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-functions

A calculated policy that Guardrails uses to create a compiled list of ALL permission
levels for GCP Functions that is used as input to
the stack that manages the Guardrails IAM permissions objects.

GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-functions

A calculated policy that Guardrails uses to create a compiled list of ALL
permissions for GCP Functions that is used as
input to the control that manages the IAM stack.