data-handling-template
Data handling plan generator — evidence retention, encryption, chain-of-custody, compliance frameworks (GDPR / HIPAA / PCI-DSS / SOC2).
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- data-handling-template
- metadata
- { "tags": "data-handling, evidence, retention, encryption, chain-of-custody, compliance, gdpr, hipaa", "subdomain": "planning", "when_to_use": "create data handling plan, evidence retention, chain-of-custody, GDPR, HIPAA, PCI-DSS, compliance, PII handling", "upstream_ref": "Soundwave data-handling template — evidence retention, encryption, chain-of-custody, compliance" }
- description
- Data handling plan generator — evidence retention, encryption, chain-of-custody, compliance frameworks (GDPR / HIPAA / PCI-DSS / SOC2).
- allowed-tools
- Read Write Edit
03 SKILL.md 正文
Data Handling Plan Generator
The data handling plan defines what evidence the agent collects, where it lives, how long it's kept, and who can read it. Replaces the deprecated free-form RoE.data_handling string with structured per-class fields.
When to Use
- After RoE is written (RoE constraints + scope drive which data classes appear)
- User says "create data handling", "retention policy", "evidence storage", "PII handling", "compliance"
Workflow
Step 1: Start From the Schema Defaults
The DataHandlingPlan schema seeds four default classes — credentials, pii, source-code, business-data — with conservative retention. Keep these by default; override only when the engagement requires stricter or looser rules.
Step 2: Add Engagement-Specific Classes
Based on the interview:
| Engagement type | Likely additional classes |
|---|---|
| Healthcare client | health-records (classification: secret, retention: 7 days, framework: HIPAA) |
| Financial client | cardholder-data (classification: secret, retention: 0 days — never store, framework: PCI-DSS) |
| EU client / data subjects | Mark existing pii with framework: GDPR; consider personal-data-eu for stricter handling |
| Defense / classified | controlled-unclassified (classification: secret, retention: 0 days off-network) |
Step 3: Set Evidence Storage Path
Default "/workspace/<engagement>/evidence/" works for sandbox-isolated engagements. Override only when:
- Engagement requires an external-bucket destination (S3 / Azure Blob with client KMS)
- Multiple engagement workspaces share an evidence repository
Step 4: Compliance Frameworks
Set compliance_frameworks from the interview. Common entries: GDPR, HIPAA, PCI-DSS, SOC2, NIST 800-53, FedRAMP, ISO 27001.
The orchestrator (Decepticon) reads this list and refuses to start objectives that violate the matching framework's evidence-handling rules.
Step 5: Purge Hard Cap
purge_after_days is the GLOBAL upper bound — every artifact older than this is deleted regardless of per-class retention. Default 90 days; reduce for engagements with tighter regulatory exposure.
Validation Checklist
Before writing plan/data-handling.json:
- [ ] At least one
data_classiscredentials-equivalent - [ ] Every class has
retention_days >= 0 - [ ]
purge_after_days >= max(class.retention_days)(otherwise classes get cut short) - [ ] If
compliance_frameworksincludes HIPAA / GDPR / PCI-DSS, matching data classes exist - [ ]
chain_of_custody=Truefor any engagement that may produce findings
Anti-patterns
- Setting
retention_days=0forcredentialswithout explicit operator approval — agent then can't reference creds across phases - Disabling
encryption_at_restfor any restricted+ class — straight compliance violation - Listing HIPAA in
compliance_frameworkswithout ahealth-recordsclass — orchestrator will refuse objectives that touch PHI
Output
Write to plan/data-handling.json validating against decepticon.core.schemas.DataHandlingPlan.
04 同仓库更多 Skills
wps-pixie-dust
WPS Pixie-Dust offline nonce attack (reaver -K / pixiewps) and fallback online PIN brute (bully) to recover the AP's WPA PSK without capturing a handshake.
wpa3-sae
WPA3-SAE transition-mode downgrade (DragonShift), SSID Confusion CVE-2023-52424, Dragonblood side-channels, and SAE captive-portal credential recovery against WPA3-Personal networks.
wpa2-psk
WPA/WPA2-PSK handshake capture via targeted deauth + PMKID (no deauth required) + offline hashcat cracking. The most common consumer/SMB encryption mode in 2026.
wpa-enterprise-eap
WPA/WPA2/WPA3-Enterprise (802.1X/EAP) rogue-RADIUS evil-twin for MSCHAPv2 capture, GTC downgrade, and PEAP relay. MSCHAPv2 capture equals a NetNTLM hash — the primary wireless on-ramp to Active Directory.
krack-fragattacks
KRACK key-reinstallation (CVE-2017-13077..13082) and FragAttacks fragmentation/aggregation flaws (CVE-2020-24586..24588, CVE-2020-26139..26147) against legacy or embedded 802.11 supplicants with poor patch cadence.
evil-twin-karma
Evil-twin rogue AP with KARMA/Mana PNL-probe response, captive-portal credential capture, and post-association MITM for PSK/open networks. Distinct from wpa-enterprise-eap which targets 802.1X.