Deploys and monitors Canary Tokens via the Thinkst Canary REST API for deception-based breach detection, programmatically creating web bug, DNS, MS Word document, and AWS API key tokens and generating deception coverage reports from triggered alerts. Use when standing up honeytoken tripwires for early breach detection or building a deception-technology coverage report.
Start a fresh conversation. Replace the highlighted placeholders.
Use implementing-deception-based-detection-with-canarytoken to design Canary Token coverage for [authorized environment] and [deployment locations]; after I explicitly approve deployment, create the selected tokens and produce a triggered-alert and coverage report.
Required inputs
[authorized environment]
[deployment locations]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: implementing-deception-based-detection-with-canarytokendescription: Deploys and monitors Canary Tokens via the Thinkst Canary REST API for deception-based breach detection, programmatically creating web bug, DNS, MS Word document, and AWS API key tokens and generating deception coverage reports from triggered alerts. Use when standing up honeytoken tripwires for early breach detection or building a deception-technology coverage report.domain: cybersecuritysubdomain: deception-technologytags: - canarytoken- deception- honeytokens- breach-detection- Thinkst-Canary- tripwire- early-warningversion: '1.0'author: mahipallicense: Apache-2.0nist_csf: - DE.CM-01- DE.AE-06- PR.IR-01mitre_attack: - T1078- T1190- T1059- T1078.004- T1530
Implementing Deception-Based Detection with Canarytoken
Overview
Canary Tokens are lightweight tripwire mechanisms that alert when an attacker accesses a resource. This skill uses the Thinkst Canary REST API to programmatically create tokens (web bugs, DNS tokens, MS Word documents, AWS API keys), deploy them to strategic locations, monitor for triggered alerts, and generate deception coverage reports.
When to Use
When deploying or configuring implementing deception based detection with canarytoken capabilities in your environment
When establishing security controls aligned to compliance requirements
When building or improving security architecture for this domain
When conducting security assessments that require this implementation
Prerequisites
Thinkst Canary Console or canarytokens.org account
API auth token from Canary Console
Python 3.9+ with requests
File system access for deploying document and file tokens
Steps
Authenticate to the Canary Console API using auth_token
Create web bug (HTTP) tokens for embedding in documents and web pages
Create DNS tokens for monitoring DNS resolution attempts
Create MS Word document tokens for file share deployment
List all active tokens and their trigger history
Query recent alerts for triggered token events
Generate deception coverage report with deployment recommendations
Expected Output
JSON report listing all deployed Canary Tokens, trigger history, alert details, and coverage analysis
Deployment map showing token types across network segments