Policy types for @turbot/gcp-storage
- GCP > Storage > API Enabled
- GCP > Storage > Approved Regions [Default]
- GCP > Storage > Bucket > Access Control
- GCP > Storage > Bucket > Active
- GCP > Storage > Bucket > Active > Age
- GCP > Storage > Bucket > Active > Last Modified
- GCP > Storage > Bucket > Approved
- GCP > Storage > Bucket > Approved > Custom
- GCP > Storage > Bucket > Approved > Regions
- GCP > Storage > Bucket > Approved > Usage
- GCP > Storage > Bucket > CMDB
- GCP > Storage > Bucket > Encryption at Rest
- GCP > Storage > Bucket > Encryption at Rest > Customer Managed Key
- GCP > Storage > Bucket > Labels
- GCP > Storage > Bucket > Labels > Template
- GCP > Storage > Bucket > Policy
- GCP > Storage > Bucket > Policy > Trusted Access
- GCP > Storage > Bucket > Policy > Trusted Access > All Authenticated
- GCP > Storage > Bucket > Policy > Trusted Access > All Users
- GCP > Storage > Bucket > Policy > Trusted Access > Domains
- GCP > Storage > Bucket > Policy > Trusted Access > Groups
- GCP > Storage > Bucket > Policy > Trusted Access > Projects
- GCP > Storage > Bucket > Policy > Trusted Access > Service Accounts
- GCP > Storage > Bucket > Policy > Trusted Access > Users
- GCP > Storage > Bucket > Regions
- GCP > Storage > Bucket > Usage
- GCP > Storage > Bucket > Usage > Limit
- GCP > Storage > Bucket > Versioning
- GCP > Storage > CMDB
- GCP > Storage > Enabled
- GCP > Storage > Labels Template [Default]
- GCP > Storage > Object > Active
- GCP > Storage > Object > Active > Age
- GCP > Storage > Object > Active > Last Modified
- GCP > Storage > Object > Approved
- GCP > Storage > Object > Approved > Custom
- GCP > Storage > Object > Approved > Regions
- GCP > Storage > Object > Approved > Usage
- GCP > Storage > Object > CMDB
- GCP > Storage > Object > Regions
- GCP > Storage > Permissions
- GCP > Storage > Permissions > Levels
- GCP > Storage > Permissions > Levels > Modifiers
- GCP > Storage > Regions
- GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-storage
- GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-storage
- GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-storage
GCP > Storage > API Enabled
Check whether GCP Storage 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 > Storage > API Enabled
control compares
the API state against the API Enabled policies,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/gcp-storage#/policy/types/storageApiEnabled
[ "Skip", "Check: Disabled", "Check: Enabled", "Check: Enabled if Storage > Enabled", "Enforce: Disabled", "Enforce: Enabled", "Enforce: Enabled if Storage > Enabled"]
{ "type": "string", "enum": [ "Skip", "Check: Disabled", "Check: Enabled", "Check: Enabled if Storage > Enabled", "Enforce: Disabled", "Enforce: Enabled", "Enforce: Enabled if Storage > Enabled" ], "default": "Skip"}
GCP > Storage > Approved Regions [Default]
A list of GCP regions in which GCP Storage 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 Storage resources' Approved > Regions policies.
tmod:@turbot/gcp-storage#/policy/types/storageApprovedRegionsDefault
"{\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 > Storage > Bucket > Access Control
Define the Access Level settings required for GCP > Storage > Bucket
.
The Access control determines whether the access level for GCP Storage Bucket should be set to Uniform or Fine-grained.
Enabling uniform bucket-level access on a bucket, Access Control Lists (ACLs) are disabled, and only bucket-level Identity and Access Management (IAM) permissions grant access to that bucket and the objects it contains
tmod:@turbot/gcp-storage#/policy/types/bucketAccessControl
[ "Skip", "Check: Fine-grained", "Check: Uniform", "Enforce: Fine-grained", "Enforce: Uniform"]
{ "type": "string", "enum": [ "Skip", "Check: Fine-grained", "Check: Uniform", "Enforce: Fine-grained", "Enforce: Uniform" ], "example": [ "Check: Uniform" ], "default": "Skip"}
GCP > Storage > Bucket > Active
Determine the action to take when an GCP Storage bucket, based on the GCP > Storage > Bucket > 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 > Storage > Bucket > 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.
tmod:@turbot/gcp-storage#/policy/types/bucketActive
[ "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 > Storage > Bucket > Active > Age
The age after which the GCP Storage bucket
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 > Storage > Bucket > 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.
tmod:@turbot/gcp-storage#/policy/types/bucketActiveAge
[ "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 > Storage > Bucket > Active > Last Modified
The number of days since the GCP Storage bucket 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 > Storage > Bucket > 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.
tmod:@turbot/gcp-storage#/policy/types/bucketActiveLastModified
[ "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 > Storage > Bucket > Approved
Determine the action to take when a GCP Storage bucket is not approved based on GCP > Storage > Bucket > 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.
tmod:@turbot/gcp-storage#/policy/types/bucketApproved
[ "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 > Storage > Bucket > Approved > Custom
Determine whether the GCP Storage bucket is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Storage bucket is not approved, it will be subject to the action specified in the GCP > Storage > Bucket > 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.
tmod:@turbot/gcp-storage#/policy/types/bucketApprovedCustom
{ "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 > Storage > Bucket > Approved > Regions
A list of GCP regions in which GCP Storage buckets 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 Storage bucket is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Storage > Bucket > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-storage#/policy/types/bucketApprovedRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-storage#/policy/types/storageApprovedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
GCP > Storage > Bucket > Approved > Usage
Determine whether the GCP Storage bucket is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Storage bucket is not approved, it will be subject to the action specified in the GCP > Storage > Bucket > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-storage#/policy/types/bucketApprovedUsage
[ "Not approved", "Approved", "Approved if GCP > Storage > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if GCP > Storage > Enabled" ], "example": [ "Not approved" ], "default": "Approved if GCP > Storage > Enabled"}
GCP > Storage > Bucket > CMDB
Configure whether to record and synchronize details for the GCP Storage bucket 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 > Storage > Bucket > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/gcp-storage#/policy/types/bucketCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if Storage API is enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if Storage API is enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if Storage API is enabled"}
GCP > Storage > Bucket > Encryption at Rest
Define the minimum level of encryption required for GCP Storage bucket.
tmod:@turbot/gcp-storage#/policy/types/bucketEncryptionAtRest
[ "Skip", "Check: Google managed key", "Check: Google managed key or higher", "Check: Customer managed key", "Check: Encryption at Rest > Customer Managed Key", "Enforce: Google managed key", "Enforce: Google managed key or higher", "Enforce: Customer managed key", "Enforce: Encryption at Rest > Customer Managed Key"]
{ "type": "string", "enum": [ "Skip", "Check: Google managed key", "Check: Google managed key or higher", "Check: Customer managed key", "Check: Encryption at Rest > Customer Managed Key", "Enforce: Google managed key", "Enforce: Google managed key or higher", "Enforce: Customer managed key", "Enforce: Encryption at Rest > Customer Managed Key" ], "example": [ "Check: Google managed key or higher" ], "default": "Skip"}
GCP > Storage > Bucket > Encryption at Rest > Customer Managed Key
This template is used to generate the Google Cloud KMS symmetric key to use for bucket encryption at rest.
tmod:@turbot/gcp-storage#/policy/types/bucketEncryptionAtRestCustomerManagedKey
{ "type": "string", "example": "projects/cse-legolas/locations/global/keyRings/test/cryptoKeys/disk/cryptoKeyVersions/1", "default": ""}
GCP > Storage > Bucket > Labels
Determine the action to take when an GCP Storage bucket labels are not updated based on the GCP > Storage > Bucket > Labels > *
policies.
The control ensure GCP Storage bucket labels include labels defined in GCP > Storage > Bucket > Labels > Template
.
Labels not defined in Bucket 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.
tmod:@turbot/gcp-storage#/policy/types/bucketLabels
[ "Skip", "Check: Labels are correct", "Enforce: Set labels"]
{ "type": "string", "enum": [ "Skip", "Check: Labels are correct", "Enforce: Set labels" ], "example": [ "Check: Labels are correct" ], "default": "Skip"}
GCP > Storage > Bucket > Labels > Template
The template is used to generate the keys and values for GCP Storage bucket.
Labels not defined in Bucket 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.
tmod:@turbot/gcp-storage#/policy/types/bucketLabelsTemplate
[ "{\n project {\n turbot {\n id\n }\n }\n}\n", "{\n defaultLabels: policyValue(uri:\"tmod:@turbot/gcp-storage#/policy/types/storageLabelsTemplate\" resourceId: \"{{ $.project.turbot.id }}\") {\n value\n }\n}\n"]
"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"
GCP > Storage > Bucket > Policy
tmod:@turbot/gcp-storage#/policy/types/bucketPolicy
GCP > Storage > Bucket > Policy > Trusted Access
Check or Enforce access checking on the GCP Storage Bucket
Policy.
Google Cloud IAM allows you to control who has access to the
storage bucket 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.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedAccess
[ "Skip", "Check: Trusted Access > *", "Enforce: Trusted Access > *"]
{ "type": "string", "enum": [ "Skip", "Check: Trusted Access > *", "Enforce: Trusted Access > *" ], "default": "Skip"}
GCP > Storage > Bucket > Policy > Trusted Access > All Authenticated
Determine whether public access may be granted on GCP Storage Bucket.
This policy is used by the GCP > Storage > Bucket > Policy > Trusted Access
control to determine whether grants to allAuthenticatedUsers
is allowed.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedAllAuthenticated
[ "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 > Storage > Bucket > Policy > Trusted Access > All Users
Determine whether anonymous access may be granted on GCP Storage Bucket.
This policy is used by the GCP > Storage > Bucket > Policy > Trusted Access
control to determine whether grants to allUsers
is allowed.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedAllUsers
[ "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 > Storage > Bucket > Policy > Trusted Access > Domains
List of GCP Domains that are trusted for access in the GCP Storage Bucket Policy.
This policy is used by the GCP > Storage > Bucket > 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 an Empty
array will remove all domains.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedDomains
"{\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 > Storage > Bucket > Policy > Trusted Access > Groups
List of GCP Groups that are trusted for access in the GCP Storage Bucket Policy.
This policy is used by the GCP > Storage > Bucket > 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.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedGroups
"{\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 > Storage > Bucket > Policy > Trusted Access > Projects
List of GCP Projects that are trusted for access in the GCP Storage Bucket Policy.
This policy is used by the GCP > Storage > Bucket > Policy > Trusted Access
control to determine whether members of type "project" are allowed
to be granted access.You may use the '*' and '?' wildcard characters.<br />example:<br /> - dev-aaa<br /> - dev-aab<br />
Note: Setting the policy to an Empty
array will remove all projects.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedProjects
"{\n value: policy(uri: \"tmod:@turbot/gcp#/policy/types/trustedProjects\")\n}\n"
"{% if $.value | length == 0 %}[]{% else %}{% for item in $.value %}- '{{ item }}'\n{% endfor %}{% endif %}"
{ "type": "array", "items": { "type": "string" }}
GCP > Storage > Bucket > Policy > Trusted Access > Service Accounts
List of GCP Service Accounts that are trusted for access in the GCP Storage
Bucket Policy.
This policy is used by the GCP > Storage > Bucket > 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 />**Note**: Setting the policy to an
Empty` array will remove all service accounts.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedServiceAccounts
"{\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 > Storage > Bucket > Policy > Trusted Access > Users
List of GCP Users that are trusted for access in the GCP Storage Bucket Policy.
This policy is used by the GCP > Storage > Bucket > Policy > Trusted Access
control to determine whether which 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.
tmod:@turbot/gcp-storage#/policy/types/bucketPolicyTrustedUsers
"{\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 > Storage > Bucket > Regions
A list of GCP regions in which GCP Storage buckets are supported for use.
Any buckets 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.
tmod:@turbot/gcp-storage#/policy/types/bucketRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-storage#/policy/types/storageRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
GCP > Storage > Bucket > Usage
Configure the number of GCP Storage buckets 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 > Storage > Bucket > Usage
policy.
tmod:@turbot/gcp-storage#/policy/types/bucketUsage
[ "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 > Storage > Bucket > Usage > Limit
Maximum number of items that can be created for this region
tmod:@turbot/gcp-storage#/policy/types/bucketUsageLimit
{ "type": "integer", "minimum": 0, "default": 100}
GCP > Storage > Bucket > Versioning
Configure whether Versioning is enabled for a Storage bucket.
tmod:@turbot/gcp-storage#/policy/types/bucketVersioning
[ "Skip", "Check: Disabled", "Check: Enabled", "Enforce: Disabled", "Enforce: Enabled"]
{ "type": "string", "enum": [ "Skip", "Check: Disabled", "Check: Enabled", "Enforce: Disabled", "Enforce: Enabled" ], "example": [ "Skip" ], "default": "Skip"}
GCP > Storage > CMDB
Configure whether to record and synchronize details for the GCP Storage storage 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 > Storage > Storage > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/gcp-storage#/policy/types/storageCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
GCP > Storage > Enabled
Enabled Storage.
tmod:@turbot/gcp-storage#/policy/types/storageEnabled
[ "Enabled", "Enabled: Metadata Only", "Disabled"]
{ "type": "string", "enum": [ "Enabled", "Enabled: Metadata Only", "Disabled" ], "example": [ "Enabled" ], "default": "Disabled"}
GCP > Storage > Labels Template [Default]
A template used to generate the keys and values for GCP Storage resources.
By default, all Storage resource Labels > Template policies will use this value.
tmod:@turbot/gcp-storage#/policy/types/storageLabelsTemplate
"{\n defaultLabels: policyValue(uri:\"tmod:@turbot/gcp#/policy/types/defaultLabelsTemplate\") {\n value\n }\n}\n"
"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"
GCP > Storage > Object > Active
Determine the action to take when an GCP Storage object, based on the GCP > Storage > Object > 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 > Storage > Object > 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.
tmod:@turbot/gcp-storage#/policy/types/objectActive
[ "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 > Storage > Object > Active > Age
The age after which the GCP Storage object
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 > Storage > Object > 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.
tmod:@turbot/gcp-storage#/policy/types/objectActiveAge
[ "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 > Storage > Object > Active > Last Modified
The number of days since the GCP Storage object 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 > Storage > Object > 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.
tmod:@turbot/gcp-storage#/policy/types/objectActiveLastModified
[ "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 > Storage > Object > Approved
Determine the action to take when a GCP Storage object is not approved based on GCP > Storage > Object > 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.
tmod:@turbot/gcp-storage#/policy/types/objectApproved
[ "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 > Storage > Object > Approved > Custom
Determine whether the GCP Storage object is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Storage object is not approved, it will be subject to the action specified in the GCP > Storage > Object > 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.
tmod:@turbot/gcp-storage#/policy/types/objectApprovedCustom
{ "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 > Storage > Object > Approved > Regions
A list of GCP regions in which GCP Storage objects 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 Storage object is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Storage > Object > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-storage#/policy/types/objectApprovedRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-storage#/policy/types/storageApprovedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
GCP > Storage > Object > Approved > Usage
Determine whether the GCP Storage object is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Storage object is not approved, it will be subject to the action specified in the GCP > Storage > Object > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-storage#/policy/types/objectApprovedUsage
[ "Not approved", "Approved", "Approved if GCP > Storage > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if GCP > Storage > Enabled" ], "example": [ "Not approved" ], "default": "Approved if GCP > Storage > Enabled"}
GCP > Storage > Object > CMDB
Configure whether to record and synchronize details for the GCP Storage object 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 > Storage > Object > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/gcp-storage#/policy/types/objectCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if Storage API is enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if Storage API is enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Skip"}
GCP > Storage > Object > Regions
A list of GCP regions in which GCP Storage objects are supported for use.
Any objects 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.
tmod:@turbot/gcp-storage#/policy/types/objectRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-storage#/policy/types/storageRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
GCP > Storage > Permissions
Configure whether permissions policies are in effect for GCP Storage.
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.
tmod:@turbot/gcp-storage#/policy/types/storagePermissions
[ "Enabled", "Disabled", "Enabled if GCP > Storage > Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if GCP > Storage > Enabled" ], "example": [ "Enabled" ], "default": "Enabled if GCP > Storage > Enabled"}
GCP > Storage > Permissions > Levels
Define the permissions levels that can be used to grant access to Storage
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.
tmod:@turbot/gcp-storage#/policy/types/storagePermissionsLevels
[ "{\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 > Storage > 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 /> - "storage.bucket.create": admin<br /> - "sql.database.create": metadata<br />
tmod:@turbot/gcp-storage#/policy/types/storagePermissionsLevelsModifiers
GCP > Storage > Regions
A list of GCP regions in which GCP Storage 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 Storage resources' Regions policies.
tmod:@turbot/gcp-storage#/policy/types/storageRegionsDefault
{ "allOf": [ { "$ref": "gcp#/definitions/regionNameMatcherList" }, { "default": [ "asia", "asia-east1", "asia-east2", "asia-northeast1", "asia-northeast2", "asia-south1", "asia-southeast1", "australia-southeast1", "eu", "eur4", "europe-north1", "europe-west1", "europe-west2", "europe-west3", "europe-west4", "europe-west6", "nam4", "northamerica-northeast1", "southamerica-east1", "us", "us-central1", "us-east1", "us-east4", "us-west1", "us-west2" ] } ]}
GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-storage
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-storage mod
This is a read-only policy that is used internally by Turbot
tmod:@turbot/gcp-storage#/policy/types/storageEventPatterns
{ "type": "string", "default": "(resource.type = gcs_bucket AND (protoPayload.authorizationInfo.permission = storage.buckets.create OR protoPayload.authorizationInfo.permission = storage.buckets.delete OR protoPayload.authorizationInfo.permission = storage.buckets.update OR protoPayload.authorizationInfo.permission = storage.buckets.setIamPolicy OR protoPayload.authorizationInfo.permission = storage.objects.create OR protoPayload.authorizationInfo.permission = storage.objects.delete OR protoPayload.authorizationInfo.permission = storage.objects.update OR protoPayload.authorizationInfo.permission = storage.objects.setIamPolicy) AND severity>=INFO AND severity<ERROR)"}
GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-storage
A calculated policy that Guardrails uses to create a compiled list of ALL permission
levels for GCP Storage that is used as input to
the stack that manages the Guardrails IAM permissions objects.
tmod:@turbot/gcp-storage#/policy/types/gcpLevelsCompiled
GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-storage
A calculated policy that Guardrails uses to create a compiled list of ALL
permissions for GCP Storage that is used as
input to the control that manages the IAM stack.
tmod:@turbot/gcp-storage#/policy/types/gcpCompiledServicePermissions