How xenloops/red_team_notes works
Main Components
• Attacker Environment: Represent the attacker’s machine where tools like Cobalt Strike are run (as noted in the README).
• Beacon/Listener Setup: A component for beacon listeners, which are set up and maintained throughout the engagement.
• Recon and Initial Access: Group components for initial engagement stages (files like 02_external_recon.md and 03_init_compromise.md).
• Internal Recon and Exploitation: Components detailing host recon, privilege escalation (04_host_recon.md, 06_priv_escalation.md), and lateral movement (12_lateral_movement.md, 16_pivoting.md).
• Persistence and Post-Exploitation: Components for persistence (05_persistence.md), credential theft (08_cred_theft.md, 09_password_cracking.md), and further domain control (e.g., 10_domain_recon.md, 21_domain_dominance.md).
• Specialized Techniques: Additional nodes for advanced techniques like DPAPI (14_DPAPI.md), Kerberos exploitation (15_kerberos.md), and manipulation of certificate services or group policies.
• Tools and Utilities: Acknowledgment of common tools (Cobalt Strike and guides) and notes on environment caveats (like snapshot limitations or copy/paste limitations).
Relationships and Interactions
• Typical “flow” of a red team operation: starting at the attacker machine, proceeding to reconnaissance and initial compromise, then escalating privileges, moving laterally through internal networks, and eventually achieving persistence or exfiltrate data.
• Feedback loops where appropriate (for example, how established command and control (C2) structures feed back into ongoing operations).
Architectural Patterns and Design Principles
• Stress the importance of separation of concerns—each file or module in the documentation focuses on a specific phase or technique. This modularity is critical to clearly conveying the workflow and dependencies.
• “pipeline” as a series of steps: from the initial connection (attacker setup) to later phases (credential theft, lateral movement, etc.).
Relevant Technologies, Frameworks, or Libraries
• That the techniques and strategies documented are applied in real network scenarios (lab machines and attacker setups) and often interact with existing operating systems, network configurations, and security measures (such as Microsoft Defender, group policy adjustments, etc.).
Elements
• Clear Labels: Each module or stage (Attacker Environment, Recon, Exploitation, etc.) should be clearly labeled.