Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
mukul975/executing-red-team-engagement-planningWeb e bug bounty

executing-red-team-engagement-planning

⁨Build the foundational red team engagement plan - scope definition, Rules⁩

v1.03 installazioni+3 in 7 giorni36,3K StelleApache-2.0sincronizzato 12 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install mukul975/executing-red-team-engagement-planning

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
cEsiHp7nv9…Nn1v8zCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto08ba5cdf…c69ebcf7
08ba5cdf20f8…2cefc69ebcf78 file · ⁦22.5 KB⁩
ScansioneMedio3 segnalazioni
  • Script eseguibile incluso nella skillscripts/agent.py
  • Script eseguibile incluso nella skillscripts/process.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/executing-red-team-engagement-planning@54a7988

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

Overview

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. A well-structured engagement plan ensures the red team simulates realistic adversary behavior while maintaining safety guardrails that prevent unintended business disruption.

When to Use

  • When conducting security assessments that involve executing red team engagement planning
  • When following incident response procedures for related security events
  • When performing scheduled security testing or auditing activities
  • When validating security controls through hands-on testing

Prerequisites

  • Familiarity with red teaming concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Objectives

  • Define clear engagement scope including in-scope and out-of-scope assets, networks, and personnel
  • Establish Rules of Engagement (ROE) with emergency stop procedures, communication channels, and legal boundaries
  • Select appropriate threat profiles from the MITRE ATT&CK framework aligned to the organization's threat landscape
  • Create a detailed attack plan mapping adversary TTPs to engagement objectives
  • Develop deconfliction procedures with the organization's SOC/blue team
  • Produce a comprehensive engagement brief for stakeholder approval

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.

Core Concepts

Engagement Types

Type Description Scope
Full Scope Complete adversary simulation with physical, social, and cyber vectors Entire organization
Assumed Breach Starts from initial foothold, focuses on post-exploitation Internal network
Objective-Based Target specific crown jewels (e.g., domain admin, PII exfiltration) Defined targets
Purple Team Collaborative with blue team for detection improvement Specific controls

Rules of Engagement Components

  1. Scope Definition: IP ranges, domains, physical locations, personnel
  2. Restrictions: Systems/networks that must not be touched (e.g., production databases, medical devices)
  3. Communication Plan: Primary and secondary contact channels, escalation procedures
  4. Emergency Procedures: Code word for immediate cessation, incident response coordination
  5. Legal Authorization: Signed authorization letters, get-out-of-jail letters for physical tests
  6. Data Handling: How sensitive data discovered during testing will be handled and destroyed
  7. Timeline: Start/end dates, blackout windows, reporting deadlines

Threat Profile Selection

Map organizational threats using MITRE ATT&CK Navigator to select relevant adversary profiles:

  • APT29 (Cozy Bear): Government/defense sector targeting via spearphishing, supply chain
  • APT28 (Fancy Bear): Government organizations, credential harvesting, zero-days
  • FIN7: Financial sector, POS malware, social engineering
  • Lazarus Group: Financial institutions, cryptocurrency exchanges, destructive malware
  • Conti/Royal: Ransomware operators, double extortion, RaaS model

Workflow

Phase 1: Pre-Engagement

  1. Conduct initial scoping meeting with stakeholders
  2. Identify crown jewels and critical business assets
  3. Review previous security assessments and audit findings
  4. Define success criteria and engagement objectives
  5. Draft Rules of Engagement document

Phase 2: Threat Modeling

  1. Identify relevant threat actors using MITRE ATT&CK
  2. Map threat actor TTPs to organizational attack surface
  3. Select primary and secondary attack scenarios
  4. Define adversary emulation plan with specific technique IDs
  5. Establish detection checkpoints for purple team opportunities

Phase 3: Operational Planning

  1. Set up secure communication channels (encrypted email, Signal, etc.)
  2. Create operational security (OPSEC) guidelines for the red team
  3. Establish infrastructure requirements (C2 servers, redirectors, phishing domains)
  4. Develop phased attack timeline with go/no-go decision points
  5. Create deconfliction matrix with SOC/IR team

Phase 4: Documentation and Approval

  1. Compile engagement plan document
  2. Review with legal counsel
  3. Obtain executive sponsor signature
  4. Brief red team operators on ROE and restrictions
  5. Distribute emergency contact cards

Tools and Resources

  • MITRE ATT&CK Navigator: Threat actor TTP mapping and visualization
  • VECTR: Red team engagement tracking and metrics platform
  • Cobalt Strike / Nighthawk: C2 framework planning and infrastructure design
  • PlexTrac: Red team reporting and engagement management platform
  • SCYTHE: Adversary emulation platform for attack plan creation

Validation Criteria

  • Signed Rules of Engagement document
  • Defined scope with explicit in/out boundaries
  • Selected threat profile with mapped MITRE ATT&CK techniques
  • Emergency stop procedures tested and verified
  • Communication plan distributed to all stakeholders
  • Legal authorization obtained and filed
  • Red team operators briefed and acknowledged ROE

Common Pitfalls

  1. Scope Creep: Expanding testing beyond approved boundaries during execution
  2. Inadequate Deconfliction: SOC investigating red team activity as real incidents
  3. Missing Legal Authorization: Testing without proper signed authorization
  4. Unrealistic Threat Models: Simulating threats irrelevant to the organization
  5. Poor Communication: Failing to maintain contact with stakeholders during engagement
  • performing-open-source-intelligence-gathering
  • conducting-adversary-simulation-with-atomic-red-team
  • performing-assumed-breach-red-team-exercise
  • building-red-team-infrastructure-with-redirectors

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileSìSì
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/agent.py
  2. MediaFile · Script eseguibile incluso nella skillscripts/process.py
  3. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.013 nov 202654a798808ba5cdfFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login