Decoy · Device
Redis decoy
Open Redis servers are a well-known way in, and scanners look for them all the time. This decoy poses as cache-prod01, with Redis on its usual port and SSH.
What it emulates
Poses as: Redis cache server.
It answers the first Redis command with "PONG" and records what each visitor sends. For the full Redis emulation, with recorded passwords and commands, use the Linux server or AI agent server decoy.
- SSH 22
Records every username, password and key fingerprint tried, then refuses them. Disconnects after six tries.
- Redis 6379
Answers "PONG" and records the first bytes each visitor sends.
What it catches
Every touch, explained in plain English.
Each event gets a plain-English explanation. Related events from the same source become one incident with a recommended action.
- Scanners looking for open Redis servers
- SSH password guessing
- Port scans across the server
MITRE ATT&CK
Techniques come from a fixed table, not from AI, so the same activity always maps the same way.
- T1046Network Service Discovery
- T1110Brute Force
Incidents go to email, Slack, your SIEM or a signed webhook. Kandaro and your SOC
Safe by design
Built to be attacked. Never a way in.
A decoy only listens and answers with fake data. It never runs code and only connects out to Kandaro, so it can never become a way into your network.
It runs nothing
The sensor has no way to run a command, load code or update itself. Every command an intruder types gets a fake text answer.
It connects to one place only
Its only outbound connection is HTTPS to the Kandaro API address set at install time. Nothing Kandaro sends can change that address.
Kandaro can only send it settings
Which decoy to imitate, which services to turn off, which addresses to ignore. There is no field for code, files, commands or updates.
It holds no real secrets
Passwords, keys and records it shows are fake. Its only credential is its own key, which can send events for your organisation and nothing more.
It cannot be used to attack others
It never forwards traffic, never fetches a URL and never serves scripts or programs. Its only UDP replies (SNMP) are rate-limited per address.
Non-root, read-only container with signed images. How we secure sensors
Where to put it
Place it where an intruder will look.
Put it in the server or application network, next to your real caches.
Installs in about a minute with Docker, Kubernetes, Ansible, a VM or a Raspberry Pi, and needs outbound HTTPS only. Deployment guide · Where to put your first decoys
FAQ
Redis decoy questions
Does it store any data?
Is it safe to run on my network?
Related decoys
Pair it with these.
- device
Linux server
Ubuntu database and web server
The classic lateral-movement target: SSH, a web admin, MySQL, Redis and MongoDB.
SSH 22HTTP 80HTTPS 443MySQL 3306Redis 6379+3 - device
MongoDB
MongoDB database server
A MongoDB server that serves endless fake documents to anyone pulling data.
SSH 22MongoDB 27017 - device
Elasticsearch
Elasticsearch cluster
A search cluster that looks full of data. Catches index listing and credential guessing.
SSH 22Elasticsearch 9200ES transport 9300
Put this decoy on your network today.
Start a 14-day trial of Kandaro Deception. Your first decoy is running in about a minute.
Card required · cancel before day 14 and pay nothing