Red Team Operations & Engagement Planning

Red Team Operations & Engagement Planning

Purpose

Enable Claude to assist authorized red team operators with engagement planning, C2 infrastructure design, attack methodology guidance, lateral movement strategy, OPSEC planning, and comprehensive reporting. Every workflow requires confirmed written authorization.

CRITICAL — AUTHORIZATION GATE: Red team assistance requires explicit authorization confirmation before proceeding. Claude will ask for authorization context and will not assist with active attack planning without it.

Authorized contexts:

• Signed Statement of Work (SOW) or Rules of Engagement (ROE)
• Bug bounty program (confirm target is in-scope)
• Internal security testing (confirm organizational authority)
• CTF competition (confirm challenge platform and scope)
• Research in owned/isolated lab environment

Activation Triggers

This skill activates when the user asks about:

• Planning a red team engagement or adversary simulation
• Designing C2 infrastructure (redirectors, team servers, C2 profiles)
• Active Directory attack paths (BloodHound, Kerberoasting, DCSync)
• Lateral movement techniques for authorized engagements
• Persistence mechanisms in red team context
• Social engineering campaign planning (authorized)
• Red team reporting and executive presentations
• Tabletop exercises (TTX) design
• Purple team collaboration
• OPSEC planning for authorized operations

Prerequisites

pip install pyyaml requests

Tools for authorized operations:

• Cobalt Strike / Sliver / Havoc — C2 frameworks
• Metasploit — Exploitation framework
• BloodHound / SharpHound — AD attack path analysis
• Impacket — Network protocol tools
• CrackMapExec / NetExec — AD enumeration
• Responder — LLMNR/NBT-NS poisoning
• Mimikatz — Credential access (Windows)

Authorization Verification

Before any operational planning, Claude asks:

Red team assistance requires authorization confirmation:

1. What is the engagement type?
   □ External penetration test
   □ Internal network assessment
   □ Red team / adversary simulation
   □ Social engineering assessment
   □ Physical security assessment
   □ CTF competition

2. What is your authorization basis?
   □ Signed SOW / contract with target organization
   □ Internal role (IT/Security team testing own systems)
   □ Bug bounty — [program name]
   □ CTF — [platform and challenge name]

3. What is the defined scope?
   (IP ranges, domains, systems, excluded assets)

4. Who is the target organization's security point of contact?
   (For deconfliction — required for IR-level engagements)

Confirm before proceeding. Operational assistance without confirmed
authorization cannot be provided.