Azure > Redis > Redis Cache

Azure > Redis > Redis Cache > Delete

Process events for Azure Redis service Redis Cache resources.

The router receives events from the event handler and creates, updates, or deletes Redis Cache resources in the CMDB.


Azure > Resource Group

Azure > Redis > Redis Cache > Router

Update the tags for Azure Redis redis cache.


Azure > Redis > Redis Cache > Set Tags

Update the Azure Redis Cache Firewall settings.


Azure > Redis > Redis Cache > Update Firewall

Update the firewall rules for Azure > Redis > Redis Cache.

This action will update the Redis Cache firewall rules by adding or deleting IP ranges.


Azure > Redis > Redis Cache > Update Firewall IP Ranges

Take an action when an Azure Redis redis cache is not active based on the&#92;n`Azure &gt; Redis &gt; Redis Cache &gt; Active &gt; * policies`.&#92;n&#92;nThe Active control determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated compliance&#92;nenvironment, it&#39;s common to end up with a wide range of alarms that are difficult&#92;nand time consuming to clear. The Active control brings automated, well-defined&#92;ncontrol to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Redis &gt; Redis Cache &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

Azure > Redis > Redis Cache > Active > Age

Azure > Redis > Redis Cache > Active > Last Modified

Azure > Redis > Redis Cache > Active

This control serves as a hierarchical parent for more specific Allowed controls, such as region-based controls and custom rule-based controls.&#92;n

Azure > Redis > Redis Cache > Allowed

Take an action when an Azure Redis redis cache is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the redis cache is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the redis cache is not allowed, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete if not allowed and resource is new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Azure > Redis > Redis Cache > Allowed > Custom > Rules

Azure > Redis > Redis Cache > Allowed > Custom

Take an action when an Azure Redis redis cache is created in a region that is not allowed.&#92;n&#92;nThe `Allowed &gt; Region` control checks if the redis cache is created in an allowed region based on the `Allowed &gt; Region &gt; *` policies. If the redis cache is created in a region that is not in the allowed list, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete if region not allowed and redis cache is new`, this control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Azure > Redis > Redis Cache > Allowed > Region > Regions

Azure > Redis > Redis Cache > Allowed > Region

Record and synchronize details for the Azure Redis redis cache into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is&#92;nresponsible for populating and updating all the attributes for that&#92;nresource type in the Guardrails CMDB.&#92;n&#92;n**Note:** If CMDB is set to Skip for a resource, then it will not be added&#92;nto the CMDB, and no controls that target it will run.&#92;n&#92;nCMDB controls also use the Regions policy associated with the resource. If&#92;nregion is not in `Azure &gt; Redis &gt; Redis Cache &gt; Regions` policy, the CMDB control will delete the&#92;nresource from the CMDB.&#92;n

Azure > Redis > Redis Cache > Regions

Azure > Redis > Redis Cache > CMDB

Discover all Azure Redis redis cache resources and add them to the CMDB.&#92;n&#92;nThe [Discovery](https://turbot.com/guardrails/docs/concepts/guardrails/discovery) control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control.&#92;n&#92;n**Note:** Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in `Azure &gt; Redis &gt; Redis Cache &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n

Azure > Redis > Redis Cache > Discovery

Determine the firewall settings required for `Azure &gt; Redis &gt; Redis Cache`.&#92;n&#92;nAzure Cache for Redis supports firewall rules to control access to your Redis Cache. Firewall rules specify which IP address ranges are allowed to connect to the cache, enabling you to secure access from specific internet-based services and on-premises networks.&#92;n

Azure > Redis > Redis Cache > Firewall

Azure > Redis > Redis Cache > Firewall > IP Ranges

Configure firewall IP address range checking. This control defines whether&#92;nto verify the firewall IP address ranges are approved, as well as the&#92;nsubsequent action to take on unapproved items. Rules for all `Approved`&#92;npolicies will be compiled in `Approved &gt; Compiled Rules` and then&#92;nevaluated.&#92;nIf set to `Enforce: Delete unapproved`, any unapproved IP address ranges&#92;nwill be deleted from the firewall.&#92;n

Azure > Redis > Redis Cache > Firewall > IP Ranges > Approved > Compiled Rules

Azure > Redis > Redis Cache > Firewall > IP Ranges > Approved

Configure firewall IP address range checking. This control defines whether to verify the firewall IP address ranges are required, as well as the subsequent action to take on required items.&#92;n&#92;nIf set to `Enforce: Required &gt; Items`, the required IP address ranges will be added to the firewall.&#92;n

Azure > Redis > Redis Cache > Firewall > IP Ranges > Required > Items

Azure > Redis > Redis Cache > Firewall > IP Ranges > Required

Take an action when an Azure Redis redis cache tags is not updated based on the `Azure &gt; Redis &gt; Redis Cache &gt; Tags &gt; *` policies.&#92;n&#92;nIf the resource is not updated with the tags defined in `Azure &gt; Redis &gt; Redis Cache &gt; Tags &gt; Template`, this control raises an alarm and takes the defined enforcement action.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

Azure > Redis > Redis Cache > Tags > Template

Azure > Redis > Redis Cache > Tags

Invalid - prefix must be smaller than or equal to 30.

firewallIp

firewallIpRange

rule1

firewallIpRangeWithRuleName

redis

redisAka

test0001

redisCache

redisCacheAka

redisCacheId

redisCacheIdentity

redisCacheName

redisCacheProperties

ruleName

azure-redis

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermissions for Azure Redis that is used as input to the control that manages&#92;nthe IAM stack.&#92;n

Azure > Turbot > Permissions > Compiled > Service Permissions

Azure > Subscription

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

A calculated policy that Guardrails uses to create a compiled list of ALL&#92;npermission levels for Azure Redis that is used as input to the&#92;nstack that manages the Guardrails IAM permissions objects.&#92;n

Azure > Turbot > Permissions > Compiled > Levels

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

A list of Azure regions in which Azure Redis resources are allowed for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Redis resources&#39; Allowed &gt; Regions policies.&#92;n

Azure > Redis

Azure > Redis > Allowed Regions [Default]

A list of Azure regions in which Azure Redis resources are approved for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Redis resources&#39; Approved &gt; Regions policies.&#92;n

Azure > Redis > Approved Regions [Default]

Determine the action to take when an Azure Redis redis cache, based on the `Azure &gt; Redis &gt; Redis Cache &gt; Active &gt; *` policies.&#92;n&#92;nThe control determines whether the resource is in active use, and if not,&#92;nhas the ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Redis &gt; Redis Cache &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note:** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The age after which the Azure Redis redis cache&#92;nis no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Redis &gt; Redis Cache &gt; Active &gt; *`),&#92;nraises an alarm, and takes the defined enforcement action. Each Active&#92;nsub-policy can calculate a status of active, inactive or skipped. Generally,&#92;nif the resource appears to be Active for any reason it will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the resource appears to be Unapproved&#92;nfor any reason it will be considered Unapproved.&#92;n&#92;nSee [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active) for more information.&#92;n

The number of days since the Azure Redis redis cache was last modified before it is considered&#92;ninactive.&#92;n&#92;nThe [Active](https://turbot.com/guardrails/docs/concepts/guardrails/active)&#92;ncontrol determines whether the resource is in active use, and if not, has&#92;nthe ability to delete / cleanup the resource. When running an automated&#92;ncompliance environment, it&#39;s common to end up with a wide range of alarms&#92;nthat are difficult and time consuming to clear. The Active control brings&#92;nautomated, well-defined control to this process.&#92;n&#92;nThe Active control checks the status of all defined Active policies for the&#92;nresource (`Azure &gt; Redis &gt; Redis Cache &gt; Active &gt; *`), raises an alarm, and takes the defined enforcement&#92;naction. Each Active sub-policy can calculate a status of active, inactive&#92;nor skipped. Generally, if the resource appears to be Active for any reason&#92;nit will be considered Active.&#92;n&#92;n**Note** In contrast with Approved, where if the&#92;nresource appears to be Unapproved for any reason it will be considered&#92;nUnapproved.&#92;n

This policy serves as a hierarchical parent for more specific Allowed policies, such as region-based policies and custom rule-based policies.&#92;n

Determine the action to take when an Azure Redis redis cache is not allowed based on custom rules.&#92;n&#92;nThe `Allowed &gt; Custom` control checks if the redis cache is allowed based on the `Allowed &gt; Custom &gt; *` policies. If the redis cache is not allowed, the control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete if not allowed and resource is new`, the control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

Determine whether the Azure Redis redis cache is allowed to exist based on custom rules.&#92;n&#92;nThis policy will be evaluated by the `Allowed &gt; Custom` control. If an Azure Redis redis cache is not allowed, it will be subject to the action specified in the `Allowed &gt; Custom` policy.&#92;n&#92;n**Note**: The policy value must be a string with a value of `Allowed`, `Not allowed` or `Skip`, or in the form of YAML objects. The object(s) must contain the key `result` with its value as `Allowed` or `Not allowed`. A custom title and message can also be added using the keys `title` and `message` respectively.&#92;n

string

Determine the action to take when an Azure Redis redis cache is created in a region that is not allowed.&#92;n&#92;nThe `Allowed &gt; Region` control checks if the redis cache is created in an allowed region based on the `Allowed &gt; Region &gt; *` policies. If the redis cache is created in a region that is not in the allowed list, the control raises an alarm and takes the defined enforcement action.&#92;n&#92;nFor any enforcement actions that specify `if new`, e.g., `Enforce: Delete if region not allowed and resource is new`, the control will only take the enforcement actions for resources created within the last 60 minutes.&#92;n

A list of Azure regions in which Azure Redis redis caches are allowed for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and &#39;?&#39; wildcard characters.&#92;n&#92;nThis policy will be evaluated by the `Allowed &gt; Region` control. If an Azure Redis redis cache is created in a region that is not in the allowed list, it will be subject to the action specified in the `Allowed &gt; Region` policy.&#92;n

Configure whether to record and synchronize details for the Azure Redis redis cache into the CMDB.&#92;n&#92;nThe [CMDB](https://turbot.com/guardrails/docs/concepts/guardrails/cmdb) control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.&#92;nAll policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to **&quot;Enforce: Enabled&quot;**.&#92;n&#92;nIf 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.&#92;n&#92;nTo cleanup resources and stop tracking changes, set this policy to **&quot;Enforce: Disabled&quot;**.&#92;n&#92;nCMDB controls also use the Regions policy associated with the resource. If region is not in `Azure &gt; Redis &gt; Redis Cache &gt; Regions` policy, the CMDB control will delete the resource from the CMDB.&#92;n&#92;n(**Note**: Setting CMDB to **&quot;Skip&quot;** will also pause these changes.)&#92;n

Configure the firewall settings required for Azure &gt; Redis &gt; Redis Cache.&#92;n&#92;nAzure Cache for Redis supports firewall rules to control access to your Redis Cache.&#92;nFirewall rules specify which IP address ranges are allowed to connect to the cache,&#92;nenabling you to secure access from specific internet-based services and on-premises networks.&#92;n

Azure > Redis > Redis Cache > Firewall > IP Ranges > Approved > IP Addresses

Azure > Redis > Redis Cache > Firewall > IP Ranges > Approved > Rules

Configure firewall IP address range checking. This policy defines whether&#92;nto verify the firewall IP address ranges are approved, as well as the&#92;nsubsequent action to take on unapproved items. Rules for all `Approved`&#92;npolicies will be compiled in `Approved &gt; Compiled Rules` and then&#92;nevaluated.&#92;n&#92;nIf set to `Enforce: Delete unapproved`, any unapproved IP address ranges&#92;nwill be deleted from the firewall.&#92;n

A read-only Object Control List (OCL) to approve or reject IP addresses&#92;nfor a Redis Cache firewall. This list is compiled from specified approved IP addresses&#92;nand additional filtering rules.&#92;n&#92;nThis policy is generated by Guardrails and is designed to ensure that only&#92;napproved IP addresses are allowed access, aligning with security and compliance standards.&#92;n

Configure Redis Cache to allow access from specific internet IP addresses.&#92;nThis configuration grants access to specific internet-based services and on-premises networks,&#92;nand blocks general internet traffic.&#92;n&#92;nProvide allowed internet IP addresses in the form of individual startIpAddress and endIpAddress like in the below example.&#92;n&#92;nExample:&#92;n  - startIpAddress: 203.0.113.5 &lt;br /&gt;&#92;n    endIpAddress: 203.0.113.5&#92;n

An Object Control List (OCL) with a list of filter rules&#92;nto approve or reject IP ranges for a Redis Cache firewall.&#92;n&#92;nNote that the Approved control does not operate directly from this policy,&#92;nbut from the `Approved &gt; Compiled Rules`. The rules are processed in order,&#92;nand any built-in Guardrails rules will appear first in the list of compiled&#92;nrules.&#92;n

Configure Redis Cache to allow access from specific public internet IP address ranges. This policy grants access to approved internet address ranges or individual IP addresses and blocks unapproved internet traffic.&#92;n&#92;nIf set to `Enforce: Required &gt; Items`, this policy will grant access to the IP ranges in Required &gt; Items.&#92;n

Configure Redis Cache to allow access from specific internet IP addresses.&#92;nThis configuration grants access to specific internet-based services and on-premises networks, and blocks general internet traffic.&#92;n&#92;nProvide allowed internet IP addresses in the form of individual startIpAddress and endIpAddress like in the below example.&#92;n&#92;nExample:&#92;n  - startIpAddress: 203.0.113.5 &lt;br /&gt;&#92;n    endIpAddress: 203.0.113.5 &lt;br /&gt;&#92;n    name: AllowMyOfficeIP&#92;n

AllowMyOfficeIP

A list of Azure regions in which Azure Redis redis caches are supported for use.&#92;n&#92;nAny redis caches in a region not listed here will not be recorded in CMDB.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n

Determine the action to take when an Azure Redis redis cache tags are not updated based on the `Azure &gt; Redis &gt; Redis Cache &gt; Tags &gt; *` policies.&#92;n&#92;nThe control ensure Azure Redis redis cache tags include tags defined in `Azure &gt; Redis &gt; Redis Cache &gt; Tags &gt; Template`.&#92;n&#92;nTags not defined in Redis Cache Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

The template is used to generate the keys and values for Azure Redis redis cache.&#92;n&#92;nTags not defined in Redis Cache Tags Template will not be modified or deleted. Setting a tag value to `undefined` will result in the tag being deleted.&#92;n&#92;nSee [Tags](https://turbot.com/guardrails/docs/concepts/guardrails/tagging) for more information.&#92;n

The Event Grid event pattern used by the Azure Redis module to specify&#92;nwhich events to forward to the Guardrails Event Handlers [Event Grid].&#92;n&#92;nThis policy automatically generates operation filters based on which&#92;nresource types have CMDB enabled. Only enabled resource types will&#92;nhave their events forwarded to Guardrails.&#92;n

Azure > Turbot > Event Handlers [Event Grid] > Custom Event Patterns

Azure > Turbot > Event Handlers [Event Grid] > Custom Event Patterns > @turbot/azure-redis

Azure > Redis > Enabled

Azure > Redis > Permissions > Levels

Configure whether permissions policies are in effect for Azure Redis&#92;nThis setting does not affect Subscription level permissions (Azure/Admin, Azure/Owner, etc)&#92;n

Azure > Redis > Permissions

Azure > Redis > Permissions > Levels > Modifiers

Define the permissions levels that can be used to grant access to Storage an&#92;nAzure Subscription.  Permissions levels defined will appear in the UI to assign&#92;naccess to Guardrails users.&#92;n

A map of Azure API to Guardrails Permission Level used to customize Guardrails&#39;&#92;nstandard permissions. You can add, remove or redefine the mapping of&#92;nAzure API operations to Guardrails permissions levels here.&#92;n&#92;n```&#92;nexample:&#92;n  - &quot;Microsoft.Redis/Redis/delete&quot;: operator&#92;n  - &quot;Microsoft.Redis/Redis/write&quot;: admin&#92;n  - &quot;Microsoft.Redis/Redis/read&quot;: readonly&#92;n```&#92;n

A list of Azure regions in which Azure Redis resources are supported for use.&#92;n&#92;nThe expected format is an array of regions names. You may use the &#39;*&#39; and&#92;n&#39;?&#39; wildcard characters.&#92;n&#92;nThis policy is the default value for all Azure Redis resources&#39; Regions policies.&#92;n

Azure > Redis > Regions

A template used to generate the keys and values for Azure Redis resources.&#92;n&#92;nBy default, all Redis resource Tags &gt; Template policies will use this value.&#92;n

Mod: azure-redis

Recommended Version

Resource Types

Controls

IAM Roles

Policies