--- name: performing-deception-technology-deployment-4737ca1cd4b2 description: 'Deploys deception technology including honeypots, honeytokens, and decoy systems to detect attackers who have bypassed perimeter defenses, providing high-fidelity alerts with near-zero false positive rates. Use when SOC teams need early warning of lateral movement, credential abuse, or internal reconnaissance by deploying convincing traps across the network. ' domain: cybersecurity subdomain: soc-operations tags: - soc - deception - honeypot - honeytoken - canary - lateral-movement - detection version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - DE.CM-01 - DE.AE-02 - RS.MA-01 - DE.AE-06 mitre_attack: - T1078 - T1685.002 - T1685.005 - T1566 - T1021 --- # Performing Deception Technology Deployment ## When to Use Use this skill when: - SOC teams need high-fidelity detection of post-compromise lateral movement with near-zero false positives - Existing detection tools miss advanced attackers who avoid triggering threshold-based alerts - The organization wants to detect credential abuse by planting fake credentials as honeytokens - Network segmentation gaps need compensating detection controls **Do not use** as a replacement for fundamental security controls (patching, EDR, network segmentation) — deception is a detection layer, not a prevention mechanism. ## Prerequisites - Network segments identified for honeypot/decoy deployment (server VLANs, DMZ, OT networks) - Deception platform (Thinkst Canary, Attivo/SentinelOne Hologram, or open-source alternatives) - SIEM integration for deception alerts (any interaction with deception assets is suspicious) - Active Directory access for honeytoken account and credential creation - Network team coordination for IP allocation and traffic routing ## Workflow ### Step 1: Map Attack Surface for Deception Placement Identify high-value network segments where attackers would traverse: ``` DECEPTION DEPLOYMENT MAP ━━━━━━━━━━━━━━━━━━━━━━━━ Segment Decoy Type Rationale Server VLAN Fake file server Attackers enumerate SMB shares during recon Database VLAN Fake DB server SQL scanning detected in past incidents AD/DC Segment Honeytoken account Credential theft detection Executive Subnet Fake workstation Targeted attacks pivot through exec systems DMZ Honeypot web app External attacker detection OT Network Fake PLC/HMI Industrial threat detection Cloud (AWS VPC) Canary EC2 + S3 Cloud lateral movement detection ``` ### Step 2: Deploy Thinkst Canary Devices Configure Canary devices mimicking real infrastructure: **Windows File Server Canary:** ```json { "device_name": "FILESERVER-BK04", "personality": "windows-server-2019", "services": { "smb": { "enabled": true, "shares": ["Finance_Backup", "HR_Archive", "IT_Docs"], "files": [ {"name": "Q4_Revenue_2024.xlsx", "alert_on": "read"}, {"name": "employee_ssn_export.csv", "alert_on": "read"}, {"name": "admin_passwords.kdbx", "alert_on": "read"} ] }, "rdp": {"enabled": true}, "http": {"enabled": false} }, "network": { "ip": "10.0.5.200", "hostname": "FILESERVER-BK04", "domain": "company.local" }, "alert_webhook": "https://soar.company.com/api/webhook/canary" } ``` **Database Server Canary:** ```json { "device_name": "DB-ARCHIVE-02", "personality": "linux-mysql", "services": { "mysql": { "enabled": true, "port": 3306, "databases": ["customer_pii", "payment_archive"], "alert_on_login_attempt": true }, "ssh": { "enabled": true, "port": 22, "alert_on_login_attempt": true } }, "network": { "ip": "10.0.10.50", "hostname": "db-archive-02" } } ``` ### Step 3: Deploy Honeytokens in Active Directory Create fake privileged accounts that should never be used: ```powershell # Create honeytoken service account New-ADUser -Name "svc_sql_backup" ` -SamAccountName "svc_sql_backup" ` -UserPrincipalName "svc_sql_backup@company.local" ` -Description "SQL Backup Service Account - DO NOT DELETE" ` -AccountPassword (ConvertTo-SecureString "FakeP@ssw0rd2024!" -AsPlainText -Force) ` -Enabled $true ` -PasswordNeverExpires $true ` -CannotChangePassword $true # Add to a group that looks attractive (but monitor for any use) Add-ADGroupMember -Identity "Domain Admins" -Members "svc_sql_backup" # Place cached credentials on decoy workstation # (Mimikatz/credential dumping will find these) cmdkey /add:fileserver-bk04.company.local /user:company\svc_sql_backup /pass:FakeP@ssw0rd2024! ``` **Monitor honeytoken usage in Splunk:** ```spl index=wineventlog sourcetype="WinEventLog:Security" (EventCode=4624 OR EventCode=4625 OR EventCode=4648 OR EventCode=4768 OR EventCode=4769) TargetUserName="svc_sql_backup" | eval alert_severity = "CRITICAL" | eval alert_message = "HONEYTOKEN ACCOUNT USED — Likely credential theft detected" | table _time, EventCode, src_ip, ComputerName, TargetUserName, Logon_Type, alert_message ``` ### Step 4: Deploy Canary Files and Documents Plant tracked documents that beacon when opened: **Canary Document (Word doc with tracking):** ```python # Using Thinkst Canary API to create a canary token document import requests response = requests.post( "https://YOURCOMPANY.canary.tools/api/v1/canarytoken/create", data={ "auth_token": "YOUR_API_TOKEN", "kind": "doc-msword", "memo": "Finance backup folder canary document", "flock_id": "flock:default" } ) token = response.json() download_url = token["canarytoken"]["canarytoken_url"] print(f"Download canary doc: {download_url}") # Place this document in honeypot SMB shares and sensitive directories ``` **AWS Canary Token (S3 access key):** ```python # Create AWS canary token — alerts when access key is used response = requests.post( "https://YOURCOMPANY.canary.tools/api/v1/canarytoken/create", data={ "auth_token": "YOUR_API_TOKEN", "kind": "aws-id", "memo": "Canary AWS key in developer laptop .aws/credentials" } ) aws_keys = response.json() print(f"Access Key: {aws_keys['canarytoken']['access_key_id']}") print(f"Secret Key: {aws_keys['canarytoken']['secret_access_key']}") # Plant in .aws/credentials on developer workstations ``` ### Step 5: Integrate Deception Alerts with SIEM/SOAR All deception alerts are high-fidelity — any interaction is suspicious: **Splunk Alert for Canary Triggers:** ```spl index=canary sourcetype="canary:alerts" | eval severity = "CRITICAL" | eval confidence = "HIGH — Deception asset triggered, zero false positive expected" | table _time, canary_name, alert_type, source_ip, service, details | sendalert create_notable param.rule_title="Deception Alert — Canary Triggered" param.severity="critical" param.drilldown_search="index=canary source_ip=$source_ip$" ``` **SOAR Automated Response:** ```python def canary_triggered(container): """Auto-response for deception alerts — high confidence, no approval needed""" source_ip = container["artifacts"][0]["cef"]["sourceAddress"] # Immediately isolate the source phantom.act("quarantine device", parameters=[{"ip_hostname": source_ip}], assets=["crowdstrike_prod"], name="isolate_attacker_host") # Block at firewall phantom.act("block ip", parameters=[{"ip": source_ip, "direction": "both"}], assets=["palo_alto_prod"], name="block_attacker_ip") # Create high-priority incident phantom.act("create ticket", parameters=[{ "short_description": f"DECEPTION ALERT: Canary triggered from {source_ip}", "urgency": "1", "impact": "1" }], assets=["servicenow_prod"]) phantom.set_severity(container, "critical") ``` ### Step 6: Maintain Deception Realism Regularly update decoys to maintain believability: - Rotate honeytoken passwords quarterly (update cached credentials on decoy workstations) - Update canary file modification dates to appear recently accessed - Add realistic network traffic to honeypots (scheduled SMB enumeration, DNS lookups) - Register honeypot hostnames in DNS and Active Directory to appear in network scans - Update canary document contents to match current business context ## Key Concepts | Term | Definition | |------|-----------| | **Honeypot** | Decoy system mimicking real infrastructure to attract and detect attackers in the network | | **Honeytoken** | Fake credential, file, or data record that triggers an alert when accessed or used | | **Canary** | Lightweight deception device or token that alerts on any interaction (Thinkst Canary platform) | | **Breadcrumb** | Planted artifact (cached credential, bookmark, config file) leading attackers to deception assets | | **High-Fidelity Alert** | Detection signal with near-zero false positive rate because no legitimate user should interact with deception assets | | **Decoy Network** | Set of interconnected honeypots simulating a realistic network segment to observe attacker TTPs | ## Tools & Systems - **Thinkst Canary**: Commercial deception platform offering hardware/virtual canaries and canary tokens - **Canarytokens.org**: Free honeytoken generation service (DNS, HTTP, AWS keys, Word docs, SQL queries) - **Attivo Networks (SentinelOne)**: Enterprise deception platform with AD decoys and endpoint breadcrumbs - **HoneyDB**: Community honeypot data aggregation platform for threat intelligence sharing - **T-Pot**: Open-source multi-honeypot platform combining 20+ honeypot types in a Docker deployment ## Common Scenarios - **Lateral Movement Detection**: Attacker enumerates SMB shares and accesses honeypot file server — immediate high-fidelity alert - **Credential Theft Discovery**: Mimikatz dumps honeytoken cached credentials — usage of fake account triggers alert - **Cloud Key Compromise**: Stolen AWS canary token used from external IP — detects supply chain or insider compromise - **Ransomware Early Warning**: Ransomware encrypts canary files on honeypot shares — early detection before production systems affected - **Insider Threat Signal**: Employee accesses honeypot "salary database" — indicates unauthorized data exploration ## Output Format ``` DECEPTION ALERT — CRITICAL ━━━━━━━━━━━━━━━━━━━━━━━━━━ Time: 2024-03-15 14:23:07 UTC Canary: FILESERVER-BK04 (10.0.5.200) Service: SMB — File share "Finance_Backup" accessed Source: 192.168.1.105 (WORKSTATION-042, Finance Dept) User: company\jsmith File Accessed: Q4_Revenue_2024.xlsx (canary document) Alert Confidence: HIGH — No legitimate reason to access deception asset False Positive Likelihood: <1% Automated Response: [DONE] WORKSTATION-042 isolated via CrowdStrike [DONE] 192.168.1.105 blocked at firewall (bidirectional) [DONE] Incident INC0012567 created (P1 — Critical) [PENDING] Tier 2 investigation — determine if workstation compromised or insider threat ``` --- Source attribution: costrict-plugins-repo Original project: https://github.com/costrict-plugins-repo/mukul975-anthropic-cybersecurity-skills-cybersecurity-skills/blob/1b344d155f00bae5cf27d8eba9508e8f5050d904/skills/performing-deception-technology-deployment/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: costrict-plugins-repo Original project: https://github.com/costrict-plugins-repo/mukul975-anthropic-cybersecurity-skills-cybersecurity-skills/blob/1b344d155f00bae5cf27d8eba9508e8f5050d904/skills/performing-deception-technology-deployment/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Security Engineer Specialties: API Tools: Attivo Sentinelone, Thinkst Canary Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: f868f977fd1e768be32d97d01a34718a0857fab4c008cbef5027762117b5a153