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
75 lines
2.2 KiB
Markdown
75 lines
2.2 KiB
Markdown
---
|
|
name: implementing-honeytokens-for-breach-detection
|
|
description: 'Deploys canary tokens and honeytokens (fake AWS credentials, DNS canaries, document beacons, database records)
|
|
that trigger alerts when accessed by attackers. Uses the Canarytokens API and custom webhook integrations for breach detection.
|
|
Use when building deception-based early warning systems for intrusion detection.
|
|
|
|
'
|
|
domain: cybersecurity
|
|
subdomain: security-operations
|
|
tags:
|
|
- implementing
|
|
- honeytokens
|
|
- for
|
|
- breach
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- DE.CM-01
|
|
- RS.MA-01
|
|
- GV.OV-01
|
|
- DE.AE-02
|
|
---
|
|
|
|
# Implementing Honeytokens for Breach Detection
|
|
|
|
|
|
## When to Use
|
|
|
|
- When deploying or configuring implementing honeytokens for breach detection 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
|
|
|
|
- Familiarity with security operations concepts and tools
|
|
- Access to a test or lab environment for safe execution
|
|
- Python 3.8+ with required dependencies installed
|
|
- Appropriate authorization for any testing activities
|
|
|
|
## Instructions
|
|
|
|
Deploy honeytokens across critical systems to detect unauthorized access. Each token
|
|
type alerts via webhook when triggered by an attacker.
|
|
|
|
```python
|
|
import requests
|
|
|
|
# Create a DNS canary token via Canarytokens
|
|
resp = requests.post("https://canarytokens.org/generate", data={
|
|
"type": "dns",
|
|
"email": "soc@company.com",
|
|
"memo": "Production DB server honeytoken",
|
|
})
|
|
token = resp.json()
|
|
print(f"DNS token: {token['hostname']}")
|
|
```
|
|
|
|
Token types to deploy:
|
|
1. AWS credential files (~/.aws/credentials) with canary keys
|
|
2. DNS tokens embedded in configuration files
|
|
3. Document beacons (Word/PDF) in sensitive file shares
|
|
4. Database honeytoken records in user tables
|
|
5. Web bugs in internal wiki/documentation pages
|
|
|
|
## Examples
|
|
|
|
```python
|
|
# Generate a fake AWS credentials file with canary token
|
|
aws_creds = f"[default]\naws_access_key_id = {canary_key_id}\naws_secret_access_key = {canary_secret}\n"
|
|
with open("/opt/backup/.aws/credentials", "w") as f:
|
|
f.write(aws_creds)
|
|
```
|