Skip to content

borghei/Claude-Skills / engineering/red-team

red-team

Verified

This skill should be used when the user asks to "plan a red team engagement", "scope a penetration test", "design a security assessment methodology", "create rules of engagement", or "plan an adversary simulation".

FileKindSize
SKILL.mdskill md5.5 KB
references/red-team-methodology.mdmarkdown3.7 KB
scripts/engagement_planner.pyscript19.5 KB

references/red-team-methodology.md

View on GitHub
# Red Team Methodology Reference

## Frameworks

### MITRE ATT&CK
Industry standard framework mapping adversary tactics, techniques, and procedures (TTPs):

| Tactic | Description | Example Techniques |
|--------|-------------|-------------------|
| Reconnaissance | Gathering target information | Active scanning, search open databases |
| Resource Development | Building attack infrastructure | Acquire infrastructure, develop capabilities |
| Initial Access | Gaining foothold | Phishing, exploit public-facing app, valid accounts |
| Execution | Running adversary code | Command-line interface, scripting, user execution |
| Persistence | Maintaining access | Account creation, scheduled tasks, registry keys |
| Privilege Escalation | Gaining higher permissions | Exploit vulnerability, token manipulation |
| Defense Evasion | Avoiding detection | Obfuscation, disabling security tools |
| Credential Access | Stealing credentials | Brute force, credential dumping, keylogging |
| Discovery | Learning the environment | Network scanning, account discovery |
| Lateral Movement | Moving through network | Remote services, pass-the-hash |
| Collection | Gathering target data | Data from information repositories |
| Exfiltration | Stealing data | Exfiltration over C2 channel, web service |
| Impact | Disrupting operations | Data destruction, defacement |

### OWASP Testing Guide
For web application testing:
- Information Gathering
- Configuration and Deployment Management Testing
- Identity Management Testing
- Authentication Testing
- Authorization Testing
- Session Management Testing
- Input Validation Testing
- Error Handling Testing
- Cryptography Testing
- Business Logic Testing
- Client-Side Testing
- API Testing

### PTES (Penetration Testing Execution Standard)
1. Pre-engagement Interactions
2. Intelligence Gathering
3. Threat Modeling
4. Vulnerability Analysis
5. Exploitation
6. Post-Exploitation
7. Reporting

## Rules of Engagement (ROE)

### Required Elements
- **Scope**: Exact systems, networks, and applications in scope
- **Out of Scope**: Explicitly excluded targets
- **Authorized Actions**: What testers are allowed to do
- **Prohibited Actions**: Actions that are never acceptable
- **Testing Windows**: When testing can occur
- **Emergency Contacts**: Who to call if things go wrong
- **Legal Authorization**: Signed permission documentation
- **Data Handling**: How discovered data/credentials are handled

### Common Prohibitions
- Denial of service attacks against production systems
- Social engineering of non-consenting individuals
- Physical security testing without explicit authorization
- Modification or deletion of production data
- Accessing systems outside the defined scope
- Sharing findings with unauthorized parties

## Engagement Phases

### Phase 1: Planning (10-15% of engagement)
- Scope definition and ROE agreement
- Target enumeration
- Methodology selection
- Tool preparation
- Communication plan

### Phase 2: Reconnaissance (15-20%)
- OSINT gathering
- Network mapping
- Service enumeration
- Vulnerability identification

### Phase 3: Exploitation (30-40%)
- Vulnerability exploitation
- Payload development
- Initial access achievement
- Privilege escalation

### Phase 4: Post-Exploitation (15-20%)
- Lateral movement
- Persistence establishment
- Data collection
- Objective completion

### Phase 5: Reporting (10-15%)
- Finding documentation
- Risk scoring
- Remediation recommendations
- Executive summary
- Technical detail appendix

## Deliverables Checklist

- [ ] Executive summary (1-2 pages)
- [ ] Methodology description
- [ ] Scope confirmation
- [ ] Finding inventory with severity ratings
- [ ] Attack narrative/kill chain
- [ ] Evidence (screenshots, logs)
- [ ] Remediation recommendations (prioritized)
- [ ] Re-test plan
- [ ] Raw data appendix
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: 472kUpdated 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: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated 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