Product logo
DocsBlogPricing

Policy types for @turbot/gcp-secretmanager

GCP > Secret Manager > API Enabled

Check whether GCP Secret Manager 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 > Secret Manager > API Enabled control compares the API state against the API Enabled policies, raises an alarm, and takes the defined enforcement action.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerApiEnabled
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: Disabled",
  "Check: Enabled",
  "Check: Enabled if Secret Manager > Enabled",
  "Enforce: Disabled",
  "Enforce: Enabled",
  "Enforce: Enabled if Secret Manager > Enabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Disabled",
    "Check: Enabled",
    "Check: Enabled if Secret Manager > Enabled",
    "Enforce: Disabled",
    "Enforce: Enabled",
    "Enforce: Enabled if Secret Manager > Enabled"
  ],
  "default": "Skip"
}

GCP > Secret Manager > CMDB

Configure whether to record and synchronize details for the GCP Secret Manager into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB. All policies and controls in Turbot 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".

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerCmdb
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Enforce: Enabled",
  "Enforce: Disabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Enforce: Enabled",
    "Enforce: Disabled"
  ],
  "example": [
    "Skip"
  ],
  "default": "Enforce: Enabled"
}

GCP > Secret Manager > Enabled

Enabled Secret Manager.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerEnabled
Category
Parent
Targets
Valid Value
[
  "Enabled",
  "Enabled: Metadata Only",
  "Disabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Enabled",
    "Enabled: Metadata Only",
    "Disabled"
  ],
  "example": [
    "Enabled"
  ],
  "default": "Disabled"
}

GCP > Secret Manager > Labels Template [Default]

A template used to generate the keys and values for GCP Secret Manager resources.

By default, all Secret Manager resource Labels > Template policies will use this value.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerLabelsTemplate
Category
Parent
Targets
Default Template Input
"{\n  defaultLabels: policyValue(uri:\"tmod:@turbot/gcp#/policy/types/defaultLabelsTemplate\") {\n    value\n  }\n}\n"
Default Template
"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"
Schema

GCP > Secret Manager > Permissions

Configure whether permissions policies are in effect for GCP Secret Manager. 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerPermissions
Category
Parent
Targets
Valid Value
[
  "Enabled",
  "Disabled",
  "Enabled if GCP > Secret Manager > Enabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Enabled",
    "Disabled",
    "Enabled if GCP > Secret Manager > Enabled"
  ],
  "example": [
    "Enabled"
  ],
  "default": "Enabled if GCP > Secret Manager > Enabled"
}

GCP > Secret Manager > Permissions > Levels

Define the permissions levels that can be used to grant access to Secret Manager an GCP project. Permissions levels defined will appear in the UI to assign access to Turbot 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerPermissionsLevels
Category
Parent
Targets
Default Template Input
[
  "{\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"
]
Default Template
"{% if $.availableLevels.items[0].value | length == 0 %} [] {% endif %}{% for item in $.availableLevels.items[0].value %}- {{ item }}\n{% endfor %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string",
    "enum": [
      "Metadata",
      "ReadOnly",
      "Operator",
      "Admin",
      "Owner"
    ]
  }
}

GCP > Secret Manager > Permissions > Levels > Modifiers

A map of GCP API to Turbot Permission Level used to customize Turbot's standard permissions. You can add, remove or redefine the mapping of GCP API operations to Turbot 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

example:
  - "storage.bucket.create": admin
  - "sql.database.create": metadata
URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerPermissionsLevelsModifiers
Category
Parent
Targets
Schema

GCP > Secret Manager > Secret > Active

Determine the action to take when an GCP Secret Manager secret, based on the GCP > Secret Manager > Secret > 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 > Secret Manager > Secret > 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretActive
Category
Parent
Targets
Valid Value
[
  "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"
]
Schema
{
  "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 > Secret Manager > Secret > Active > Age

The age after which the GCP Secret Manager secret is no longer considered active. If a create time is unavailable, the time Turbot 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 > Secret Manager > Secret > 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretActiveAge
Category
Parent
Targets
Valid Value
[
  "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"
]
Schema
{
  "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 > Secret Manager > Secret > Active > Last Modified

The number of days since the GCP Secret Manager secret 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 > Secret Manager > Secret > 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretActiveLastModified
Category
Parent
Targets
Valid Value
[
  "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"
]
Schema
{
  "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 > Secret Manager > Secret > Approved

Determine the action to take when a GCP Secret Manager secret is not approved based on GCP > Secret Manager > Secret > 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretApproved
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: Approved",
  "Enforce: Delete unapproved if new"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Approved",
    "Enforce: Delete unapproved if new"
  ],
  "example": [
    "Check: Approved"
  ],
  "default": "Skip"
}

GCP > Secret Manager > Secret > Approved > Custom

Determine whether the GCP Secret Manager secret is allowed to exist. This policy will be evaluated by the Approved control. If a GCP Secret Manager secret is not approved, it will be subject to the action specified in the GCP > Secret Manager > Secret > 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretApprovedCustom
Category
Parent
Targets
Schema
{
  "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 > Secret Manager > Secret > Approved > Usage

Determine whether the GCP Secret Manager secret is allowed to exist.

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

See Approved for more information.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretApprovedUsage
Category
Parent
Targets
Valid Value
[
  "Not approved",
  "Approved",
  "Approved if GCP > Secret Manager > Enabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Not approved",
    "Approved",
    "Approved if GCP > Secret Manager > Enabled"
  ],
  "example": [
    "Not approved"
  ],
  "default": "Approved if GCP > Secret Manager > Enabled"
}

GCP > Secret Manager > Secret > CMDB

Configure whether to record and synchronize details for the GCP Secret Manager secret into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB. All policies and controls in Turbot 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".

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretCmdb
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Enforce: Enabled",
  "Enforce: Enabled if Secrets Manager API is enabled",
  "Enforce: Disabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Enforce: Enabled",
    "Enforce: Enabled if Secrets Manager API is enabled",
    "Enforce: Disabled"
  ],
  "example": [
    "Skip"
  ],
  "default": "Enforce: Enabled if Secrets Manager API is enabled"
}

GCP > Secret Manager > Secret > Labels

Determine the action to take when an GCP Secret Manager secret labels are not updated based on the GCP > Secret Manager > Secret > Labels > * policies.

The control ensure GCP Secret Manager secret labels include labels defined in GCP > Secret Manager > Secret > Labels > Template.

Labels not defined in Secret Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretLabels
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: Labels are correct",
  "Enforce: Set labels"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Labels are correct",
    "Enforce: Set labels"
  ],
  "example": [
    "Check: Labels are correct"
  ],
  "default": "Skip"
}

GCP > Secret Manager > Secret > Labels > Template

The template is used to generate the keys and values for GCP Secret Manager secret.

Labels not defined in Secret Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretLabelsTemplate
Category
Parent
Targets
Default Template Input
[
  "{\n  project {\n    turbot {\n      id\n    }\n  }\n}\n",
  "{\n  defaultLabels: policyValue(uri:\"tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerLabelsTemplate\" resourceId: \"{{ $.project.turbot.id }}\") {\n    value\n  }\n}\n"
]
Default Template
"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"
Schema

GCP > Secret Manager > Secret > Policy

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretPolicy
Category
Parent
Targets

GCP > Secret Manager > Secret > Policy > Trusted Access

Check or Enforce access checking on the GCP Secret Manager Secret policy.

Google Cloud IAM allows you to control who has access to the secret manager secret via an IAM Policy. The Trusted Access policy allows you to configure whether Turbot 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.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretPolicyTrustedAccess
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: Trusted Access > *",
  "Enforce: Trusted Access > *"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Trusted Access > *",
    "Enforce: Trusted Access > *"
  ],
  "default": "Skip"
}

GCP > Secret Manager > Secret > Policy > Trusted Access > Domains

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

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

example:
  - company.com
  - company-dev.org

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretPolicyTrustedDomains
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedDomains\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Secret Manager > Secret > Policy > Trusted Access > Groups

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

This policy is used by the GCP > Secret Manager > Secret > 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
  - &quot;*@company.com&quot;

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretPolicyTrustedGroups
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedGroups\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Secret Manager > Secret > Policy > Trusted Access > Service Accounts

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

This policy is used by the GCP > Secret Manager > Secret > 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
  - &quot;*&quot; # All service account trusted

Note: Setting the policy to an Empty array will remove all service accounts.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretPolicyTrustedServiceAccounts
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedServiceAccounts\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Secret Manager > Secret > Policy > Trusted Access > Users

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

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

example:
  - &quot;*@company.com&quot; # All users with email ending in @company.com are trusted
  - &quot;test@dev-company.com&quot;
  - &quot;dummy@gmail.com&quot;

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretPolicyTrustedUsers
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedUsers\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Secret Manager > Trusted Domains [Default]

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

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

example:
  - company.com
  - company-dev.org

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedDomains
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedDomains\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Secret Manager > Trusted Groups [Default]

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

This policy is used by the GCP > Secret Manager > 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
  - &quot;*@company.com&quot;

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedGroups
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedGroups\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Secret Manager > Trusted Service Accounts [Default]

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

This policy is used by the GCP > Secret Manager > 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
  - &quot;*&quot; # All service account trusted

Note: Setting the policy to an Empty array will remove all service accounts.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedServiceAccounts
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedServiceAccounts\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

GCP > Secret Manager > Trusted Users [Default]

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

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

example:
  - &quot;*@company.com&quot; # All users with email ending in @company.com are trusted
  - &quot;test@dev-company.com&quot;
  - &quot;dummy@gmail.com&quot;

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerTrustedUsers
Category
Parent
Targets
Default Template Input
"{\n  value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedUsers\")\n}\n"
Default Template
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- &#39;{{ item }}&#39;\n{% endfor %}{% endif %}"
Schema
{
  "type": "array",
  "items": {
    "type": "string"
  }
}

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

GCP logs advanced filter used to specify a subset of log entries that is forwarded to the Turbot Event Handlers by the logging sink on behalf of GCP Secret Manager.

URI
tmod:@turbot/gcp-secretmanager#/policy/types/secretManagerCustomEventPatterns
Category
Parent
Targets
Schema
{
  "type": "string",
  "default": "(resource.type = audited_resource AND (protoPayload.authorizationInfo.permission=secretmanager.secrets.create OR protoPayload.authorizationInfo.permission=secretmanager.secrets.update OR protoPayload.authorizationInfo.permission=secretmanager.secrets.delete OR protoPayload.authorizationInfo.permission=secretmanager.secrets.setIamPolicy) AND severity>=INFO AND severity<ERROR)"
}

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

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/gcpLevelsCompiled
Category
Parent
Targets
Schema

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

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

URI
tmod:@turbot/gcp-secretmanager#/policy/types/gcpCompiledServicePermissions
Category
Parent
Targets
Schema