[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78P040V2M8YYXZ7FA1PVV6W":3,"skill-same:01M78P040V2M8YYXZ7FA1PVV6W":94},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":6,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M78P040V2M8YYXZ7FA1PVV6W","executing-red-team-engagement-planning",null,"Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: executing-red-team-engagement-planning\ndescription: Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.\ndomain: cybersecurity\nsubdomain: red-teaming\ntags: [red-team, adversary-simulation, mitre-attack, exploitation, post-exploitation, engagement-planning, rules-of-engagement]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n# Executing Red Team Engagement Planning\n\n## Overview\n\nRed team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins. A well-structured engagement plan ensures the red team simulates realistic adversary behavior while maintaining safety guardrails that prevent unintended business disruption.\n\n\n## When to Use\n\n- When conducting security assessments that involve executing red team engagement planning\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Define clear engagement scope including in-scope and out-of-scope assets, networks, and personnel\n- Establish Rules of Engagement (ROE) with emergency stop procedures, communication channels, and legal boundaries\n- Select appropriate threat profiles from the MITRE ATT&CK framework aligned to the organization's threat landscape\n- Create a detailed attack plan mapping adversary TTPs to engagement objectives\n- Develop deconfliction procedures with the organization's SOC\u002Fblue team\n- Produce a comprehensive engagement brief for stakeholder approval\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Core Concepts\n\n### Engagement Types\n\n| Type | Description | Scope |\n|------|-------------|-------|\n| Full Scope | Complete adversary simulation with physical, social, and cyber vectors | Entire organization |\n| Assumed Breach | Starts from initial foothold, focuses on post-exploitation | Internal network |\n| Objective-Based | Target specific crown jewels (e.g., domain admin, PII exfiltration) | Defined targets |\n| Purple Team | Collaborative with blue team for detection improvement | Specific controls |\n\n### Rules of Engagement Components\n\n1. **Scope Definition**: IP ranges, domains, physical locations, personnel\n2. **Restrictions**: Systems\u002Fnetworks that must not be touched (e.g., production databases, medical devices)\n3. **Communication Plan**: Primary and secondary contact channels, escalation procedures\n4. **Emergency Procedures**: Code word for immediate cessation, incident response coordination\n5. **Legal Authorization**: Signed authorization letters, get-out-of-jail letters for physical tests\n6. **Data Handling**: How sensitive data discovered during testing will be handled and destroyed\n7. **Timeline**: Start\u002Fend dates, blackout windows, reporting deadlines\n\n### Threat Profile Selection\n\nMap organizational threats using MITRE ATT&CK Navigator to select relevant adversary profiles:\n\n- **APT29 (Cozy Bear)**: Government\u002Fdefense sector targeting via spearphishing, supply chain\n- **APT28 (Fancy Bear)**: Government organizations, credential harvesting, zero-days\n- **FIN7**: Financial sector, POS malware, social engineering\n- **Lazarus Group**: Financial institutions, cryptocurrency exchanges, destructive malware\n- **Conti\u002FRoyal**: Ransomware operators, double extortion, RaaS model\n\n## Workflow\n\n### Phase 1: Pre-Engagement\n\n1. Conduct initial scoping meeting with stakeholders\n2. Identify crown jewels and critical business assets\n3. Review previous security assessments and audit findings\n4. Define success criteria and engagement objectives\n5. Draft Rules of Engagement document\n\n### Phase 2: Threat Modeling\n\n1. Identify relevant threat actors using MITRE ATT&CK\n2. Map threat actor TTPs to organizational attack surface\n3. Select primary and secondary attack scenarios\n4. Define adversary emulation plan with specific technique IDs\n5. Establish detection checkpoints for purple team opportunities\n\n### Phase 3: Operational Planning\n\n1. Set up secure communication channels (encrypted email, Signal, etc.)\n2. Create operational security (OPSEC) guidelines for the red team\n3. Establish infrastructure requirements (C2 servers, redirectors, phishing domains)\n4. Develop phased attack timeline with go\u002Fno-go decision points\n5. Create deconfliction matrix with SOC\u002FIR team\n\n### Phase 4: Documentation and Approval\n\n1. Compile engagement plan document\n2. Review with legal counsel\n3. Obtain executive sponsor signature\n4. Brief red team operators on ROE and restrictions\n5. Distribute emergency contact cards\n\n## Tools and Resources\n\n- **MITRE ATT&CK Navigator**: Threat actor TTP mapping and visualization\n- **VECTR**: Red team engagement tracking and metrics platform\n- **Cobalt Strike \u002F Nighthawk**: C2 framework planning and infrastructure design\n- **PlexTrac**: Red team reporting and engagement management platform\n- **SCYTHE**: Adversary emulation platform for attack plan creation\n\n## Validation Criteria\n\n- [ ] Signed Rules of Engagement document\n- [ ] Defined scope with explicit in\u002Fout boundaries\n- [ ] Selected threat profile with mapped MITRE ATT&CK techniques\n- [ ] Emergency stop procedures tested and verified\n- [ ] Communication plan distributed to all stakeholders\n- [ ] Legal authorization obtained and filed\n- [ ] Red team operators briefed and acknowledged ROE\n\n## Common Pitfalls\n\n1. **Scope Creep**: Expanding testing beyond approved boundaries during execution\n2. **Inadequate Deconfliction**: SOC investigating red team activity as real incidents\n3. **Missing Legal Authorization**: Testing without proper signed authorization\n4. **Unrealistic Threat Models**: Simulating threats irrelevant to the organization\n5. **Poor Communication**: Failing to maintain contact with stakeholders during engagement\n\n## Related Skills\n\n- performing-open-source-intelligence-gathering\n- conducting-adversary-simulation-with-atomic-red-team\n- performing-assumed-breach-red-team-exercise\n- building-red-team-infrastructure-with-redirectors\n","# Executing Red Team Engagement Planning\n\n## Overview\n\nRed team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins. A well-structured engagement plan ensures the red team simulates realistic adversary behavior while maintaining safety guardrails that prevent unintended business disruption.\n\n\n## When to Use\n\n- When conducting security assessments that involve executing red team engagement planning\n- When following incident response procedures for related security events\n- When performing scheduled security testing or auditing activities\n- When validating security controls through hands-on testing\n\n## Prerequisites\n\n- Familiarity with red teaming concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n\n- Define clear engagement scope including in-scope and out-of-scope assets, networks, and personnel\n- Establish Rules of Engagement (ROE) with emergency stop procedures, communication channels, and legal boundaries\n- Select appropriate threat profiles from the MITRE ATT&CK framework aligned to the organization's threat landscape\n- Create a detailed attack plan mapping adversary TTPs to engagement objectives\n- Develop deconfliction procedures with the organization's SOC\u002Fblue team\n- Produce a comprehensive engagement brief for stakeholder approval\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Core Concepts\n\n### Engagement Types\n\n| Type | Description | Scope |\n|------|-------------|-------|\n| Full Scope | Complete adversary simulation with physical, social, and cyber vectors | Entire organization |\n| Assumed Breach | Starts from initial foothold, focuses on post-exploitation | Internal network |\n| Objective-Based | Target specific crown jewels (e.g., domain admin, PII exfiltration) | Defined targets |\n| Purple Team | Collaborative with blue team for detection improvement | Specific controls |\n\n### Rules of Engagement Components\n\n1. **Scope Definition**: IP ranges, domains, physical locations, personnel\n2. **Restrictions**: Systems\u002Fnetworks that must not be touched (e.g., production databases, medical devices)\n3. **Communication Plan**: Primary and secondary contact channels, escalation procedures\n4. **Emergency Procedures**: Code word for immediate cessation, incident response coordination\n5. **Legal Authorization**: Signed authorization letters, get-out-of-jail letters for physical tests\n6. **Data Handling**: How sensitive data discovered during testing will be handled and destroyed\n7. **Timeline**: Start\u002Fend dates, blackout windows, reporting deadlines\n\n### Threat Profile Selection\n\nMap organizational threats using MITRE ATT&CK Navigator to select relevant adversary profiles:\n\n- **APT29 (Cozy Bear)**: Government\u002Fdefense sector targeting via spearphishing, supply chain\n- **APT28 (Fancy Bear)**: Government organizations, credential harvesting, zero-days\n- **FIN7**: Financial sector, POS malware, social engineering\n- **Lazarus Group**: Financial institutions, cryptocurrency exchanges, destructive malware\n- **Conti\u002FRoyal**: Ransomware operators, double extortion, RaaS model\n\n## Workflow\n\n### Phase 1: Pre-Engagement\n\n1. Conduct initial scoping meeting with stakeholders\n2. Identify crown jewels and critical business assets\n3. Review previous security assessments and audit findings\n4. Define success criteria and engagement objectives\n5. Draft Rules of Engagement document\n\n### Phase 2: Threat Modeling\n\n1. Identify relevant threat actors using MITRE ATT&CK\n2. Map threat actor TTPs to organizational attack surface\n3. Select primary and secondary attack scenarios\n4. Define adversary emulation plan with specific technique IDs\n5. Establish detection checkpoints for purple team opportunities\n\n### Phase 3: Operational Planning\n\n1. Set up secure communication channels (encrypted email, Signal, etc.)\n2. Create operational security (OPSEC) guidelines for the red team\n3. Establish infrastructure requirements (C2 servers, redirectors, phishing domains)\n4. Develop phased attack timeline with go\u002Fno-go decision points\n5. Create deconfliction matrix with SOC\u002FIR team\n\n### Phase 4: Documentation and Approval\n\n1. Compile engagement plan document\n2. Review with legal counsel\n3. Obtain executive sponsor signature\n4. Brief red team operators on ROE and restrictions\n5. Distribute emergency contact cards\n\n## Tools and Resources\n\n- **MITRE ATT&CK Navigator**: Threat actor TTP mapping and visualization\n- **VECTR**: Red team engagement tracking and metrics platform\n- **Cobalt Strike \u002F Nighthawk**: C2 framework planning and infrastructure design\n- **PlexTrac**: Red team reporting and engagement management platform\n- **SCYTHE**: Adversary emulation platform for attack plan creation\n\n## Validation Criteria\n\n- [ ] Signed Rules of Engagement document\n- [ ] Defined scope with explicit in\u002Fout boundaries\n- [ ] Selected threat profile with mapped MITRE ATT&CK techniques\n- [ ] Emergency stop procedures tested and verified\n- [ ] Communication plan distributed to all stakeholders\n- [ ] Legal authorization obtained and filed\n- [ ] Red team operators briefed and acknowledged ROE\n\n## Common Pitfalls\n\n1. **Scope Creep**: Expanding testing beyond approved boundaries during execution\n2. **Inadequate Deconfliction**: SOC investigating red team activity as real incidents\n3. **Missing Legal Authorization**: Testing without proper signed authorization\n4. **Unrealistic Threat Models**: Simulating threats irrelevant to the organization\n5. **Poor Communication**: Failing to maintain contact with stakeholders during engagement\n\n## Related Skills\n\n- performing-open-source-intelligence-gathering\n- conducting-adversary-simulation-with-atomic-red-team\n- performing-assumed-breach-red-team-exercise\n- building-red-team-infrastructure-with-redirectors\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"subdomain":36,"description":7},[26,27,28,29,30,31,32],"red-team","adversary-simulation","mitre-attack","exploitation","post-exploitation","engagement-planning","rules-of-engagement","mahipal","cybersecurity","1.0","red-teaming","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fexecuting-red-team-engagement-planning",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill executing-red-team-engagement-planning",{"tool":52,"command":53},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill executing-red-team-engagement-planning",{"tool":55,"command":56},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill executing-red-team-engagement-planning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002FSKILL.md",true,[60,66,70,76,80,84,90],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"assets\u002Ftemplate.md","ASSET","资产文件",6830,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Fassets\u002Ftemplate.md",{"path":67,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fapi-reference.md","REFERENCE","参考文档",2273,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Freferences\u002Fapi-reference.md",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fstandards.md",2798,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Freferences\u002Fstandards.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fworkflows.md",6292,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Freferences\u002Fworkflows.md",{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fagent.py","SCRIPT","脚本",6072,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Fscripts\u002Fagent.py",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fprocess.py",33525,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fexecuting-red-team-engagement-planning\u002Fscripts\u002Fprocess.py",[95,103,110,117,124,132],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":20},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":128,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":20},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":20},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]