D018F1
Data
🗄️ Canary File
Tripwire documents (credentials.csv, passwords.xlsx) in storage.
What it is
A document named and shaped like something valuable, such as an exported credential list or a finance sheet, containing only fake values. Attackers open or copy files like this on sight. Two tripwires fire independently: the read of that exact file in storage, and a callback from the document itself when it is opened, if it is opened online.
Implementation requirements
- Create documents named and shaped like the files they imitate, such as an exported credentials list or a finance spreadsheet. Every value is fake
- Tripwire 1, storage: a read of that exact object. S3: CloudTrail data events (
GetObject) scoped to the object or bucket. Azure:StorageBlobLogs(GetBlob) via a diagnostic setting. GCS: Data Access logs (storage.objects.get). File servers: a SACL with Audit File System (event 4663), or an auditd rule on the path - Tripwire 2, the document itself: a canarytoken that calls back when the file is opened. Thinkst Canarytokens offers MS Word, MS Excel and PDF types
- The open-time callback fails if the file is opened offline or in a viewer that blocks remote content. The storage-level read still fires on download, so deploy both
- Safety: the file contains no real data, and any credential in it is itself a honeytoken (D006) that grants nothing
- OPSEC: plausible sizes, authors and timestamps. Never reuse the same file name across environments
- Rollback: Delete the files from every location they were placed. Deactivate their canarytokens.
- Upkeep: Refresh dates and names, so they do not age out of plausibility. Monthly proof-of-life download and open.
Technologies
AWSAzureGCPLinuxWindows
ATT&CK coverage 16
| Technique | Tactic | Status | Confidence | Tier |
|---|---|---|---|---|
| T1005 Data from Local System |
Collection | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (2 sources)
| ||||
| T1025 Data from Removable Media |
Collection | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (3 sources)
| ||||
| T1039 Data from Network Shared Drive |
Collection | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1119 Automated Collection |
Collection | confirmed | strong | T3 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (3 sources)
| ||||
| T1530 Data from Cloud Storage |
Collection | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (4 sources)
| ||||
| T1560 Archive Collected Data |
Collection | theoretical | moderate | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (3 sources)
Fires when the archived canary is later opened, not when it is archived. | ||||
| T1552 Unsecured Credentials |
Credential Access | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (4 sources)
| ||||
| T1552.001 Credentials In Files |
Credential Access | confirmed | strong | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (5 sources)
| ||||
| T1222 File and Directory Permissions Modification |
Defense Impairment | theoretical | moderate | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1083 File and Directory Discovery |
Discovery | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1619 Cloud Storage Object Discovery |
Discovery | confirmed | strong | T1 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (1 source)
| ||||
| T1011 Exfiltration Over Other Network Medium |
Exfiltration | theoretical | moderate | T2 |
| ↳ Detection point: the decoy fires at a later step of the attack | ||||
↳ Evidence (3 sources)
The canary fires when the stolen file is opened, whatever route took it out; it does not show which medium was used. | ||||
| T1486 Data Encrypted for Impact |
Impact | confirmed | strong | T4 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (3 sources)
| ||||
| T1565 Data Manipulation |
Impact | theoretical | moderate | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
Direct when the attacker alters the decoy's own records; database-level audit not yet sourced. | ||||
| T1080 Taint Shared Content |
Lateral Movement | confirmed | strong | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
| T1570 Lateral Tool Transfer |
Lateral Movement | theoretical | moderate | T2 |
| ↳ Detection point: the attack step itself touches the decoy | ||||
↳ Evidence (2 sources)
| ||||
Evidence
- Decoy File (D3-DF) — MITRE D3FEND standard
- Using Honeybuckets to Characterize Cloud Storage Scanning in the Wild — Izhikevich, K.; Voelker, G.; Savage, S.; Izhikevich, L., IEEE EuroS&P 2024 peer-reviewed
- Canarytokens — Thinkst Applied Research industry
- MITRE Engage — adversary engagement matrix and ATT&CK mapping — MITRE 2022 standard
- Canarytokens token guides (MS Word, Windows Directory, Network Folder, Kubeconfig, AWS Infrastructure, DNS, Azure Login Certificate, MySQL Dump) — Thinkst Applied Research industry
- Ransomware in the honeypot: how we capture keys with sticky canary files — Bitam, S.; Alladoum, C., Elastic Security Labs 2024 industry
- Baiting Inside Attackers Using Decoy Documents — Bowen, B.; Hershkop, S.; Keromytis, A.; Stolfo, S., SecureComm 2009 peer-reviewed
- 4663(S) An attempt was made to access an object — Microsoft industry
- 4670(S) Permissions on an object were changed — Microsoft industry
- MITRE ATT&CK Enterprise v20.0 — MITRE 2026 standard