---
name: rt-create-sead
description: "Create SEAD — Statement of Engagement Authorization Document. Use at the start of every engagement to document legal authorization, scope, targets, exclusions, rules of engagement, and emergency contacts. Required before any testing begins."
---

# rt-create-sead

# SEAD Creation Workflow

## Step 1 — Collect Engagement Details
Ask the operator for:
- Engagement reference number (format: CLIENT-RT-TYPE-YEAR-NNN)
- Client organization name and point of contact
- Authorized tester(s) name and organization
- Engagement type: blackbox / greybox / whitebox
- Testing methodology selected

## Step 2 — Define Scope
Document:
- **In-scope targets**: IPs, CIDR ranges, domains, URLs, apps
- **Out-of-scope**: What must NOT be touched
- **Scope type**: External / Internal / Full
- **Testing window**: Start and end dates/times
- **After-hours testing**: Allowed or not?

## Step 3 — Rules of Engagement
Document:
- Destructive testing: Allowed / Not allowed
- DoS simulation: Allowed with 24hr notice / Never
- Social engineering: Phishing / Vishing / Physical
- Data handling: What to do with discovered PII
- Evidence retention: Period and destruction policy
- Escalation triggers: When to stop immediately

## Step 4 — Emergency Contacts
| Role | Name | Phone | Email | Available |
|------|------|-------|-------|-----------|
| CISO / Security Contact | | | | 24/7 |
| IT Emergency | | | | 24/7 |
| Project Manager | | | | Business hours |
| Legal Counsel | | | | On call |

## Step 5 — Generate SEAD Document
Create: `_rtexit-output/docs/engagement/SEAD.md`
Use template: `{skill-root}/template.md`

## Step 6 — Initialize Engagement
Run:
```bash
python3 {project-root}/_rtexit/scripts/autodoc_engine.py init \
  --ref ENGAGEMENT_REF \
  --client CLIENT_NAME \
  --methodology METHODOLOGY \
  --scope SCOPE_TYPE
```

## SEAD Completeness Criteria

A SEAD is not complete until it answers who authorized the work, which assets are in scope, which techniques are excluded, when testing may occur, what happens during instability, who receives urgent escalation, and what evidence may be collected.

## Validation

| Gate | Expected |
|---|---|
| SEAD file exists | Yes |
| Client name and reference | Populated |
| Dates | Current |
| Scope | Non-empty |
| Rules of Engagement | Defined |
| Sign-off | Captured or explicitly pending |

## Handoff

After creating the SEAD, run `rt-scope-definition`, `rt-rules-of-engagement`, `rt-methodology-selector`, and initialize timeline through `rt-autodoc`.
