2 ms·
I evaluated this a while back. Cool idea but limited application in a corporate environment. But for personal use, why not? Someone needs to open a document fo
by _8j50 4y ago
I evaluated this a while back. Cool idea but limited application in a corporate environment. But for personal use, why not?
Someone needs to open a document for the canary token to trigger. Even the smallest company with M365 gets MSIP (formerly Azure Information Protection), if you classify your docs right, only people who own or have been shared the document can decrypt it and even without a good classification, you get logs of any M365 document being opened, so why can't I just have a regular but public doc everywhere and monitor when it gets opened from external IPs, user agents,etc....
I struggled to show value for this. Honehashes are more interesting for me: https://github.com/EmpireProject/Empire/blob/master/data/module_source/management/New-HoneyHash.ps1 https://github.com/EmpireProject/Empire/blob/master/data/mod...
- icecap12 4y agoNot everyone is using Azure and a full M365 implementation though.
- _8j50 4y agoFair enough, but you need some sort of data classification and usually that tool can also do protection and leak detection. This tool is focused on just the canary part, if you have documents that can just get copied on a usb drive or emailed and exposed to the public there are plenty of good solutions before you accept that as an inevitable reality and implement leak detection via canaries. Don't get me wrong though, I'm a believer in deception tech in general.