/

/redis-security

Redis security guidance covering authentication (requirepass and ACL users), TLS, ACL-based least-privilege access control, restricting network exposure via bind and protected-mode, firewall rules, and disabling dangerous commands. Use when deploying Redis to production, defining ACL users for an application, configuring TLS connections, locking down a Redis instance behind a firewall, or auditing a Redis deployment for security hardening.

4 files
6.9 KB
MIT
Updated 4 months ago
GitHub
1 warning

Ask your Agent

Use this Skill: https://skilld.dev/gh/redis/agent-skills/redis-security

This session only. Nothing lands on disk.

referencesacls.md

862 B raw

≈216 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Use ACLs for Fine-Grained Access Control

Create users with only the permissions they need (principle of least privilege).

Correct: Create specific users with limited permissions.

# Read-only user for cache access
ACL SETUSER app_readonly on >password ~cache:* +get +mget +scan

# Writer that can't run dangerous commands
ACL SETUSER app_writer on >password ~* +@all -@dangerous

# Admin user (use sparingly)
ACL SETUSER admin on >strong-password ~* +@all

Incorrect: Using the default user for everything.

# Bad: Single password for all access
requirepass shared-password

ACL categories:

@read - Read commands
@write - Write commands
@dangerous - Commands like FLUSHALL, DEBUG
@admin - Administrative commands

Reference: Redis ACL

Source: SKILL.md on GitHub

Third-party checks

1 warning1mo3 checks · Risk SAFE

Gen Agent Trust Hub1mo
This skill provides standard security hardening guidance for Redis deployments, including instructions for authentication, TLS configuration, ACL management, and network security. No malicious patterns were detected.
Socket1mo
No alerts
Snyk1mo
Risk: MEDIUM · 1 issue

Provenance

Signed by skilld at 17faa8d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 4 months ago

Capability

metadata: { "author": "Redis, Inc.", "version": "0.1.0" }

Topics

redis
authentication
acl
tls
network-security
firewall
access-control
production
hardening

What it does

Configures Redis authentication via requirepass and ACL users, enables TLS encryption, restricts network exposure with bind and protected-mode, and disables dangerous commands. Apply this skill when deploying Redis to production, setting up per-application credentials, or auditing an instance against security hardening requirements.

Generated from the current SKILL.md.

Frequently asked

Does this skill cover both authentication and network isolation?

Yes. The skill covers authentication (requirepass and ACL users), TLS encryption, network binding, protected-mode, firewall rules, and command disabling. All three layers are recommended together to avoid exploitable gaps.

Can I use this skill to set up ACL users for different applications?

Yes. The skill includes examples of creating dedicated ACL users with least-privilege access — e.g., read-only cache users, writers without dangerous commands, and admin users. Each user can be restricted to specific command categories and key patterns.

Does this cover TLS/SSL configuration?

Yes. The skill includes redis.conf settings for tls-port, tls-cert-file, and tls-key-file, plus a Python client example using SSL connections.

What commands can be disabled or renamed?

The skill covers disabling or renaming dangerous commands like FLUSHALL, DEBUG, KEYS, and CONFIG using the rename-command directive in redis.conf.

Is this skill for development or production only?

Primarily production. The skill notes that a single shared password with the default user is acceptable for development, but recommends ACL users and full hardening for production deployments.

Generated from the current SKILL.md. These answers refresh after source changes.