Redis protected mode
What is Redis protected mode?
Redis protected mode, a default Redis has shipped since version 3.2.0, restricts an unauthenticated instance with no bind address set to loopback-only connections, per Redis's own security documentation. AdminKit's guide explains why Redis ships without a password by default, and what protected mode does and doesn't cover.
By AdminKit team, Netbase JSC · Updated
Protected mode is a safety feature Redis has enabled by default since version 3.2.0, intended to limit the damage of RESP’s lack of built-in authentication. When a Redis instance starts with no password set and a bind address that isn’t restricted to loopback, protected mode automatically refuses connections from any client that isn’t connecting from localhost, per Redis’s own security documentation, with protected-mode yes shipped as the default directly in Redis’s own redis.conf. It is not a substitute for setting a password with Redis’s AUTH mechanism or Access Control Lists — an administrator can disable protected mode explicitly, bind Redis to a public interface deliberately, or change the bind address without realizing the two settings interact, and any of those reintroduce the original no-password exposure. Managed providers reach the same conclusion: AWS’s ElastiCache documentation on the Redis AUTH command recommends requiring an auth token regardless, since protected mode’s loopback-only default is no substitute for actually requiring credentials on a production deployment. Because protected mode is a configuration default rather than a protocol-level control, whether it’s still active on a given instance has to be checked directly, not assumed.
Redis protected mode is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What does Redis protected mode do?
It automatically refuses connections from any client that isn't connecting from localhost, when a Redis instance starts with no password set and an unrestricted bind address.
Since which Redis version has protected mode been enabled by default?
Version 3.2.0.
Does protected mode replace setting a password?
No -- it's not a substitute for Redis's AUTH mechanism or Access Control Lists; an administrator can disable it or bind Redis to a public interface deliberately.
Why can protected mode silently stop protecting an instance?
Because it's a configuration default rather than a protocol-level control, so whether it's still active on a given instance has to be checked directly, not assumed.