Back to catalog
Static reviewDevelopment

Skill dossier

implementing-canary-tokens-for-network-intrusion

Source declaration

Deploys DNS, HTTP, and AWS API key canary tokens across network infrastructure to detect unauthorized access and lateral movement. Integrates with webhook alerting (Slack, Teams, email, generic HTTP) for real-time intrusion notifications. Provides automated token generation, placement strategies, and monitoring for enterprise network environments. Use when building deception-based network intrusion detection with Canarytokens.org and Thinkst Canary platforms.

The author's original description, preserved in English. It describes intent, not verified performance.

Deploys DNS, HTTP, and AWS API key canary tokens across network infrastructure to detect unauthorized access and lateral movement. Integrates with webhook alerting (Slack, Teams, email, generic HTTP) for real-time intrusion notifications. Provides automated token generation, placement strategies, and monitoring for enterprise network environments. Use when building deception-based network intrusion detection with Canarytokens.org and Thinkst Canary platforms.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Deploys DNS, HTTP, and AWS API key canary tokens across network infrastructure to detect unauthorized access and lateral movement. Integrates with webhook alerting (Slack, Teams, email, generic HTTP) for real-time intrusion notifications. Provides automated token generation, placement strategies, and monitoring for enterprise network environments. Use when building deception-based network intrusion detection with Canarytokens.org and Thinkst Canary platforms. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Step 1: Generate DNS Canary Tokens [Source statement; provisional, not tested. Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L91]
  • Step 2: Deploy HTTP Canary Tokens [Source statement; provisional, not tested. Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L120]
  • Step 3: Create AWS API Key Tokens [Source statement; provisional, not tested. Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L145]
  • Step 4: Configure Webhook Alert Integration [Source statement; provisional, not tested. Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L180]
  • Step 5: Enterprise Deployment with Thinkst Canary API [Source statement; provisional, not tested. Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L227]
  • Step 6: Token Placement Strategy by Network Zone [Source statement; provisional, not tested. Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L260]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
62.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-canary-tokens-for-network-intrusion/LICENSEOther11 KB
skills/implementing-canary-tokens-for-network-intrusion/references/api-reference.mdReference5.9 KB
skills/implementing-canary-tokens-for-network-intrusion/scripts/agent.pyScript33.4 KB
skills/implementing-canary-tokens-for-network-intrusion/SKILL.mdInstruction12.1 KB

SKILL.md frontmatter

{
  "name": "implementing-canary-tokens-for-network-intrusion",
  "description": "Deploys DNS, HTTP, and AWS API key canary tokens across network infrastructure to detect unauthorized access and lateral movement. Integrates with webhook alerting (Slack, Teams, email, generic HTTP) for real-time intrusion notifications. Provides automated token generation, placement strategies, and monitoring for enterprise network environments. Use when building deception-based network intrusion detection with Canarytokens.org and Thinkst Canary platforms.\n",
  "domain": "cybersecurity",
  "subdomain": "security-operations",
  "tags": [
    "canary-tokens",
    "intrusion-detection",
    "deception",
    "network-security",
    "honeytokens",
    "breach-detection"
  ],
  "version": "1.0",
  "author": "mukul975",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.CM-01",
    "RS.MA-01",
    "GV.OV-01",
    "DE.AE-02"
  ],
  "mitre_attack": [
    "T1078",
    "T1190",
    "T1059",
    "T1021",
    "T1550"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Core Concepts

    Source-described action candidate under “Core Concepts”; not verified execution.

  3. 03
    Action

    Instructions

    Source-described action candidate under “Instructions”; not verified execution.

  4. 04
    Action

    Step 1: Generate DNS Canary Tokens

    Source-described action candidate under “Step 1: Generate DNS Canary Tokens”; not verified execution.

  5. 05
    Action

    `/etc/hosts` entries pointing to the canary FQDN

    Source-described action candidate under “Step 1: Generate DNS Canary Tokens”; not verified execution.

  6. 06
    Action

    Application configuration files (`databasehost`, `backupserver`)

    Source-described action candidate under “Step 1: Generate DNS Canary Tokens”; not verified execution.

Inspect all extracted workflow candidates (36 candidate steps)
  1. 07
    Action

    SSH config files (`/.ssh/config`) with canary hostnames

    Source-described action candidate under “Step 1: Generate DNS Canary Tokens”; not verified execution.

  2. 08
    Action

    Internal DNS zone files as decoy A records

    Source-described action candidate under “Step 1: Generate DNS Canary Tokens”; not verified execution.

  3. 09
    Action

    CI/CD pipeline environment variables

    Source-described action candidate under “Step 1: Generate DNS Canary Tokens”; not verified execution.

  4. 10
    Action

    Step 2: Deploy HTTP Canary Tokens

    Source-described action candidate under “Step 2: Deploy HTTP Canary Tokens”; not verified execution.

  5. 11
    Action

    Hidden `<img>` tags in internal wiki pages with sensitive titles

    Source-described action candidate under “Step 2: Deploy HTTP Canary Tokens”; not verified execution.

  6. 12
    Action

    URL shortener redirects in shared bookmark collections

    Source-described action candidate under “Step 2: Deploy HTTP Canary Tokens”; not verified execution.

  7. 13
    Action

    Links in internal documentation labeled "admin credentials" or "VPN configs"

    Source-described action candidate under “Step 2: Deploy HTTP Canary Tokens”; not verified execution.

  8. 14
    Action

    `.url` or `.webloc` shortcut files in network shares

    Source-described action candidate under “Step 2: Deploy HTTP Canary Tokens”; not verified execution.

  9. 15
    Action

    Browser bookmark exports in user profile backups

    Source-described action candidate under “Step 2: Deploy HTTP Canary Tokens”; not verified execution.

  10. 16
    Action

    Step 3: Create AWS API Key Tokens

    Source-described action candidate under “Step 3: Create AWS API Key Tokens”; not verified execution.

  11. 17
    Action

    Step 4: Configure Webhook Alert Integration

    Source-described action candidate under “Step 4: Configure Webhook Alert Integration”; not verified execution.

  12. 18
    Action

    Step 5: Enterprise Deployment with Thinkst Canary API

    Source-described action candidate under “Step 5: Enterprise Deployment with Thinkst Canary API”; not verified execution.

  13. 19
    Action

    Step 6: Token Placement Strategy by Network Zone

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  14. 20
    Action

    HTTP tokens in admin panel login pages (hidden image tag)

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  15. 21
    Action

    DNS tokens in web server configuration files

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  16. 22
    Action

    AWS keys in `.env` files on staging servers

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  17. 23
    Action

    DNS tokens in Active Directory Group Policy scripts

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  18. 24
    Action

    AWS keys in developer workstation backup directories

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  19. 25
    Action

    HTTP tokens in internal SharePoint/Confluence pages titled "Emergency Credentials"

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  20. 26
    Action

    Word document tokens in network shares (`\\fileserver\IT\passwords.docx`)

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  21. 27
    Action

    DNS tokens in database configuration files

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  22. 28
    Action

    AWS keys in CI/CD environment variables

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  23. 29
    Action

    SQL Server tokens in connection strings on application servers

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  24. 30
    Action

    SVN/Git tokens in repository configuration files

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  25. 31
    Action

    AWS key tokens in S3 bucket policies (decoy)

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  26. 32
    Action

    DNS tokens in CloudFormation/Terraform templates

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  27. 33
    Action

    HTTP tokens in Lambda function environment variables

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  28. 34
    Action

    Cloned-site tokens mimicking cloud admin consoles

    Source-described action candidate under “Step 6: Token Placement Strategy by Network Zone”; not verified execution.

  29. 35
    Action

    Validation Checklist

    Source-described action candidate under “Validation Checklist”; not verified execution.

  30. 36
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

75 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

51 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 51 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

5 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 5 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

19 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 19 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/implementing-canary-tokens-for-network-intrusion/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/implementing-canary-tokens-for-network-intrusion/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/implementing-canary-tokens-for-network-intrusion
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.