redis · cmilesb · May 16, 2025 · May 16, 2025 · May 16, 2025
diff --git a/content/develop/tools/insight/release-notes/v.2.56.0.md b/content/develop/tools/insight/release-notes/v.2.56.0.md
@@ -10,7 +10,7 @@ weight: 1
 This is the General Availability (GA) release of Redis Insight 2.56.
 
 ### Highlights
-- Seamlessly sign in to your Redis Cloud account using the new [SAML single sign-on](https://redis.io/docs/latest/operate/rc/security/access-control/saml-sso/) feature, now available alongside existing social logins via Google and GitHub. This integration lets you connect to all your Redis Cloud databases in several clicks.
+- Seamlessly sign in to your Redis Cloud account using the new [SAML single sign-on](https://redis.io/docs/latest/operate/rc/security/console-access-control/saml-sso/) feature, now available alongside existing social logins via Google and GitHub. This integration lets you connect to all your Redis Cloud databases in several clicks.
 - Start your Redis journey faster with a sample data set automatically loaded for new free Redis Cloud databases created directly within Redis Insight.
 - Focus on what matters most:
   - Hide or show [TTL for individual hash fields](https://redis.io/docs/latest/develop/data-types/hashes/?utm_source=redisinsight&utm_medium=release_notes&utm_campaign=2.52#field-expiration) to create a cleaner, more efficient workspace.
@@ -21,7 +21,7 @@ This is the General Availability (GA) release of Redis Insight 2.56.
 ### Details
 
 **Features and improvements**
-- [#3727](https://github.com/RedisInsight/RedisInsight/pull/3727) Seamlessly sign in to your Redis Cloud account using the new [SAML single sign-on](https://redis.io/docs/latest/operate/rc/security/access-control/saml-sso/) feature, now available alongside existing social logins via Google and GitHub. This integration lets you connect to all your Redis Cloud databases in several clicks. Before setting up SAML in Redis Cloud, you must first [verify domain ownership](https://redis.io/docs/latest/operate/rc/security/access-control/saml-sso/?utm_source=redisinsight&utm_medium=repository&utm_campaign=release_notes) for any domains associated with your SAML setup. Note that integration with Redis Cloud is currently available only in the desktop version of Redis Insight.
+- [#3727](https://github.com/RedisInsight/RedisInsight/pull/3727) Seamlessly sign in to your Redis Cloud account using the new [SAML single sign-on](https://redis.io/docs/latest/operate/rc/security/console-access-control/saml-sso/) feature, now available alongside existing social logins via Google and GitHub. This integration lets you connect to all your Redis Cloud databases in several clicks. Before setting up SAML in Redis Cloud, you must first [verify domain ownership](https://redis.io/docs/latest/operate/rc/security/console-access-control/saml-sso/?utm_source=redisinsight&utm_medium=repository&utm_campaign=release_notes) for any domains associated with your SAML setup. Note that integration with Redis Cloud is currently available only in the desktop version of Redis Insight.
 - [#3659](https://github.com/RedisInsight/RedisInsight/pull/3659) Start your Redis journey faster with a sample data set automatically loaded for new free Redis Cloud databases created directly within Redis Insight. This feature ensures a smoother setup process, allowing you to dive into your data immediately.
 - [#3624](https://github.com/RedisInsight/RedisInsight/pull/3624) The ability to hide or show [TTL for individual hash fields](https://redis.io/docs/latest/develop/data-types/hashes/?utm_source=redisinsight&utm_medium=release_notes&utm_campaign=2.52#field-expiration) to create a cleaner, more efficient workspace. This optimization complements the highly requested hash field expiration feature introduced in the [first release candidate of Redis 7.4](https://github.com/redis-stack/redis-stack/releases/tag/v7.4.0-v0).
 - [#3701](https://github.com/RedisInsight/RedisInsight/pull/3701) Enhanced vector data representation with updated 32-bit and 64-bit vector formatters in the Browser. These changes ensure that vector formatters are applied only to data containing unprintable values when converted to UTF-8, providing a clearer and more accurate view of your data.

diff --git a/content/embeds/rc-vpc-peering-cidr-list.md b/content/embeds/rc-vpc-peering-cidr-list.md
@@ -1 +1 @@
-If you've enabled the database's [CIDR allow list]({{< relref "/operate/rc/security/cidr-whitelist" >}}), you must also [add the VPC peered IP addresses to the CIDR allow list]({{< relref "/operate/rc/security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.
+If you've enabled the database's [CIDR allow list]({{< relref "/operate/rc/security/network-data-security/cidr-whitelist" >}}), you must also [add the VPC peered IP addresses to the CIDR allow list]({{< relref "/operate/rc/security/network-data-security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.
diff --git a/content/glossary/_index.md b/content/glossary/_index.md
@@ -18,7 +18,7 @@ aliases: /glossary/
 {{%definition "access control list (ACL)"%}}
 Allows you to manage permissions based on key patterns.
 
-More info: [redis.io/operate/oss_and_stack/management/security/acl]({{< relref "/operate/oss_and_stack/management/security/acl" >}}); [ACL wikipedia](https://en.wikipedia.org/wiki/Access-control_list); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Update database ACLs]({{<relref "/operate/rs/security/access-control/ldap/update-database-acls">}}); [Role-based access control]({{<relref "/operate/rc/security/access-control/data-access-control/role-based-access-control">}})
+More info: [redis.io/operate/oss_and_stack/management/security/acl]({{< relref "/operate/oss_and_stack/management/security/acl" >}}); [ACL wikipedia](https://en.wikipedia.org/wiki/Access-control_list); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Update database ACLs]({{<relref "/operate/rs/security/access-control/ldap/update-database-acls">}}); [Role-based access control]({{<relref "/operate/rc/security/data-access-control/role-based-access-control">}})
 {{%/definition%}}
 
 <a name="active-active"></a>
@@ -64,7 +64,7 @@ More info: [Causal consistency wikipedia](https://en.wikipedia.org/wiki/Causal_c
 {{%definition "CIDR allowlist"%}}
 Classless Inter-Domain Routing (CIDR) is a method to allocate and route IP addresses. A CIDR allowlist defines a range of IP addresses and permits connections to them.
 
-More info: [CIDR wikipedia](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing), [Configure CIDR allowlist]({{<relref "/operate/rc/security/cidr-whitelist">}})
+More info: [CIDR wikipedia](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing), [Configure CIDR allowlist]({{<relref "/operate/rc/security/network-data-security/cidr-whitelist">}})
 {{%/definition%}}
 
 {{%definition "concurrent writes"%}}
@@ -212,7 +212,7 @@ More info: [multicast DNS wikipedia](https://en.wikipedia.org/wiki/Multicast_DNS
 {{%definition "multi-factor authentication (MFA)"%}}
 Method of authenticating users with pieces of evidence of the user's identity. When MFA is enabled on Redis Cloud, users must enter their username, password, and an authentication code when logging in.
 
-More info: [Multi-factor authentication]({{<relref "/operate/rc/security/access-control/multi-factor-authentication">}})
+More info: [Multi-factor authentication]({{<relref "/operate/rc/security/console-access-control/multi-factor-authentication">}})
 {{%/definition%}}
 
 {{%definition "multi-primary replication"%}}
@@ -349,7 +349,7 @@ More info: [Database replication]({{<relref "/operate/rs/databases/durability-ha
 {{%definition "role-based access control (RBAC)"%}}
 A security approach that restricts system access to authorized users.
 
-More info: [RBAC wikipedia](https://en.wikipedia.org/wiki/Role-based_access_control); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Role-based access control]({{<relref "/operate/rc/security/access-control/data-access-control/role-based-access-control">}})
+More info: [RBAC wikipedia](https://en.wikipedia.org/wiki/Role-based_access_control); [Database access control]({{<relref "/operate/rs/security/access-control">}}); [Role-based access control]({{<relref "/operate/rc/security/data-access-control/role-based-access-control">}})
 {{%/definition%}}
 
 ## S {#letter-s}
@@ -395,13 +395,13 @@ A key that is logically deleted but stays in memory until it is collected by the
 {{%definition "Transport Layer Security (TLS)"%}}
 Protocols that provide communications security over a computer network.
 
-More info: [TLS wikipedia](https://en.wikipedia.org/wiki/Transport_Layer_Security), [Cloud database TLS]({{<relref "/operate/rc/security/database-security/tls-ssl">}}), [Redis Enterprise TLS]({{<relref "/operate/rs/security/encryption/tls">}})
+More info: [TLS wikipedia](https://en.wikipedia.org/wiki/Transport_Layer_Security), [Cloud database TLS]({{<relref "/operate/rc/security/network-data-security/tls-ssl">}}), [Redis Enterprise TLS]({{<relref "/operate/rs/security/encryption/tls">}})
 {{%/definition%}}
 
 {{%definition "VPC peering"%}}
 Networking connection between two VPCs that enables you to route traffic between them using private IP addresses. Instances in either VPC can communicate with each other as if they are within the same network.
 
-More info: [VPC wikipedia](https://en.wikipedia.org/wiki/Virtual_private_cloud), [Enable VPC peering]({{<relref "/operate/rc/security/vpc-peering">}})
+More info: [VPC wikipedia](https://en.wikipedia.org/wiki/Virtual_private_cloud), [Enable VPC peering]({{<relref "/operate/rc/security/network-data-security/connect-private-endpoint/vpc-peering">}})
 {{%/definition%}}
 
 

diff --git a/content/integrate/amazon-bedrock/set-up-redis.md b/content/integrate/amazon-bedrock/set-up-redis.md
@@ -111,7 +111,7 @@ To set up a Redis Cloud instance for Bedrock, you need to:
 
 ## Enable TLS and get certificates {#get-certs}
 
-For your database to be fully secure, you must enable [Transport Layer Security (TLS)]({{< relref "/operate/rc/security/database-security/tls-ssl#enable-tls" >}}) for your database with client authentication.
+For your database to be fully secure, you must enable [Transport Layer Security (TLS)]({{< relref "/operate/rc/security/network-data-security/tls-ssl#enable-tls" >}}) for your database with client authentication.
 
 1. Select **Databases** from the [Redis Cloud console](https://cloud.redis.io/) menu and then select your database from the list.
 
@@ -165,7 +165,7 @@ In the [AWS Management Console](https://console.aws.amazon.com/), use the **Serv
 
 - `username`: Database username
 - `password`: Database password
-- `serverCertificate`: Contents of the [server certificate]({{< relref "/operate/rc/security/database-security/tls-ssl#download-certificates" >}}) (`redis_ca.pem`)
+- `serverCertificate`: Contents of the [server certificate]({{< relref "/operate/rc/security/network-data-security/tls-ssl#download-certificates" >}}) (`redis_ca.pem`)
 - `clientCertificate`: Contents of the client certificate (`redis_user.crt`)
 - `clientPrivateKey`: Contents of the client private key (`redis_user_private.key`)
 

diff --git a/content/integrate/confluent-with-redis-cloud/_index.md b/content/integrate/confluent-with-redis-cloud/_index.md
@@ -22,13 +22,13 @@ Before you add the Redis Sink Confluent connector to your Confluent Cloud cluste
 
 1. [Create a database]({{< relref "/operate/rc/databases/create-database" >}}) in the same region as your Confluent Cloud cluster.
 
-1. If you decide to [enable Transport Layer Security (TLS)]({{< relref "/operate/rc/security/database-security/tls-ssl" >}}) for your Redis database, [download the server certificate]({{< relref "/operate/rc/security/database-security/tls-ssl#download-certificates" >}}) from the Redis Cloud console and [encode it](#encode-server-certificate) to be used with Confluent Cloud.
+1. If you decide to [enable Transport Layer Security (TLS)]({{< relref "/operate/rc/security/network-data-security/tls-ssl" >}}) for your Redis database, [download the server certificate]({{< relref "/operate/rc/security/network-data-security/tls-ssl#download-certificates" >}}) from the Redis Cloud console and [encode it](#encode-server-certificate) to be used with Confluent Cloud.
 
 1. Ensure you meet the prerequisites in the [Redis Sink connector documentation](https://docs.confluent.io/cloud/current/connectors/cc-redis-sink.html#quick-start) to set up your Redis Sink with Confluent Cloud. 
 
 ### Encode server certificate
 
-If you decide to enable Transport Layer Security (TLS) for your database, you will need to encode the [server certificate]({{< relref "/operate/rc/security/database-security/tls-ssl#download-certificates" >}}) (`redis_ca.pem`) for use as the Confluent Cloud Truststore file. To do this:
+If you decide to enable Transport Layer Security (TLS) for your database, you will need to encode the [server certificate]({{< relref "/operate/rc/security/network-data-security/tls-ssl#download-certificates" >}}) (`redis_ca.pem`) for use as the Confluent Cloud Truststore file. To do this:
 
 1. Use a base64 utility to encode `redis_ca.pem` into base64 in a new file. For example, using the [`base64` command-line utility](https://linux.die.net/man/1/base64):
 
@@ -65,8 +65,8 @@ To add the Redis Sink connector to your Confluent Cloud environment from the Red
     - **Redis hostname**: The Public endpoint of your database, without the port number. This can be found in the [Redis Cloud console](https://cloud.redis.io/) from the database list or from the **General** section of the **Configuration** tab for the source database.
     - **Redis port number**: The database's port. This is the number at the end of your database's Public endpoint.
     - **Redis database index**: Set this to 0 for a Redis Cloud database.
-    - **Redis server password**: Enter the database password. If you have not set your own database user and password, use the [default user password]({{< relref "/operate/rc/security/access-control/data-access-control/default-user" >}}), which appears in the **Security** section of the **Configuration** tab of the database details screen.
-    - **SSL mode**: Set depending on what type of [TLS authentication]({{< relref "/operate/rc/security/database-security/tls-ssl" >}}) is set for your database.
+    - **Redis server password**: Enter the database password. If you have not set your own database user and password, use the [default user password]({{< relref "/operate/rc/security/data-access-control/default-user" >}}), which appears in the **Security** section of the **Configuration** tab of the database details screen.
+    - **SSL mode**: Set depending on what type of [TLS authentication]({{< relref "/operate/rc/security/network-data-security/tls-ssl" >}}) is set for your database.
         - If TLS authentication is turned off, select **disabled**.
         - If TLS authentication is turned on, select **server**. 
     - **Trustore file**: If the **SSL mode** is set to **server**, upload the truststore file created when you [encoded the server certificate](#encode-server-certificate).

diff --git a/content/integrate/datadog-with-redis-cloud/_index.md b/content/integrate/datadog-with-redis-cloud/_index.md
@@ -42,7 +42,7 @@ Select 'Integrations' from the menu in the Datadog portal and then enter 'Redis'
 'Redis Cloud by Redis, Inc.'. Next click 'Install Integration' in the top-right corner of the overview page.
 
 If you have not already created a VPC between the Redis Cloud cluster and the network in which the machine hosting the 
-Datadog agent lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) 
+Datadog agent lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/network-data-security/connect-private-endpoint/vpc-peering/) 
 and follow the instructions for the cloud platform of your choice.
 
 Returning to the Datadog console, open the 'Configure' tab of the integration and follow the instructions for installing 

diff --git a/content/integrate/dynatrace-with-redis-cloud/_index.md b/content/integrate/dynatrace-with-redis-cloud/_index.md
@@ -39,7 +39,7 @@ another destination using remote writes. This will require a Prometheus installa
 Redis Cloud deployment.
 
 If you have not already created a VPC between the Redis Cloud cluster and the network in which the machine hosting 
-Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) 
+Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/network-data-security/connect-private-endpoint/vpc-peering/) 
 and follow the instructions for the cloud platform of your choice.
 
 

diff --git a/content/integrate/new-relic-with-redis-cloud/_index.md b/content/integrate/new-relic-with-redis-cloud/_index.md
@@ -40,7 +40,7 @@ another destination using remote writes. This will require a Prometheus installa
 Redis Cloud deployment.
 
 If you have not already created a VPC between the Redis Cloud cluster and the network in which the machine hosting 
-Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/vpc-peering/) 
+Prometheus lives you should do so now. Please visit [VPC Peering](https://redis.io/docs/latest/operate/rc/security/network-data-security/connect-private-endpoint/vpc-peering/) 
 and follow the instructions for the cloud platform of your choice.
 
 Finally, the Prometheus installation must be configured to pull metrics from Redis Cloud and write them to New Relic. There 

diff --git a/content/integrate/prometheus-with-redis-cloud/_index.md b/content/integrate/prometheus-with-redis-cloud/_index.md
@@ -23,7 +23,7 @@ You can use Prometheus and Grafana to collect and visualize your Redis Cloud met
 
 Redis Cloud exposes its metrics through a Prometheus endpoint. You can configure your Prometheus server to scrape metrics from your Redis Cloud subscription on port 8070.
 
-The Redis Cloud Prometheus endpoint is exposed on Redis Cloud's internal network. To access this network, enable [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}) or [Private Service Connect]({{< relref "/operate/rc/security/private-service-connect" >}}). Both options are only available with Redis Cloud Pro. You cannot use Prometheus and Grafana with Redis Cloud Essentials.
+The Redis Cloud Prometheus endpoint is exposed on Redis Cloud's internal network. To access this network, enable [VPC peering]({{< relref "/operate/rc/security/network-data-security/connect-private-endpoint/vpc-peering" >}}) or [Private Service Connect]({{< relref "/operate/rc/security/network-data-security/connect-private-endpoint/private-service-connect" >}}). Both options are only available with Redis Cloud Pro. You cannot use Prometheus and Grafana with Redis Cloud Essentials.
 
 For more information on how Prometheus communicates with Redis Enterprise clusters, see [Prometheus integration with Redis Enterprise Software]({{< relref "/integrate/prometheus-with-redis-enterprise/" >}}).
 
@@ -35,7 +35,7 @@ You can quickly set up Prometheus and Grafana for testing using the Prometheus a
 
 1. Create a [Redis Cloud Pro database]({{< relref "/operate/rc/databases/create-database/create-pro-database-new" >}}). 
 
-1. Set up [VPC peering]({{< relref "/operate/rc/security/vpc-peering" >}}).
+1. Set up [VPC peering]({{< relref "/operate/rc/security/network-data-security/connect-private-endpoint/vpc-peering" >}}).
 
 1. Extract the Prometheus endpoint from the private endpoint to your database. The private endpoint is in the [Redis Cloud console](https://cloud.redis.io/) under the [Configuration tab]({{< relref "/operate/rc/databases/view-edit-database#configuration-tab" >}}) of your database. The Prometheus endpoint is on port 8070 of the internal server.
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		If you've enabled the database's [CIDR allow list]({{< relref "/operate/rc/security/cidr-whitelist" >}}), you must also [add the VPC peered IP addresses to the CIDR allow list]({{< relref "/operate/rc/security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.
		If you've enabled the database's [CIDR allow list]({{< relref "/operate/rc/security/network-data-security/cidr-whitelist" >}}), you must also [add the VPC peered IP addresses to the CIDR allow list]({{< relref "/operate/rc/security/network-data-security/cidr-whitelist#define-cidr-allow-list" >}}) to connect to the database via the private endpoint.