mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-09-02 14:40:51 +03:00
mukul975
cb8d79e068
- Add validated mitre_attack frontmatter to all 754 skills (286 distinct techniques), verified against MITRE ATT&CK v19.1 via the official mitreattack-python library: 0 revoked, deprecated, or invalid IDs - Curate precise per-skill technique IDs for forensics, malware-analysis, threat-intel, and red-team skills (e.g. DCSync -> T1003.006, Kerberoasting -> T1558.003, Pass-the-Ticket -> T1550.003) - Reconcile v19.1 tactic restructuring: Defense Evasion split into Stealth (TA0005) and Defense Impairment (TA0112); revoked T1562.* family and T1070.001/.002 remapped to active equivalents (T1685.*) - Normalize word-split tags across 35 skills (remove filename-derived stopword tags, add semantic cybersecurity tags) - Add api-reference.md for 3 skills that were missing it - Update README ATT&CK section with accurate v19.1 tactic distribution
84 lines
2.3 KiB
Markdown
84 lines
2.3 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:
|
|
- deception-technology
|
|
- honeytokens
|
|
- canary-tokens
|
|
- breach-detection
|
|
- dns-canary
|
|
- security-operations
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- DE.CM-01
|
|
- RS.MA-01
|
|
- GV.OV-01
|
|
- DE.AE-02
|
|
mitre_attack:
|
|
- T1078
|
|
- T1190
|
|
- T1059
|
|
- T1003
|
|
- T1110
|
|
---
|
|
|
|
# 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)
|
|
```
|