mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-04 01:40:19 +03:00
Mahipal
2fb6a9faff
Each rewritten description now states both what the skill does (concrete capability, named tools/artifacts) and an explicit when-to-use trigger, improving agent discovery/activation. Grounded in each skill's own body; changes confined to the `description` field only (bodies and all other frontmatter untouched). Produced by a gated audit->rewrite->recheck loop (548 -> 0 flagged) with a sampled anti-invention check (0 ungrounded). Schema: 817/817 pass. Framework-ID gate: 0 defects.
68 lines
2.3 KiB
Markdown
68 lines
2.3 KiB
Markdown
---
|
|
name: implementing-deception-based-detection-with-canarytoken
|
|
description: 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: cybersecurity
|
|
subdomain: deception-technology
|
|
tags:
|
|
- canarytoken
|
|
- deception
|
|
- honeytokens
|
|
- breach-detection
|
|
- Thinkst-Canary
|
|
- tripwire
|
|
- early-warning
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- DE.CM-01
|
|
- DE.AE-06
|
|
- PR.IR-01
|
|
mitre_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
|
|
|
|
1. Authenticate to the Canary Console API using auth_token
|
|
2. Create web bug (HTTP) tokens for embedding in documents and web pages
|
|
3. Create DNS tokens for monitoring DNS resolution attempts
|
|
4. Create MS Word document tokens for file share deployment
|
|
5. List all active tokens and their trigger history
|
|
6. Query recent alerts for triggered token events
|
|
7. 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
|