Canary by Thinkst
Order, configure and deploy your Canaries throughout your network. Make one a Windows file server, another a router, throw in a few Linux web servers while you're at it. Each one hosts realistic services and look and acts like its namesake.
Then you wait. Your Canaries run in the background, waiting for intruders.
Attackers prowling a target network look for juicy content. They browse Active Directory for file servers and explore file shares looking for documents, try default passwords against network devices and web services, and scan for open services across the network.
When they encounter a Canary, the services on offer are designed to solicit further investigation, at which point your Canary notifies you of the incident.
Each customer gets their own management console, on which alerts can be reviewed, notifications configured and managed. Your Canaries constantly report in and provide an up to the minute report on their status.
When an incident occurs, we alert you via email or text message as you prefer. Manage your alerts in the console, where you can get more information on what triggered the incident.
Isn't this just a honeypot?
Yes and No.
Honeypots are a great idea. Everyone knows this, so why is almost nobody running them on internal networks? Simple: because with all the network problems we have, nobody needs one more machine to administer and worry about. We know the benefits that honeypots can bring but the cost and effort of deployment always drop honeypots to the bottom of the list of things to do.
Canary changes this. The Canaries can be deployed in minutes (even on complex networks), giving you all of the benefits without the admin downsides.
How easily can these be deployed?
It usually takes less than 5 minutes from unboxing your Canary, to have it ready for action on your network. With just a few clicks, you'll have a high interaction honeypot, and be able to track who’s browsing shares for PDF documents, trying to log into a NAS, or portscanning your network.
How do they communicate with the console?
Canaries are deployed inside your network and communicate with the hosted console through DNS. This means the only network access your Canary needs is to a DNS server that's capable of external queries, which is much less work than configuring border firewall rules for each device.
Okay, you have 2 minutes. How does this work?
Simply choose a profile for the Canary device (such as a Window box, brand name router, or Linux server). If you want, you can further tweak the services your Canary runs. Perhaps you need a specific IIS server version or OpenSSH, or a Windows file share with real files constructed according to your own naming scheme (say, 2016-tenders.xls). Lastly, register your Canary with our hosted console for monitoring and notifications.
Attackers who have breached your network, malicious insiders and other adversaries make themselves known by accessing your Canary. There's little room for doubt. If someone browses a file share and opened a sensitive-looking document on your Canary (\\fin_srv_02\Planning\2016_forecasts.xls) you'll immediately be alerted to the problem.
You possibly already do have a problem, you might just not know it. Canary changes that.
So, Canaries are sensors. Do you use them to do machine learning to do anomaly detection?
No. Canary doesn't do anomaly detection (with machine learning or otherwise) by learning to detect malicious behavior in day-to-day activity. The Canary triggers are incontrovertibly simple: if someone is accessing your lure-files, or brute-forcing your fake internal ssh server, then you have a problem. Canary uses deceptively simple, but high-quality markers of trouble on your network.
Can't I do this myself using honeyd, kippo, or <insert project here>?
You could certainly setup honeypots but, the truth is, most haven't. Why? Two reasons as far as we can tell: most projects have limited protocol support meaning you have to run multiple honeypots to cover a range of common protocols, and monitoring and notifications across multiple honeypots quickly becomes tricky especially if you want to have many honeypots scattered around your network.
Canary makes this easy; we have multiple protocols supported out-of-the-box, and our hosted console gives you effortless monitoring and notifications.
What if an attacker DoS'es the device or compromises it?
If your Canary can get off just one alert (and it really should) then your console far away is going to log and alert on this. Whatever happens to the Canary after that won't matter since it stores nothing of value.
What if the attacker identifies the device as a Canary? Won't they simply avoid it?
Identification will require active interrogation of the devices, and we detect common methods for fingerprinting then alert. After that, even if the attacker correctly identifies a Canary, you know they're looking and can investigate further.