What problem does it solve? Production Redis instances are frequently breached because they run without authentication, use a single shared password, or are exposed to the public internet. This Skill provides concrete configuration guidance to close those gaps across authentication, access control, and network exposure. ## Core Features & Use Cases - Authentication and TLS setup: Configure requirepass or ACL users with TLS-encrypted connections, including redis-py and Jedis client examples. - ACL-based least privilege: Create dedicated users with scoped key patterns and command categories like @read, @write, and -@dangerous to bound the blast radius of leaked credentials. - Network lockdown: Bind to specific interfaces, keep protected-mode enabled, add firewall rules, and disable dangerous commands like FLUSHALL, DEBUG, and CONFIG. - Use Case: When deploying Redis to production or responding to a scanner finding about an exposed Redis instance, apply the three-layer checklist to authenticate clients, restrict commands per application, and limit network access to trusted subnets. ## Quick Start Ask the assistant to review your redis.conf and produce a hardened production configuration with ACL users, TLS, and firewall rules.
