Decoy · Device
SQL Server decoy
SQL Server is a common target in Windows networks. This decoy poses as SQL-PROD01, with the database port, the SQL Browser service and SSH.
What it emulates
Poses as: Microsoft SQL Server.
It records every connection and what each client sends. For full SQL Server emulation, which records the username and password, use the Windows file server decoy.
- SSH 22
Records every username, password and key fingerprint tried, then refuses them. Disconnects after six tries.
- SQL Server 1433
Accepts the connection and records the first bytes sent. It does not speak the protocol yet.
- SQL Browser 1434/udp
Records every packet that arrives. Never replies.
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.
- Connections to the database port
- SQL Browser queries that list instances
- 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 database network, next to your real SQL Servers.
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
SQL Server decoy questions
Does it hold any data?
Is it safe to run on my network?
Related decoys
Pair it with these.
- device
Windows file server
Windows file server
Shares, RDP, SQL Server and IIS: exactly what ransomware operators go looking for.
SMB 445NetBIOS 139RPC 135RDP 3389SQL Server 1433+4 - device
PostgreSQL
PostgreSQL database server
A database server on its usual port, plus SSH. Catches scans and password guessing.
SSH 22PostgreSQL 5432 - device
Active Directory DC
Active Directory domain controller
The ports of a domain controller. Catches scans and connections to LDAP, Kerberos and SMB.
LDAP 389LDAPS 636Kerberos 88/udpSMB 445RPC 135+1
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