Skip to content

SSZcreate/Pentab_server / .agents/skills/cybersecurity/skills/executing-red-team-engagement-planning

executing-red-team-engagement-planning

Verified

Build the foundational red team engagement plan - scope definition, Rules of Engagement (restrictions, communication plan, emergency stop procedures, legal authorization), MITRE ATT&CK-aligned threat profile selection, and operational timelines - producing an engagement brief for stakeholder approval. Use before any offensive testing begins, when scoping a full-scope, assumed-breach, objective-based, or purple-team engagement.

FileKindSize
LICENSEother11.0 KB
SKILL.mdskill md6.8 KB
assets/template.mdmarkdown6.7 KB
references/api-reference.mdmarkdown2.2 KB
references/standards.mdmarkdown2.7 KB
references/workflows.mdmarkdown6.1 KB
scripts/agent.pyscript5.9 KB
scripts/process.pyscript32.7 KB

references/standards.md

View on GitHub
# Standards and Framework References

## MITRE ATT&CK

- **Reconnaissance (TA0043)**: Pre-engagement intelligence gathering
  - T1595 - Active Scanning
  - T1592 - Gather Victim Host Information
  - T1589 - Gather Victim Identity Information
  - T1590 - Gather Victim Network Information
  - T1591 - Gather Victim Org Information
- **Resource Development (TA0042)**: Infrastructure and capability preparation
  - T1583 - Acquire Infrastructure
  - T1584 - Compromise Infrastructure
  - T1587 - Develop Capabilities
  - T1588 - Obtain Capabilities
  - T1608 - Stage Capabilities

## PTES (Penetration Testing Execution Standard)

### Pre-engagement Interactions
- Scope definition and boundaries
- Goals and objectives
- Rules of engagement
- Communication plan
- Emergency contacts
- Timeline and milestones
- Legal considerations
- Authorization documentation

### Intelligence Gathering
- OSINT requirements
- Threat actor identification
- Attack surface mapping
- Technology profiling

## OSSTMM (Open Source Security Testing Methodology Manual)

### Section 3: Rules of Engagement
- Test boundaries and limitations
- Test vectors classification
- Compliance requirements
- Reporting standards

### Section 4: Scope
- Physical security scope
- Wireless scope
- Telecommunications scope
- Data networks scope
- Social engineering scope

## NIST SP 800-115

### Technical Guide to Information Security Testing and Assessment
- Section 3: Review Techniques
- Section 4: Target Identification and Analysis
- Section 5: Target Vulnerability Validation
- Section 6: Security Assessment Planning

## CBEST Framework (Bank of England)

- Threat intelligence-led penetration testing
- Threat actor profile development
- Scenario-based adversary simulation
- Control validation and assessment

## TIBER-EU Framework

- European framework for threat intelligence-based ethical red teaming
- Phase 1: Generic Threat Landscape
- Phase 2: Threat Intelligence
- Phase 3: Red Team Testing
- Phase 4: Closure

## CREST STAR (Simulated Targeted Attack and Response)

- Intelligence-led red team testing standard
- Adversary simulation methodology
- Detection and response validation
- Structured reporting format

## Relevant CVE/CWE References

Not directly applicable for planning phase - CVE/CWE references will be mapped during the attack execution phase based on selected TTPs and target environment.

## Compliance Frameworks Impacting Scope

| Framework | Impact on Red Team Scope |
|-----------|--------------------------|
| PCI DSS | Cardholder data environment must be tested |
| HIPAA | PHI handling requires special data protections |
| SOX | Financial systems require specific authorization |
| GDPR | Personal data handling restrictions apply |
| CMMC | DoD contractor supply chain considerations |
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall