---
name: rt-exploit-redis
description: "Redis security assessment skill for authorized exposure review, authentication, ACLs, TLS, command restrictions, sensitive cache-data handling, availability risk, and remediation."
---

# rt-exploit-redis - Redis Assessment

## Overview

Redis is often treated as internal-only infrastructure. Risk increases when it is exposed, unauthenticated, overprivileged, used for session data, or configured with unsafe persistence/command access.

## Prerequisites

- In-scope instances and environments.
- Safe test window.
- Permission to inspect configuration or use client-provided output.
- Rules for key inspection and sensitive cache data.

## Assessment Areas

| Area | Checks |
|---|---|
| Exposure | Public access, VPC rules, protected mode. |
| Authentication | AUTH/ACL users, default user state, shared passwords. |
| TLS | Encrypted transport and client verification. |
| Commands | Dangerous command availability and role restrictions. |
| Data | Session tokens, PII, credentials, excessive retention. |
| Persistence | RDB/AOF storage permissions and backups. |
| Monitoring | Auth failures, command anomalies, memory pressure. |

## Workflow

1. Confirm safe inspection boundaries.
2. Inventory exposure, auth, TLS, and Redis version.
3. Review ACL model and sensitive command access.
4. Inspect only approved keys or metadata samples.
5. Evaluate business impact: data exposure, session compromise, outage risk.
6. Recommend controls.

## Evidence

Use redacted config summaries, ACL summaries, key metadata, and screenshots. Do not dump full keyspaces.

## Remediation

- Private networking only.
- Enforce ACLs and disable default user where possible.
- Use TLS.
- Restrict dangerous commands.
- Avoid storing long-lived secrets.
- Secure persistence files and backups.
- Alert on auth failures and unusual command patterns.


## Finding Examples

| Finding | Severity Driver |
|---|---|
| Public Redis instance | Internet exposure and availability risk. |
| Default user with broad access | Privilege and data exposure risk. |
| Session tokens in cache | Account takeover potential. |
| No TLS | Credential interception risk. |

## Autodoc

```bash
python _rtexit/scripts/autodoc_engine.py log --skill rt-exploit-redis --phase exploitation --cmd "Redis posture review" --output "redacted cache risk summary"
```
