mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
24f816b6a3
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
59 lines
2.0 KiB
Markdown
59 lines
2.0 KiB
Markdown
---
|
|
name: implementing-deception-based-detection-with-canarytoken
|
|
description: Deploy and monitor Canary Tokens via the Thinkst Canary API for deception-based breach detection using web bug
|
|
tokens, DNS tokens, document tokens, and AWS key tokens.
|
|
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
|
|
---
|
|
|
|
# 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
|