In local networks, it is common for devices to send A record DNS requests on the local link or multicast addresses to find other devices on the network - this is a common fallback for devices if their defined DNS server doesn't have an IP for a local device's hostname. If a device exists on the local network that matches the hostname of the A record, that device will respond with it's IP address; allowing the requester to connect to it via the IP in the DNS response.
Spoofing or poisoning is an attack technique where an attacker sits on a local network and listens for local link/multicast DNS traffic (LLMNR, NBNS or mDNS). When the attacker sees some victim machine requesting the IP address for a hostname, the attacker would quickly respond with their own IP before the real machine can respond. The victim receives the attacker's IP first and continues with its connection. This connect may involve authentication hashes (such as NTLM) which the attack can pass onto the real machine in a successful adversary in the middle (AitM) attack.
Canary can now detect these kinds of spoofing attacks by sending out DNS requests of completely made up hostnames and seeing if any device on the network responds with their IP as the "real" device.
Please note that this does mean that your Canary will be generating traffic on your network.
Step 1: Log in to your Console
Step 2: Select the Canary
Select the Canary you want to configure Spoof Detections on.
We have selected the CT-Office-01 Canary.
Step 3: Open configuration
Click on Configure Canary to configure this Canary.
Step 4: Scroll down to the "Spoof Detection" section.
Scroll down until you find Spoof Detections and click the toggle to enable it.
Step 5: Deploy your Canary settings.
Finish configuring the services you want running on the Canary; scroll down and click Deploy new configuration.
Note: Canary Personality affects spoof detection probes.
You may notice that the wording for the Spoof detections differs slightly depending on which Canary personality you are using.
If you are using a Windows personality, you will notice that your Spoof detection probes will be LLMNR and NBNS (these are typical of Windows networks).
If you are using a non Windows personality, you will notice that your Spoof detection probe will be mDNS (these are typical of non Windows networks).
Note: Canaries will generate traffic when Spoof detection is enabled
Enabling Spoof detections means that your Canary will generate some traffic on the network making it a chatty bird instead of sitting quietly. This is required to detect to attacker tools attempting to poison these protocols.