Policy types for @turbot/azure-appservice
- Azure > App Service > App Service Plan > Active
- Azure > App Service > App Service Plan > Active > Age
- Azure > App Service > App Service Plan > Active > Last Modified
- Azure > App Service > App Service Plan > Approved
- Azure > App Service > App Service Plan > Approved > Custom
- Azure > App Service > App Service Plan > Approved > Regions
- Azure > App Service > App Service Plan > Approved > Usage
- Azure > App Service > App Service Plan > CMDB
- Azure > App Service > App Service Plan > Regions
- Azure > App Service > App Service Plan > Tags
- Azure > App Service > App Service Plan > Tags > Template
- Azure > App Service > Approved Regions [Default]
- Azure > App Service > Enabled
- Azure > App Service > Function App > Active
- Azure > App Service > Function App > Active > Age
- Azure > App Service > Function App > Active > Last Modified
- Azure > App Service > Function App > Approved
- Azure > App Service > Function App > Approved > Custom
- Azure > App Service > Function App > Approved > Regions
- Azure > App Service > Function App > Approved > Usage
- Azure > App Service > Function App > CMDB
- Azure > App Service > Function App > FTPS State
- Azure > App Service > Function App > HTTP 2.0 Enabled
- Azure > App Service > Function App > HTTPS Only
- Azure > App Service > Function App > Minimum TLS Version
- Azure > App Service > Function App > Regions
- Azure > App Service > Function App > Tags
- Azure > App Service > Function App > Tags > Template
- Azure > App Service > Permissions
- Azure > App Service > Permissions > Levels
- Azure > App Service > Permissions > Levels > Modifiers
- Azure > App Service > Regions
- Azure > App Service > Tags Template [Default]
- Azure > App Service > Web App > Active
- Azure > App Service > Web App > Active > Age
- Azure > App Service > Web App > Active > Last Modified
- Azure > App Service > Web App > Approved
- Azure > App Service > Web App > Approved > Custom
- Azure > App Service > Web App > Approved > Regions
- Azure > App Service > Web App > Approved > Usage
- Azure > App Service > Web App > CMDB
- Azure > App Service > Web App > FTPS State
- Azure > App Service > Web App > HTTP 2.0 Enabled
- Azure > App Service > Web App > HTTPS Only
- Azure > App Service > Web App > Minimum TLS Version
- Azure > App Service > Web App > Regions
- Azure > App Service > Web App > Tags
- Azure > App Service > Web App > Tags > Template
- Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-appservice
- Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-appservice
Azure > App Service > App Service Plan > Active
Determine the action to take when an Azure App Service app service plan, based on the Azure > App Service > App Service Plan > 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 (Azure > App Service > App Service Plan > 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: In 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/azure-appservice#/policy/types/appServicePlanActive
[ "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"}
Azure > App Service > App Service Plan > Active > Age
The age after which the Azure App Service app service plan
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 (Azure > App Service > App Service Plan > 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 In 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/azure-appservice#/policy/types/appServicePlanActiveAge
[ "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"}
Azure > App Service > App Service Plan > Active > Last Modified
The number of days since the Azure App Service app service plan 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 (Azure > App Service > App Service Plan > 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 In contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.
tmod:@turbot/azure-appservice#/policy/types/appServicePlanActiveLastModified
[ "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"}
Azure > App Service > App Service Plan > Approved
Determine the action to take when an Azure App Service app service plan is not approved based on Azure > App Service > App Service Plan > 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/azure-appservice#/policy/types/appServicePlanApproved
[ "Skip", "Check: Approved", "Enforce: Delete unapproved if new"]
{ "type": "string", "enum": [ "Skip", "Check: Approved", "Enforce: Delete unapproved if new" ], "example": [ "Check: Approved" ], "default": "Skip"}
Azure > App Service > App Service Plan > Approved > Custom
Determine whether the Azure App Service app service plan is allowed to exist.
This policy will be evaluated by the Approved control. If an Azure App Service app service plan is not approved, it will be subject to the action specified in the Azure > App Service > App Service Plan > 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/azure-appservice#/policy/types/appServicePlanApprovedCustom
{ "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"}
Azure > App Service > App Service Plan > Approved > Regions
A list of Azure regions in which Azure App Service app service plans 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 an Azure App Service app service plan is created in a region that is not in the approved list, it will be subject to the action specified in the Azure > App Service > App Service Plan > Approved
policy.
See Approved for more information.
tmod:@turbot/azure-appservice#/policy/types/appServicePlanApprovedRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/azure-appservice#/policy/types/appServiceApprovedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
Azure > App Service > App Service Plan > Approved > Usage
Determine whether the Azure App Service app service plan is allowed to exist.
This policy will be evaluated by the Approved control. If an Azure App Service app service plan is not approved, it will be subject to the action specified in the Azure > App Service > App Service Plan > Approved
policy.
See Approved for more information.
tmod:@turbot/azure-appservice#/policy/types/appServicePlanApprovedUsage
[ "Not approved", "Approved", "Approved if Azure > App Service > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if Azure > App Service > Enabled" ], "example": [ "Not approved" ], "default": "Approved if Azure > App Service > Enabled"}
Azure > App Service > App Service Plan > CMDB
Configure whether to record and synchronize details for the Azure App Service app service plan 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 Azure > App Service > App Service Plan > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/azure-appservice#/policy/types/appServicePlanCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if Web provider is Registered", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if Web provider is Registered", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if Web provider is Registered"}
Azure > App Service > App Service Plan > Regions
A list of Azure regions in which Azure App Service app service plans are supported for use.
Any app service plans 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/azure-appservice#/policy/types/appServicePlanRegions
{ "allOf": [ { "$ref": "azure#/definitions/regionNameMatcherList" }, { "default": [ "australiaeast", "australiasoutheast", "brazilsouth", "canadacentral", "canadaeast", "centralindia", "centralus", "eastasia", "eastus", "eastus2", "francecentral", "japaneast", "japanwest", "koreacentral", "koreasouth", "northcentralus", "northeurope", "southafricanorth", "southcentralus", "southeastasia", "southindia", "uksouth", "ukwest", "usgovarizona", "usgovtexas", "usgovvirginia", "westcentralus", "westeurope", "westindia", "westus", "westus2" ] } ]}
Azure > App Service > App Service Plan > Tags
Determine the action to take when an Azure App Service app service plan tags are not updated based on the Azure > App Service > App Service Plan > Tags > *
policies.
The control ensure Azure App Service app service plan tags include tags defined in Azure > App Service > App Service Plan > Tags > Template
.
Tags not defined in App Service Plan Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/azure-appservice#/policy/types/appServicePlanTags
[ "Skip", "Check: Tags are correct", "Enforce: Set tags"]
{ "type": "string", "enum": [ "Skip", "Check: Tags are correct", "Enforce: Set tags" ], "example": [ "Check: Tags are correct" ], "default": "Skip"}
Azure > App Service > App Service Plan > Tags > Template
The template is used to generate the keys and values for Azure App Service app service plan.
Tags not defined in App Service Plan Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/azure-appservice#/policy/types/appServicePlanTagsTemplate
[ "{\n subscription {\n turbot {\n id\n }\n }\n}\n", "{\n defaultTags: policyValue(uri:\"tmod:@turbot/azure-appservice#/policy/types/appServiceTagsTemplate\" resourceId: \"{{ $.subscription.turbot.id }}\") {\n value\n }\n}\n"]
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
Azure > App Service > Approved Regions [Default]
A list of Azure regions in which Azure App Service 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 Azure App Service resources' Approved > Regions policies.
tmod:@turbot/azure-appservice#/policy/types/appServiceApprovedRegionsDefault
"{\n regions: policyValue(uri:\"tmod:@turbot/azure#/policy/types/approvedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
Azure > App Service > Enabled
Enable Azure App Service service.
tmod:@turbot/azure-appservice#/policy/types/appServiceEnabled
[ "Enabled", "Enabled: Metadata Only", "Disabled"]
{ "type": "string", "enum": [ "Enabled", "Enabled: Metadata Only", "Disabled" ], "example": [ "Enabled" ], "default": "Disabled"}
Azure > App Service > Function App > Active
Determine the action to take when an Azure App Service function app, based on the Azure > App Service > Function App > 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 (Azure > App Service > Function App > 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: In 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/azure-appservice#/policy/types/functionAppActive
[ "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"}
Azure > App Service > Function App > Active > Age
The age after which the Azure App Service function app
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 (Azure > App Service > Function App > 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 In 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/azure-appservice#/policy/types/functionAppActiveAge
[ "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"}
Azure > App Service > Function App > Active > Last Modified
The number of days since the Azure App Service function app 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 (Azure > App Service > Function App > 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 In contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.
tmod:@turbot/azure-appservice#/policy/types/functionAppActiveLastModified
[ "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"}
Azure > App Service > Function App > Approved
Determine the action to take when an Azure App Service function app is not approved based on Azure > App Service > Function App > 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/azure-appservice#/policy/types/functionAppApproved
[ "Skip", "Check: Approved", "Enforce: Delete unapproved if new"]
{ "type": "string", "enum": [ "Skip", "Check: Approved", "Enforce: Delete unapproved if new" ], "example": [ "Check: Approved" ], "default": "Skip"}
Azure > App Service > Function App > Approved > Custom
Determine whether the Azure App Service function app is allowed to exist.
This policy will be evaluated by the Approved control. If an Azure App Service function app is not approved, it will be subject to the action specified in the Azure > App Service > Function App > 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/azure-appservice#/policy/types/functionAppApprovedCustom
{ "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"}
Azure > App Service > Function App > Approved > Regions
A list of Azure regions in which Azure App Service function apps 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 an Azure App Service function app is created in a region that is not in the approved list, it will be subject to the action specified in the Azure > App Service > Function App > Approved
policy.
See Approved for more information.
tmod:@turbot/azure-appservice#/policy/types/functionAppApprovedRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/azure-appservice#/policy/types/appServiceApprovedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
Azure > App Service > Function App > Approved > Usage
Determine whether the Azure App Service function app is allowed to exist.
This policy will be evaluated by the Approved control. If an Azure App Service function app is not approved, it will be subject to the action specified in the Azure > App Service > Function App > Approved
policy.
See Approved for more information.
tmod:@turbot/azure-appservice#/policy/types/functionAppApprovedUsage
[ "Not approved", "Approved", "Approved if Azure > App Service > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if Azure > App Service > Enabled" ], "example": [ "Not approved" ], "default": "Approved if Azure > App Service > Enabled"}
Azure > App Service > Function App > CMDB
Configure whether to record and synchronize details for the Azure App Service function app 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 Azure > App Service > Function App > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/azure-appservice#/policy/types/functionAppCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if Web provider is Registered", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if Web provider is Registered", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if Web provider is Registered"}
Azure > App Service > Function App > FTPS State
Define the state of FTP/FTPS setting required for Azure > App Service > Function App
.
tmod:@turbot/azure-appservice#/policy/types/functionAppFtpsState
[ "Skip", "Check: All allowed", "Check: Disabled", "Check: FTPS only", "Enforce: All allowed", "Enforce: Disabled", "Enforce: FTPS only"]
{ "type": "string", "enum": [ "Skip", "Check: All allowed", "Check: Disabled", "Check: FTPS only", "Enforce: All allowed", "Enforce: Disabled", "Enforce: FTPS only" ], "default": "Skip"}
Azure > App Service > Function App > HTTP 2.0 Enabled
Define the HTTP 2.0 setting required for Azure > App Service > Function App
.
tmod:@turbot/azure-appservice#/policy/types/functionAppHttp20Enabled
[ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled" ], "default": "Skip"}
Azure > App Service > Function App > HTTPS Only
Define the HTTPS Only setting required for Azure > App Service > Function App
.
tmod:@turbot/azure-appservice#/policy/types/functionAppHttpsOnly
[ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled" ], "default": "Skip"}
Azure > App Service > Function App > Minimum TLS Version
Define the Minimum TLS Version setting required for Azure > App Service > Function App
.
tmod:@turbot/azure-appservice#/policy/types/functionAppMinimumTlsVersion
[ "Skip", "Check: TLS 1.0", "Check: TLS 1.1", "Check: TLS 1.2", "Enforce: TLS 1.0", "Enforce: TLS 1.1", "Enforce: TLS 1.2"]
{ "type": "string", "enum": [ "Skip", "Check: TLS 1.0", "Check: TLS 1.1", "Check: TLS 1.2", "Enforce: TLS 1.0", "Enforce: TLS 1.1", "Enforce: TLS 1.2" ], "default": "Skip"}
Azure > App Service > Function App > Regions
A list of Azure regions in which Azure App Service function apps are supported for use.
Any function apps 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/azure-appservice#/policy/types/functionAppRegions
{ "allOf": [ { "$ref": "azure#/definitions/regionNameMatcherList" }, { "default": [ "australiacentral2", "australiaeast", "australiasoutheast", "brazilsouth", "canadacentral", "canadaeast", "centralindia", "centralus", "eastasia", "eastus", "eastus2", "francecentral", "japaneast", "japanwest", "koreacentral", "koreasouth", "northcentralus", "northeurope", "southafricanorth", "southcentralus", "southeastasia", "southindia", "uksouth", "ukwest", "usgovtexas", "usgovvirginia", "westcentralus", "westeurope", "westindia", "westus", "westus2" ] } ]}
Azure > App Service > Function App > Tags
Determine the action to take when an Azure App Service function app tags are not updated based on the Azure > App Service > Function App > Tags > *
policies.
The control ensure Azure App Service function app tags include tags defined in Azure > App Service > Function App > Tags > Template
.
Tags not defined in Function App Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/azure-appservice#/policy/types/functionAppTags
[ "Skip", "Check: Tags are correct", "Enforce: Set tags"]
{ "type": "string", "enum": [ "Skip", "Check: Tags are correct", "Enforce: Set tags" ], "example": [ "Check: Tags are correct" ], "default": "Skip"}
Azure > App Service > Function App > Tags > Template
The template is used to generate the keys and values for Azure App Service function app.
Tags not defined in Function App Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/azure-appservice#/policy/types/functionAppTagsTemplate
[ "{\n subscription {\n turbot {\n id\n }\n }\n}\n", "{\n defaultTags: policyValue(uri:\"tmod:@turbot/azure-appservice#/policy/types/appServiceTagsTemplate\" resourceId: \"{{ $.subscription.turbot.id }}\") {\n value\n }\n}\n"]
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
Azure > App Service > Permissions
Configure whether permissions policies are in effect for Azure App Service
This setting does not affect Subscription level permissions (Azure/Admin, Azure/Owner, etc)
tmod:@turbot/azure-appservice#/policy/types/appServicePermissions
[ "Enabled", "Disabled", "Enabled if Azure > App Service > Enabled"]
{ "type": "string", "enum": [ "Enabled", "Disabled", "Enabled if Azure > App Service > Enabled" ], "example": [ "Enabled" ], "default": "Enabled if Azure > App Service > Enabled"}
Azure > App Service > Permissions > Levels
Define the permissions levels that can be used to grant access to Storage an
Azure Subscription. Permissions levels defined will appear in the UI to assign
access to Guardrails users.
tmod:@turbot/azure-appservice#/policy/types/appServicePermissionsLevels
[ "{\n item: subscription {\n turbot{\n id\n }\n }\n}\n", "{\n availableLevels: policyValues(filter:\"policyTypeLevel:self resourceId:{{ $.item.turbot.id }} policyType:'tmod:@turbot/azure-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": [ "User", "Metadata", "ReadOnly", "Operator", "Admin", "Owner" ] }}
Azure > App Service > Permissions > Levels > Modifiers
A map of Azure API to Guardrails Permission Level used to customize Guardrails'
standard permissions. You can add, remove or redefine the mapping of
Azure API operations to Guardrails permissions levels here.<br />example:<br /> - "Microsoft.App Service/App Service/delete": operator<br /> - "Microsoft.App Service/App Service/write": admin<br /> - "Microsoft.App Service/App Service/read": readonly<br />
tmod:@turbot/azure-appservice#/policy/types/appServicePermissionsLevelsModifiers
Azure > App Service > Regions
A list of Azure regions in which Azure App Service 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 Azure App Service resources' Regions policies.
tmod:@turbot/azure-appservice#/policy/types/appServiceRegionsDefault
"{\n regions: policyValue(uri:\"tmod:@turbot/azure#/policy/types/regionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
Azure > App Service > Tags Template [Default]
A template used to generate the keys and values for Azure App Service resources.
By default, all App Service resource Tags > Template policies will use this value.
tmod:@turbot/azure-appservice#/policy/types/appServiceTagsTemplate
"{\n defaultTags: policyValue(uri:\"tmod:@turbot/azure#/policy/types/defaultTagsTemplate\") {\n value\n }\n}\n"
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
Azure > App Service > Web App > Active
Determine the action to take when an Azure App Service web app, based on the Azure > App Service > Web App > 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 (Azure > App Service > Web App > 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: In 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/azure-appservice#/policy/types/webAppActive
[ "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"}
Azure > App Service > Web App > Active > Age
The age after which the Azure App Service web app
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 (Azure > App Service > Web App > 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 In 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/azure-appservice#/policy/types/webAppActiveAge
[ "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"}
Azure > App Service > Web App > Active > Last Modified
The number of days since the Azure App Service web app 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 (Azure > App Service > Web App > 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 In contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.
tmod:@turbot/azure-appservice#/policy/types/webAppActiveLastModified
[ "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"}
Azure > App Service > Web App > Approved
Determine the action to take when an Azure App Service web app is not approved based on Azure > App Service > Web App > 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/azure-appservice#/policy/types/webAppApproved
[ "Skip", "Check: Approved", "Enforce: Delete unapproved if new"]
{ "type": "string", "enum": [ "Skip", "Check: Approved", "Enforce: Delete unapproved if new" ], "example": [ "Check: Approved" ], "default": "Skip"}
Azure > App Service > Web App > Approved > Custom
Determine whether the Azure App Service web app is allowed to exist.
This policy will be evaluated by the Approved control. If an Azure App Service web app is not approved, it will be subject to the action specified in the Azure > App Service > Web App > 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/azure-appservice#/policy/types/webAppApprovedCustom
{ "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"}
Azure > App Service > Web App > Approved > Regions
A list of Azure regions in which Azure App Service web apps 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 an Azure App Service web app is created in a region that is not in the approved list, it will be subject to the action specified in the Azure > App Service > Web App > Approved
policy.
See Approved for more information.
tmod:@turbot/azure-appservice#/policy/types/webAppApprovedRegions
"{\n regions: policyValue(uri:\"tmod:@turbot/azure-appservice#/policy/types/appServiceApprovedRegionsDefault\") {\n value\n }\n}\n"
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
Azure > App Service > Web App > Approved > Usage
Determine whether the Azure App Service web app is allowed to exist.
This policy will be evaluated by the Approved control. If an Azure App Service web app is not approved, it will be subject to the action specified in the Azure > App Service > Web App > Approved
policy.
See Approved for more information.
tmod:@turbot/azure-appservice#/policy/types/webAppApprovedUsage
[ "Not approved", "Approved", "Approved if Azure > App Service > Enabled"]
{ "type": "string", "enum": [ "Not approved", "Approved", "Approved if Azure > App Service > Enabled" ], "example": [ "Not approved" ], "default": "Approved if Azure > App Service > Enabled"}
Azure > App Service > Web App > CMDB
Configure whether to record and synchronize details for the Azure App Service web app 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 Azure > App Service > Web App > Regions
policy, the CMDB control will delete the resource from the CMDB.
(Note: Setting CMDB to "Skip" will also pause these changes.)
tmod:@turbot/azure-appservice#/policy/types/webAppCmdb
[ "Skip", "Enforce: Enabled", "Enforce: Enabled if Web provider is Registered", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Enforce: Enabled", "Enforce: Enabled if Web provider is Registered", "Enforce: Disabled" ], "example": [ "Skip" ], "default": "Enforce: Enabled if Web provider is Registered"}
Azure > App Service > Web App > FTPS State
Define the state of FTP/FTPS setting required for Azure > App Service > Web App
.
tmod:@turbot/azure-appservice#/policy/types/webAppFtpsState
[ "Skip", "Check: All allowed", "Check: Disabled", "Check: FTPS only", "Enforce: All allowed", "Enforce: Disabled", "Enforce: FTPS only"]
{ "type": "string", "enum": [ "Skip", "Check: All allowed", "Check: Disabled", "Check: FTPS only", "Enforce: All allowed", "Enforce: Disabled", "Enforce: FTPS only" ], "default": "Skip"}
Azure > App Service > Web App > HTTP 2.0 Enabled
Define the HTTP 2.0 setting required for Azure > App Service > Web App
.
tmod:@turbot/azure-appservice#/policy/types/webAppHttp20Enabled
[ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled" ], "default": "Skip"}
Azure > App Service > Web App > HTTPS Only
Define the HTTPS Only setting required for Azure > App Service > Web App
.
tmod:@turbot/azure-appservice#/policy/types/webAppHttpsOnly
[ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled"]
{ "type": "string", "enum": [ "Skip", "Check: Enabled", "Check: Disabled", "Enforce: Enabled", "Enforce: Disabled" ], "default": "Skip"}
Azure > App Service > Web App > Minimum TLS Version
Define the Minimum TLS Version setting required for Azure > App Service > Web App
.
tmod:@turbot/azure-appservice#/policy/types/webAppMinimumTlsVersion
[ "Skip", "Check: TLS 1.0", "Check: TLS 1.1", "Check: TLS 1.2", "Enforce: TLS 1.0", "Enforce: TLS 1.1", "Enforce: TLS 1.2"]
{ "type": "string", "enum": [ "Skip", "Check: TLS 1.0", "Check: TLS 1.1", "Check: TLS 1.2", "Enforce: TLS 1.0", "Enforce: TLS 1.1", "Enforce: TLS 1.2" ], "default": "Skip"}
Azure > App Service > Web App > Regions
A list of Azure regions in which Azure App Service web apps are supported for use.
Any web apps 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/azure-appservice#/policy/types/webAppRegions
{ "allOf": [ { "$ref": "azure#/definitions/regionNameMatcherList" }, { "default": [ "australiaeast", "australiasoutheast", "brazilsouth", "canadacentral", "canadaeast", "centralindia", "centralus", "eastasia", "eastus", "eastus2", "francecentral", "japaneast", "japanwest", "koreacentral", "koreasouth", "northcentralus", "northeurope", "southafricanorth", "southcentralus", "southeastasia", "southindia", "uksouth", "ukwest", "usgovarizona", "usgovtexas", "usgovvirginia", "westcentralus", "westeurope", "westindia", "westus", "westus2" ] } ]}
Azure > App Service > Web App > Tags
Determine the action to take when an Azure App Service web app tags are not updated based on the Azure > App Service > Web App > Tags > *
policies.
The control ensure Azure App Service web app tags include tags defined in Azure > App Service > Web App > Tags > Template
.
Tags not defined in Web App Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/azure-appservice#/policy/types/webAppTags
[ "Skip", "Check: Tags are correct", "Enforce: Set tags"]
{ "type": "string", "enum": [ "Skip", "Check: Tags are correct", "Enforce: Set tags" ], "example": [ "Check: Tags are correct" ], "default": "Skip"}
Azure > App Service > Web App > Tags > Template
The template is used to generate the keys and values for Azure App Service web app.
Tags not defined in Web App Tags Template will not be modified or deleted. Setting a tag value to undefined
will result in the tag being deleted.
See Tags for more information.
tmod:@turbot/azure-appservice#/policy/types/webAppTagsTemplate
[ "{\n subscription {\n turbot {\n id\n }\n }\n}\n", "{\n defaultTags: policyValue(uri:\"tmod:@turbot/azure-appservice#/policy/types/appServiceTagsTemplate\" resourceId: \"{{ $.subscription.turbot.id }}\") {\n value\n }\n}\n"]
"{%- if $.defaultTags.value | length == 0 %} [] {%- elif $.defaultTags.value != undefined %}{{ $.defaultTags.value | dump | safe }}{%- else %}{% for item in $.defaultTags.value %}- {{ item }}{% endfor %}{% endif %}"
Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-appservice
A calculated policy that Guardrails uses to create a compiled list of ALL
permission levels for Azure App Service that is used as input to the
stack that manages the Guardrails IAM permissions objects.
tmod:@turbot/azure-appservice#/policy/types/azureLevelsCompiled
Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-appservice
A calculated policy that Guardrails uses to create a compiled list of ALL
permissions for Azure App Service that is used as input to the control that manages
the IAM stack.
tmod:@turbot/azure-appservice#/policy/types/azureCompiledServicePermissions