Product logo
DocsBlogPricing

Policy types for @turbot/azure-loganalytics

Azure > Log Analytics > Approved Regions [Default]

A list of Azure regions in which Azure Log Analytics 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 Log Analytics resources' Approved > Regions policies.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsApprovedRegionsDefault
Category
Parent
Targets
Default Template Input
"{\n  regions: policyValue(uri:\"tmod:@turbot/azure#/policy/types/approvedRegionsDefault\") {\n    value\n  }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"
Schema

Azure > Log Analytics > Enabled

Enable Azure Log Analytics service.

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

Azure > Log Analytics > Log Analytics Workspace > Active

Determine the action to take when an Azure Log Analytics log analytics workspace, based on the Azure > Log Analytics > Log Analytics Workspace > 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 > Log Analytics > Log Analytics Workspace > 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.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceActive
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: Active",
  "Enforce: Delete inactive with 1 day warning",
  "Enforce: Delete inactive with 3 days warning",
  "Enforce: Delete inactive with 7 days warning",
  "Enforce: Delete inactive with 14 days warning",
  "Enforce: Delete inactive with 30 days warning",
  "Enforce: Delete inactive with 60 days warning",
  "Enforce: Delete inactive with 90 days warning",
  "Enforce: Delete inactive with 180 days warning",
  "Enforce: Delete inactive with 365 days warning"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Active",
    "Enforce: Delete inactive with 1 day warning",
    "Enforce: Delete inactive with 3 days warning",
    "Enforce: Delete inactive with 7 days warning",
    "Enforce: Delete inactive with 14 days warning",
    "Enforce: Delete inactive with 30 days warning",
    "Enforce: Delete inactive with 60 days warning",
    "Enforce: Delete inactive with 90 days warning",
    "Enforce: Delete inactive with 180 days warning",
    "Enforce: Delete inactive with 365 days warning"
  ],
  "example": [
    "Check: Active"
  ],
  "default": "Skip"
}

Azure > Log Analytics > Log Analytics Workspace > Active > Age

The age after which the Azure Log Analytics log analytics workspace
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 > Log Analytics > Log Analytics Workspace > 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.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceActiveAge
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Force inactive if age > 1 day",
  "Force inactive if age > 3 days",
  "Force inactive if age > 7 days",
  "Force inactive if age > 14 days",
  "Force inactive if age > 30 days",
  "Force inactive if age > 60 days",
  "Force inactive if age > 90 days",
  "Force inactive if age > 180 days",
  "Force inactive if age > 365 days"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Force inactive if age > 1 day",
    "Force inactive if age > 3 days",
    "Force inactive if age > 7 days",
    "Force inactive if age > 14 days",
    "Force inactive if age > 30 days",
    "Force inactive if age > 60 days",
    "Force inactive if age > 90 days",
    "Force inactive if age > 180 days",
    "Force inactive if age > 365 days"
  ],
  "example": [
    "Force inactive if age > 90 days"
  ],
  "default": "Skip"
}

Azure > Log Analytics > Log Analytics Workspace > Active > Last Modified

The number of days since the Azure Log Analytics log analytics workspace 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 > Log Analytics > Log Analytics Workspace > 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.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceActiveLastModified
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Active if last modified <= 1 day",
  "Active if last modified <= 3 days",
  "Active if last modified <= 7 days",
  "Active if last modified <= 14 days",
  "Active if last modified <= 30 days",
  "Active if last modified <= 60 days",
  "Active if last modified <= 90 days",
  "Active if last modified <= 180 days",
  "Active if last modified <= 365 days",
  "Force active if last modified <= 1 day",
  "Force active if last modified <= 3 days",
  "Force active if last modified <= 7 days",
  "Force active if last modified <= 14 days",
  "Force active if last modified <= 30 days",
  "Force active if last modified <= 60 days",
  "Force active if last modified <= 90 days",
  "Force active if last modified <= 180 days",
  "Force active if last modified <= 365 days"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Active if last modified <= 1 day",
    "Active if last modified <= 3 days",
    "Active if last modified <= 7 days",
    "Active if last modified <= 14 days",
    "Active if last modified <= 30 days",
    "Active if last modified <= 60 days",
    "Active if last modified <= 90 days",
    "Active if last modified <= 180 days",
    "Active if last modified <= 365 days",
    "Force active if last modified <= 1 day",
    "Force active if last modified <= 3 days",
    "Force active if last modified <= 7 days",
    "Force active if last modified <= 14 days",
    "Force active if last modified <= 30 days",
    "Force active if last modified <= 60 days",
    "Force active if last modified <= 90 days",
    "Force active if last modified <= 180 days",
    "Force active if last modified <= 365 days"
  ],
  "example": [
    "Active if last modified <= 90 days"
  ],
  "default": "Skip"
}

Azure > Log Analytics > Log Analytics Workspace > Approved

Determine the action to take when an Azure Log Analytics log analytics workspace is not approved based on Azure > Log Analytics > Log Analytics Workspace > Approved > * policies.

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

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

See Approved for more information.

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

Azure > Log Analytics > Log Analytics Workspace > Approved > Custom

Determine whether the Azure Log Analytics log analytics workspace is allowed to exist.
This policy will be evaluated by the Approved control. If an Azure Log Analytics log analytics workspace is not approved, it will be subject to the action specified in the Azure > Log Analytics > Log Analytics Workspace > Approved policy.
See Approved for more information.

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

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceApprovedCustom
Category
Parent
Targets
Schema
{
  "example": [
    "Approved",
    "Not approved",
    "Skip",
    {
      "result": "Approved"
    },
    {
      "title": "string",
      "result": "Not approved"
    },
    {
      "title": "string",
      "result": "Approved",
      "message": "string"
    },
    [
      {
        "title": "string",
        "result": "Approved",
        "message": "string"
      },
      {
        "title": "string",
        "result": "Not approved",
        "message": "string"
      }
    ]
  ],
  "anyOf": [
    {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "title": {
            "type": "string",
            "pattern": "^[\\W\\w]{1,32}$"
          },
          "message": {
            "type": "string",
            "pattern": "^[\\W\\w]{1,128}$"
          },
          "result": {
            "type": "string",
            "pattern": "^(Approved|Not approved|Skip)$"
          }
        },
        "required": [
          "result"
        ],
        "additionalProperties": false
      }
    },
    {
      "type": "object",
      "properties": {
        "title": {
          "type": "string",
          "pattern": "^[\\W\\w]{1,32}$"
        },
        "message": {
          "type": "string",
          "pattern": "^[\\W\\w]{1,128}$"
        },
        "result": {
          "type": "string",
          "pattern": "^(Approved|Not approved|Skip)$"
        }
      },
      "required": [
        "result"
      ],
      "additionalProperties": false
    },
    {
      "type": "string",
      "pattern": "^(Approved|Not approved|Skip)$"
    }
  ],
  "default": "Skip"
}

Azure > Log Analytics > Log Analytics Workspace > Approved > Regions

A list of Azure regions in which Azure Log Analytics log analytics workspaces 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 Log Analytics log analytics workspace is created in a region that is not in the approved list, it will be subject to the action specified in the Azure > Log Analytics > Log Analytics Workspace > Approved policy.

See Approved for more information.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceApprovedRegions
Category
Parent
Targets
Default Template Input
"{\n  regions: policyValue(uri:\"tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsApprovedRegionsDefault\") {\n    value\n  }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"
Schema

Azure > Log Analytics > Log Analytics Workspace > Approved > Usage

Determine whether the Azure Log Analytics log analytics workspace is allowed to exist.

This policy will be evaluated by the Approved control. If an Azure Log Analytics log analytics workspace is not approved, it will be subject to the action specified in the Azure > Log Analytics > Log Analytics Workspace > Approved policy.

See Approved for more information.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceApprovedUsage
Category
Parent
Targets
Valid Value
[
  "Not approved",
  "Approved",
  "Approved if Azure > Log Analytics > Enabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Not approved",
    "Approved",
    "Approved if Azure > Log Analytics > Enabled"
  ],
  "example": [
    "Not approved"
  ],
  "default": "Approved if Azure > Log Analytics > Enabled"
}

Azure > Log Analytics > Log Analytics Workspace > CMDB

Configure whether to record and synchronize details for the Azure Log Analytics log analytics workspace 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 > Log Analytics > Log Analytics Workspace > Regions policy, the CMDB control will delete the resource from the CMDB.

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

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceCmdb
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Enforce: Enabled",
  "Enforce: Enabled if Operational Insights provider is Registered",
  "Enforce: Disabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Enforce: Enabled",
    "Enforce: Enabled if Operational Insights provider is Registered",
    "Enforce: Disabled"
  ],
  "example": [
    "Skip"
  ],
  "default": "Enforce: Enabled if Operational Insights provider is Registered"
}

Azure > Log Analytics > Log Analytics Workspace > Data Retention

Configure the Azure Log Analytics Workspace data retention. The retention days varies from 30 to 730 days where 30 is the default value.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceDataRetention
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: Data Retention",
  "Enforce: Data Retention"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Data Retention",
    "Enforce: Data Retention"
  ],
  "default": "Skip"
}

Azure > Log Analytics > Log Analytics Workspace > Data Retention > Days

Configure the Azure Log Analytics Workspace data retention. The retention days varies from 30 to 730 days where 30 is the default value.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceDays
Category
Parent
Targets
Schema
{
  "type": "integer",
  "default": 30,
  "minimum": 30,
  "maximum": 730
}

Azure > Log Analytics > Log Analytics Workspace > Pricing Tier

The Pricing Tier control checks the resource's pricing tier based on Azure > Log Analytics > Log Analytics Workspace > Pricing Tier policy and raises an alarm if the pricing tier is not set according to this policy.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspacePricingTier
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: PerGB2018 tier"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: PerGB2018 tier"
  ],
  "default": "Skip"
}

Azure > Log Analytics > Log Analytics Workspace > Regions

A list of Azure regions in which Azure Log Analytics log analytics workspaces are supported for use.

Any log analytics workspaces 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.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceRegions
Category
Parent
Targets
Default Template Input
"{\n  regions: policyValue(uri:\"tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsRegionsDefault\") {\n    value\n  }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"
Schema

Azure > Log Analytics > Log Analytics Workspace > Tags

Determine the action to take when an Azure Log Analytics log analytics workspace tags are not updated based on the Azure > Log Analytics > Log Analytics Workspace > Tags > * policies.

The control ensure Azure Log Analytics log analytics workspace tags include tags defined in Azure > Log Analytics > Log Analytics Workspace > Tags > Template.

Tags not defined in Log Analytics Workspace 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.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsWorkspaceTags
Category
Parent
Targets
Valid Value
[
  "Skip",
  "Check: Tags are correct",
  "Enforce: Set tags"
]
Schema
{
  "type": "string",
  "enum": [
    "Skip",
    "Check: Tags are correct",
    "Enforce: Set tags"
  ],
  "example": [
    "Check: Tags are correct"
  ],
  "default": "Skip"
}

Azure > Log Analytics > Log Analytics Workspace > Tags > Template

The template is used to generate the keys and values for Azure Log Analytics log analytics workspace.

Tags not defined in Log Analytics Workspace 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.

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

Azure > Log Analytics > Permissions

Configure whether permissions policies are in effect for Azure Log Analytics
This setting does not affect Subscription level permissions (Azure/Admin, Azure/Owner, etc)

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsPermissions
Category
Parent
Targets
Valid Value
[
  "Enabled",
  "Disabled",
  "Enabled if Azure > Log Analytics > Enabled"
]
Schema
{
  "type": "string",
  "enum": [
    "Enabled",
    "Disabled",
    "Enabled if Azure > Log Analytics > Enabled"
  ],
  "example": [
    "Enabled"
  ],
  "default": "Enabled if Azure > Log Analytics > Enabled"
}

Azure > Log Analytics > 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.

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

Azure > Log Analytics > 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 /> - &quot;Microsoft.Log Analytics/Log Analytics/delete&quot;: operator<br /> - &quot;Microsoft.Log Analytics/Log Analytics/write&quot;: admin<br /> - &quot;Microsoft.Log Analytics/Log Analytics/read&quot;: readonly<br />

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsPermissionsLevelsModifiers
Category
Parent
Targets
Schema

Azure > Log Analytics > Regions

A list of Azure regions in which Azure Log Analytics 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 Log Analytics resources' Regions policies.

URI
tmod:@turbot/azure-loganalytics#/policy/types/logAnalyticsRegionsDefault
Category
Parent
Targets
Schema
{
  "allOf": [
    {
      "$ref": "azure#/definitions/regionNameMatcherList"
    },
    {
      "default": [
        "australiacentral",
        "australiacentral2",
        "australiaeast",
        "australiasoutheast",
        "brazilsouth",
        "brazilsoutheast",
        "canadacentral",
        "canadaeast",
        "centralindia",
        "centralus",
        "chinaeast2",
        "chinaeast3",
        "chinanorth3",
        "eastasia",
        "eastus",
        "eastus2",
        "francecentral",
        "francesouth",
        "germanywestcentral",
        "japaneast",
        "japanwest",
        "koreacentral",
        "koreasouth",
        "northcentralus",
        "northeurope",
        "norwayeast",
        "norwaywest",
        "qatarcentral",
        "southafricanorth",
        "southcentralus",
        "southeastasia",
        "southindia",
        "swedencentral",
        "switzerlandnorth",
        "switzerlandwest",
        "uaecentral",
        "uaenorth",
        "uksouth",
        "ukwest",
        "usgovarizona",
        "usgovvirginia",
        "westcentralus",
        "westeurope",
        "westus",
        "westus2",
        "westus3"
      ]
    }
  ]
}

Azure > Log Analytics > Tags Template [Default]

A template used to generate the keys and values for Azure Log Analytics resources.

By default, all Log Analytics resource Tags > Template policies will use this value.

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

Azure > Turbot > Permissions > Compiled > Levels > @turbot/azure-loganalytics

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

URI
tmod:@turbot/azure-loganalytics#/policy/types/azureLevelsCompiled
Category
Parent
Targets
Schema

Azure > Turbot > Permissions > Compiled > Service Permissions > @turbot/azure-loganalytics

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

URI
tmod:@turbot/azure-loganalytics#/policy/types/azureCompiledServicePermissions
Category
Parent
Targets
Schema