Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/jmagly/aiwg --skill forensics-report명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SKILL.md 표시 중
SOC 직업 분류 기준
| namespace | aiwg |
| name | forensics-report |
| platforms | ["all"] |
| description | Generate forensic investigation report |
| commandHint | {"argumentHint":"<forensics-path> [--format triage|full|executive] [--output path]","category":"forensics-reporting"} |
Compile all forensic findings, analysis outputs, timelines, and IOC registers into a structured investigation report. Supports three report formats: triage summary for immediate response, full technical report for detailed review, and executive summary for leadership briefing.
/forensics-report <forensics-path> [options]
| Argument | Required | Description |
|---|---|---|
| forensics-path | Yes | Path to investigation directory (e.g., .aiwg/forensics/) |
| --format | No | Report format: triage, full, executive (default: full) |
| --output | No | Output path (default: .aiwg/forensics/reports/forensic-report.md) |
| --include | No | Specific sections to include: timeline, ioc, evidence, remediation |
| --severity-threshold | No | Minimum finding severity to include: low, medium, high (default: low) |
| --investigator | No | Investigator name for report attribution |
| --case-id | No | Override case ID in report header |
When invoked, this command:
Collect Investigation Artifacts
Severity Classification
Executive Summary (all formats)
Technical Findings Section (triage and full formats)
Timeline Section (full format)
timeline/incident-timeline.mdIOC Section (full format)
Evidence Documentation (full format)
Remediation Plan
| Format | Audience | Length | Sections |
|---|---|---|---|
triage | First responders | 1-2 pages | Executive summary, critical findings, immediate actions |
full | Security team, legal | 10-20 pages | All sections: findings, timeline, IOCs, evidence, remediation |
executive | Leadership, board | 1 page | Business impact, incident classification, remediation summary |
/forensics-report .aiwg/forensics/
/forensics-report .aiwg/forensics/ --format triage
/forensics-report .aiwg/forensics/ --format executive --output .aiwg/forensics/reports/exec-summary.md
/forensics-report .aiwg/forensics/ --severity-threshold high
/forensics-report .aiwg/forensics/ --include timeline,ioc,remediation
Artifacts are saved to .aiwg/forensics/reports/:
.aiwg/forensics/reports/
├── forensic-report.md # Primary investigation report
├── executive-summary.md # Executive version (if requested)
├── triage-report.md # Triage version (if requested)
└── report-metadata.yaml # Generation metadata and integrity hash
# Forensic Investigation Report
Case ID: INV-2026-02-27-web01
Generated: 2026-02-27T15:01:44Z
Classification: CONFIDENTIAL
## Executive Summary
**Incident Classification**: Confirmed Breach
**Severity**: CRITICAL
**Affected Systems**: web01.internal (192.168.1.50)
**Attack Window**: 2026-02-26 22:14Z - 2026-02-27 02:15Z (4h 1m)
**Attacker Objectives**: Persistent access, C2 implant installation
**Data Impact**: Undetermined (investigation ongoing)
Key Findings:
1. [CRITICAL] Successful SSH brute force against account 'deploy'
2. [CRITICAL] C2 implant installed via cron persistence (/tmp/.update)
3. [HIGH] Active C2 beacon to 185.220.101.42:4444
4. [HIGH] Privilege escalation: deploy -> root via sudo
5. [HIGH] Attacker IP 185.220.101.42 is known Tor exit node
## Findings
| ID | Severity | Title | Asset | MITRE |
|------|----------|--------------------------------|--------|---------------|
| F-01 | CRITICAL | SSH brute force success | web01 | T1110.001 |
| F-02 | CRITICAL | Cron-based persistence | web01 | T1053.003 |
| F-03 | HIGH | Active C2 connection | web01 | T1071.001 |
...
## Remediation Plan
### Immediate (0-24h)
- [ ] Isolate web01 from network
- [ ] Revoke 'deploy' account credentials
- [ ] Block 185.220.101.42 at perimeter firewall
- [ ] Remove /tmp/.update and associated cron entry
### Short-term (1-7 days)
- [ ] Rotate all SSH keys on affected system
- [ ] Audit all user accounts for unauthorized additions
- [ ] Review and harden SSH daemon configuration
...
Report Finalization
reporting-complete