Policy types for @turbot/gcp-appengine
- GCP > App Engine > API Enabled
- GCP > App Engine > Application > CMDB
- GCP > App Engine > Approved Regions [Default]
- GCP > App Engine > CMDB
- GCP > App Engine > Enabled
- GCP > App Engine > Firewall Rule > Active
- GCP > App Engine > Firewall Rule > Active > Age
- GCP > App Engine > Firewall Rule > Active > Last Modified
- GCP > App Engine > Firewall Rule > Approved
- GCP > App Engine > Firewall Rule > Approved > Custom
- GCP > App Engine > Firewall Rule > Approved > Usage
- GCP > App Engine > Firewall Rule > CMDB
- GCP > App Engine > Instance > Active
- GCP > App Engine > Instance > Active > Age
- GCP > App Engine > Instance > Active > Last Modified
- GCP > App Engine > Instance > Approved
- GCP > App Engine > Instance > Approved > Custom
- GCP > App Engine > Instance > Approved > Usage
- GCP > App Engine > Instance > CMDB
- GCP > App Engine > Instance > Usage
- GCP > App Engine > Instance > Usage > Limit
- GCP > App Engine > Labels Template [Default]
- GCP > App Engine > Permissions
- GCP > App Engine > Permissions > Levels
- GCP > App Engine > Permissions > Levels > Modifiers
- GCP > App Engine > Regions
- GCP > App Engine > Service > Active
- GCP > App Engine > Service > Active > Age
- GCP > App Engine > Service > Active > Last Modified
- GCP > App Engine > Service > Approved
- GCP > App Engine > Service > Approved > Custom
- GCP > App Engine > Service > Approved > Usage
- GCP > App Engine > Service > CMDB
- GCP > App Engine > Service > Labels
- GCP > App Engine > Service > Labels > Template
- GCP > App Engine > Service > Usage
- GCP > App Engine > Service > Usage > Limit
- GCP > App Engine > Version > Active
- GCP > App Engine > Version > Active > Age
- GCP > App Engine > Version > Active > Last Modified
- GCP > App Engine > Version > Approved
- GCP > App Engine > Version > Approved > Custom
- GCP > App Engine > Version > Approved > Usage
- GCP > App Engine > Version > CMDB
- GCP > App Engine > Version > Usage
- GCP > App Engine > Version > Usage > Limit
- GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-appengine
- GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-appengine
- GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-appengine
GCP > App Engine > API Enabled
Check whether GCP App Engine 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 > App Engine > API Enabled
control compares
the API state against the API Enabled policies,
raises an alarm, and takes the defined enforcement action.
tmod:@turbot/gcp-appengine#/policy/types/appEngineApiEnabled
[ "Skip", "Check: Disabled", "Check: Enabled", "Check: Enabled if App Engine > Enabled", "Enforce: Disabled", "Enforce: Enabled", "Enforce: Enabled if App Engine > Enabled"]
{ "type": "string", "enum": [ "Skip", "Check: Disabled", "Check: Enabled", "Check: Enabled if App Engine > Enabled", "Enforce: Disabled", "Enforce: Enabled", "Enforce: Enabled if App Engine > Enabled" ], "default": "Skip"}
GCP > App Engine > Application > CMDB
Configure whether to record and synchronize details for the GCP App Engine application into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Turbot CMDB.
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".
tmod:@turbot/gcp-appengine#/policy/types/applicationCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if App Engine API is enabled"}
GCP > App Engine > Approved Regions [Default]
A list of GCP regions in which GCP App Engine 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 App Engine resources' Approved > Regions policies.
tmod:@turbot/gcp-appengine#/policy/types/appEngineApprovedRegionsDefault
"{\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 > App Engine > CMDB
Configure whether to record and synchronize details for the GCP App Engine app engine 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 > App Engine > App Engine > 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-appengine#/policy/types/appEngineCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled"}
GCP > App Engine > Enabled
Enabled App Engine.
tmod:@turbot/gcp-appengine#/policy/types/appEngineEnabled
[ "Enabled", "Enabled: Metadata Only", "Disabled"]
{ "type": "string", "enum": [ "Enabled", "Enabled: Metadata Only", "Disabled" ], "example": [ "Enabled" ], "default": "Disabled"}
GCP > App Engine > Firewall Rule > Active
Determine the action to take when an GCP App Engine firewall rule, based on the GCP > App Engine > Firewall Rule > 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 > App Engine > Firewall Rule > 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-appengine#/policy/types/firewallRuleActive
[ "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 > App Engine > Firewall Rule > Active > Age
The age after which the GCP App Engine firewall rule
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 > App Engine > Firewall Rule > 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-appengine#/policy/types/firewallRuleActiveAge
[ "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 > App Engine > Firewall Rule > Active > Last Modified
The number of days since the GCP App Engine firewall rule 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 > App Engine > Firewall Rule > 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-appengine#/policy/types/firewallRuleActiveLastModified
[ "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 > App Engine > Firewall Rule > Approved
Determine the action to take when a GCP App Engine firewall rule is not approved based on GCP > App Engine > Firewall Rule > 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.
See Approved for more information.
tmod:@turbot/gcp-appengine#/policy/types/firewallRuleApproved
[ "Skip", "Check: Approved"]
{ "type": "string", "enum": [ "Skip", "Check: Approved" ], "example": [ "Check: Approved" ], "default": "Skip"}
GCP > App Engine > Firewall Rule > Approved > Custom
Determine whether the GCP App Engine firewall rule is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine firewall rule is not approved, it will be subject to the action specified in the GCP > App Engine > Firewall Rule > 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-appengine#/policy/types/firewallRuleApprovedCustom
{ "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 > App Engine > Firewall Rule > Approved > Usage
Determine whether the GCP App Engine firewall rule is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine firewall rule is not approved, it will be subject to the action specified in the GCP > App Engine > Firewall Rule > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-appengine#/policy/types/firewallRuleApprovedUsage
[ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled" ], "example": [ "Not approved" ], "default": "Approved if GCP > App Engine > Enabled"}
GCP > App Engine > Firewall Rule > CMDB
Configure whether to record and synchronize details for the GCP App Engine firewall rule into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
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".
tmod:@turbot/gcp-appengine#/policy/types/firewallRuleCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if App Engine API is enabled"}
GCP > App Engine > Instance > Active
Determine the action to take when an GCP App Engine instance, based on the GCP > App Engine > Instance > 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 > App Engine > Instance > 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-appengine#/policy/types/instanceActive
[ "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 > App Engine > Instance > Active > Age
The age after which the GCP App Engine instance
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 > App Engine > Instance > 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-appengine#/policy/types/instanceActiveAge
[ "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 > App Engine > Instance > Active > Last Modified
The number of days since the GCP App Engine instance 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 > App Engine > Instance > 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-appengine#/policy/types/instanceActiveLastModified
[ "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 > App Engine > Instance > Approved
Determine the action to take when a GCP App Engine instance is not approved based on GCP > App Engine > Instance > 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-appengine#/policy/types/instanceApproved
[ "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 > App Engine > Instance > Approved > Custom
Determine whether the GCP App Engine instance is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine instance is not approved, it will be subject to the action specified in the GCP > App Engine > Instance > 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-appengine#/policy/types/instanceApprovedCustom
{ "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 > App Engine > Instance > Approved > Usage
Determine whether the GCP App Engine instance is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine instance is not approved, it will be subject to the action specified in the GCP > App Engine > Instance > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-appengine#/policy/types/instanceApprovedUsage
[ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled" ], "example": [ "Not approved" ], "default": "Approved if GCP > App Engine > Enabled"}
GCP > App Engine > Instance > CMDB
Configure whether to record and synchronize details for the GCP App Engine instance 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".
tmod:@turbot/gcp-appengine#/policy/types/instanceCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if App Engine API is enabled"}
GCP > App Engine > Instance > Usage
Configure the number of GCP App Engine instances that can be used for this version and the current consumption against the limit.
You can configure the behavior of the control with this GCP > App Engine > Instance > Usage
policy.
tmod:@turbot/gcp-appengine#/policy/types/instanceUsage
[ "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 > App Engine > Instance > Usage > Limit
Maximum number of items that can be created for this version
tmod:@turbot/gcp-appengine#/policy/types/instanceUsageLimit
{ "type": "integer", "minimum": 0, "default": 20}
GCP > App Engine > Labels Template [Default]
A template used to generate the keys and values for GCP App Engine resources.
By default, all App Engine resource Labels > Template policies will use this value.
tmod:@turbot/gcp-appengine#/policy/types/appEngineLabelsTemplate
"{\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 > App Engine > Permissions
Configure whether permissions policies are in effect for GCP App Engine.
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-appengine#/policy/types/appEnginePermissions
[ "Enabled", "Disabled", "Enabled if GCP > App Engine > Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if GCP > App Engine > Enabled" ], "example": [ "Enabled" ], "default": "Enabled if GCP > App Engine > Enabled"}
GCP > App Engine > Permissions > Levels
Define the permissions levels that can be used to grant access to App Engine
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-appengine#/policy/types/appEnginePermissionsLevels
[ "{\n item: project {\n turbot{\n id\n }\n }\n}\n", "{\n availableLevels: policyValues(filter:\"policyTypeLevel:self resourceId:{{ $.item.turbot.id }} policyType:'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 > App Engine > 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-appengine#/policy/types/appEnginePermissionsLevelsModifiers
GCP > App Engine > Regions
A list of GCP regions in which GCP App Engine 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 App Engine resources' Regions policies.
tmod:@turbot/gcp-appengine#/policy/types/appEngineRegionsDefault
{ "allOf": [ { "$ref": "gcp#/definitions/regionNameMatcherList" }, { "default": [ "asia-east2", "asia-northeast1", "asia-northeast2", "asia-south1", "australia-southeast1", "europe-west1", "europe-west2", "europe-west3", "europe-west6", "northamerica-northeast1", "southamerica-east1", "us-central1", "us-east1", "us-east4", "us-west2" ] } ]}
GCP > App Engine > Service > Active
Determine the action to take when an GCP App Engine service, based on the GCP > App Engine > Service > 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 > App Engine > Service > 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-appengine#/policy/types/serviceActive
[ "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 > App Engine > Service > Active > Age
The age after which the GCP App Engine service
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 > App Engine > Service > 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-appengine#/policy/types/serviceActiveAge
[ "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 > App Engine > Service > Active > Last Modified
The number of days since the GCP App Engine service 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 > App Engine > Service > 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-appengine#/policy/types/serviceActiveLastModified
[ "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 > App Engine > Service > Approved
Determine the action to take when a GCP App Engine service is not approved based on GCP > App Engine > Service > 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-appengine#/policy/types/serviceApproved
[ "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 > App Engine > Service > Approved > Custom
Determine whether the GCP App Engine service is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine service is not approved, it will be subject to the action specified in the GCP > App Engine > Service > 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-appengine#/policy/types/serviceApprovedCustom
{ "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 > App Engine > Service > Approved > Usage
Determine whether the GCP App Engine service is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine service is not approved, it will be subject to the action specified in the GCP > App Engine > Service > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-appengine#/policy/types/serviceApprovedUsage
[ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled" ], "example": [ "Not approved" ], "default": "Approved if GCP > App Engine > Enabled"}
GCP > App Engine > Service > CMDB
Configure whether to record and synchronize details for the GCP App Engine service into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
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".
tmod:@turbot/gcp-appengine#/policy/types/serviceCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if App Engine API is enabled"}
GCP > App Engine > Service > Labels
Determine the action to take when an GCP App Engine service labels are not updated based on the GCP > App Engine > Service > Labels > *
policies.
The control ensure GCP App Engine service labels include labels defined in GCP > App Engine > Service > Labels > Template
.
Labels not defined in Service 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-appengine#/policy/types/serviceLabels
[ "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 > App Engine > Service > Labels > Template
The template is used to generate the keys and values for GCP App Engine service.
Labels not defined in Service 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-appengine#/policy/types/serviceLabelsTemplate
[ "{\n project {\n turbot {\n id\n }\n }\n}\n", "{\n defaultLabels: policyValue(uri:\"tmod:@turbot/gcp-appengine#/policy/types/appEngineLabelsTemplate\" 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 > App Engine > Service > Usage
Configure the number of GCP App Engine services that can be used for this application and the current consumption against the limit.
You can configure the behavior of the control with this GCP > App Engine > Service > Usage
policy.
tmod:@turbot/gcp-appengine#/policy/types/serviceUsage
[ "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 > App Engine > Service > Usage > Limit
Maximum number of items that can be created for this application
tmod:@turbot/gcp-appengine#/policy/types/serviceUsageLimit
{ "type": "integer", "minimum": 0, "default": 110}
GCP > App Engine > Version > Active
Determine the action to take when an GCP App Engine version, based on the GCP > App Engine > Version > 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 > App Engine > Version > 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-appengine#/policy/types/versionActive
[ "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 > App Engine > Version > Active > Age
The age after which the GCP App Engine version
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 > App Engine > Version > 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-appengine#/policy/types/versionActiveAge
[ "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 > App Engine > Version > Active > Last Modified
The number of days since the GCP App Engine version 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 > App Engine > Version > 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-appengine#/policy/types/versionActiveLastModified
[ "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 > App Engine > Version > Approved
Determine the action to take when a GCP App Engine version is not approved based on GCP > App Engine > Version > 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-appengine#/policy/types/versionApproved
[ "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 > App Engine > Version > Approved > Custom
Determine whether the GCP App Engine version is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine version is not approved, it will be subject to the action specified in the GCP > App Engine > Version > 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-appengine#/policy/types/versionApprovedCustom
{ "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 > App Engine > Version > Approved > Usage
Determine whether the GCP App Engine version is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP App Engine version is not approved, it will be subject to the action specified in the GCP > App Engine > Version > Approved
policy.
See Approved for more information.
tmod:@turbot/gcp-appengine#/policy/types/versionApprovedUsage
[ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if GCP > App Engine > Enabled" ], "example": [ "Not approved" ], "default": "Approved if GCP > App Engine > Enabled"}
GCP > App Engine > Version > CMDB
Configure whether to record and synchronize details for the GCP App Engine version into the CMDB.
The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
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".
tmod:@turbot/gcp-appengine#/policy/types/versionCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if App Engine API is enabled", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if App Engine API is enabled"}
GCP > App Engine > Version > Usage
Configure the number of GCP App Engine versions that can be used for this service and the current consumption against the limit.
You can configure the behavior of the control with this GCP > App Engine > Version > Usage
policy.
tmod:@turbot/gcp-appengine#/policy/types/versionUsage
[ "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 > App Engine > Version > Usage > Limit
Maximum number of items that can be created for this service
tmod:@turbot/gcp-appengine#/policy/types/versionUsageLimit
{ "type": "integer", "minimum": 0, "default": 225}
GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-appengine
GCP logs advanced filter
used to specify a subset of log entries that is forwarded to the Guardrails Event Handlers
by the logging sink on behalf of GCP App Engine.
tmod:@turbot/gcp-appengine#/policy/types/appEngineCustomEventPatterns
{ "type": "string", "default": "(resource.type = gae_app AND (protoPayload.authorizationInfo.permission = appengine.applications.create OR protoPayload.authorizationInfo.permission = appengine.applications.update OR protoPayload.authorizationInfo.permission = appengine.services.delete OR protoPayload.authorizationInfo.permission = appengine.services.update OR protoPayload.authorizationInfo.permission = appengine.versions.create OR protoPayload.authorizationInfo.permission = appengine.versions.update OR protoPayload.authorizationInfo.permission = appengine.versions.delete OR protoPayload.authorizationInfo.permission = appengine.instances.delete) AND severity>=INFO AND severity<ERROR)"}
GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-appengine
A calculated policy that Guardrails uses to create a compiled list of ALL permission
levels for GCP App Engine that is used as input to
the stack that manages the Guardrails IAM permissions objects.
tmod:@turbot/gcp-appengine#/policy/types/gcpLevelsCompiled
GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-appengine
A calculated policy that Guardrails uses to create a compiled list of ALL
permissions for GCP App Engine that is used as
input to the control that manages the IAM stack.
tmod:@turbot/gcp-appengine#/policy/types/gcpCompiledServicePermissions